# Claude Prompt to Find Project Blockers - Kanera

> Copy a Claude prompt that searches live Kanera boards for blockers, ranks delivery impact, and produces an escalation list with source cards.

Canonical page: https://www.kanera.app/prompts/claude-prompt-find-project-blockers

Claude project prompt

# Claude prompt to find project blockers

Ask Claude to search live project work for explicit blockers and quieter warning signs, then rank what needs attention now.

Best for: Delivery reviews, cross-team dependencies, overdue work, and preparation for escalation meetings.

Claude prompt Copy prompt

You are helping me run a project blocker review using live Kanera data through MCP.

Scope: [WORKSPACE, BOARD, PROJECT, OR "ALL ACCESSIBLE WORK"]
Review window: [NUMBER OF DAYS]
Time zone: [TIME ZONE]
Delivery deadline or milestone: [DATE OR "NOT SET"]

Inspect the scoped work and find:
1. Cards explicitly marked blocked.
2. Overdue active cards and due-soon work with unresolved dependencies.
3. Cards whose recent comments describe waiting, missing approval, access problems, unanswered questions, or external dependency delays.
4. Blockers that affect multiple cards, boards, or milestones.
5. Items that appear stale because no meaningful progress is recorded during the review window.

For every finding, report:
- Kanera card key and title.
- What is blocked or at risk.
- Evidence from the current card, comment, or activity history.
- Delivery impact.
- Current owner and dependency owner when recorded.
- Age of the blocker or date of the latest meaningful update.
- Next action and escalation needed.
- Confidence: Confirmed blocker, likely blocker, or needs review.

Rank the findings by delivery impact, then give me:
- The three interventions that would unblock the most work.
- Questions I need to answer before escalating.
- A concise meeting-ready summary.

Do not label a card blocked only because it is old. Do not invent dependencies, dates, or ownership. Cite the relevant card keys. Keep this read-only unless I explicitly approve a follow-up change.

## Worked example output

Example result after Claude reviews two connected delivery boards, their active cards, and recent comments through Kanera MCP.

Example result

Project blocker review
Scope: Atlas launch workspace

1. Confirmed blocker: Production analytics access
Card: ATLAS-204 | Configure production conversion events
Impact: Blocks production verification for three launch journeys and the final analytics sign-off.
Evidence: The card remains in Blocked. The latest comment says the requested property access has not been granted.
Owner: Imani
Dependency owner: Client analytics administrator, name not recorded
Latest meaningful update: 12 September
Next action: Confirm the administrator and request access before the 17 September release review.

2. Confirmed blocker: Legal approval for signup copy
Card: ATLAS-189 | Finalise signup disclosures
Impact: Prevents release approval for the signup flow and holds ATLAS-211.
Evidence: Due date passed on 13 September. The latest comment says revised wording is still with legal.
Owner: Dan
Dependency owner: Legal team
Next action: Ask legal to approve the current wording or return tracked changes by 16 September.

3. Likely blocker: Unassigned data migration check
Card: ATLAS-217 | Validate legacy account mapping
Impact: Could delay the rehearsal because no owner is recorded and the card is due in two days.
Evidence: Active card, no assignee, no activity in six days.
Next action: Assign an owner and confirm whether the rehearsal depends on this check.

Highest-leverage interventions
- Resolve analytics access to unblock three verification tasks.
- Get a dated legal response on signup copy.
- Assign ATLAS-217 before the migration rehearsal.

Meeting summary
Two confirmed external dependencies threaten release approval, while one unassigned migration check needs immediate ownership.

## Get a more reliable result

- 1 Give Claude a milestone date so it can distinguish urgent blockers from ordinary waiting work.

- 2 Keep confirmed and inferred blockers separate to avoid overstating weak signals.

- 3 Review stale cards with their activity history before escalating them as blocked.

## Prompt questions

How is this different from the ChatGPT blocker summary? Claude searches live boards to find blockers, including stale work and comments about waiting. ChatGPT summarises blocker notes you already have into a client update.

Will Claude mark old cards as blocked? No. The prompt says not to label a card blocked only because it is old. Confirmed, likely, and needs-review findings stay separate.

Can Claude escalate directly? It prepares the list and the meeting summary. Review the evidence, then decide what to escalate.

## Go from live Kanera work to a finished update.

Connect Claude to Kanera so it can trace blockers across cards, comments, owners, due dates, and board activity without a manual export.

[Explore Kanera's AI workflow](https://www.kanera.app/ai-agents)

[Start free](https://board.kanera.app/signup) 30-day Pro trial. No card required.

## Related prompts

Nearby ChatGPT and Claude templates for the same delivery job.

[Browse all prompts](https://www.kanera.app/prompts)

[ChatGPT prompt to summarize project blockers](https://www.kanera.app/prompts/chatgpt-prompt-summarize-project-blockers)[Claude prompt for weekly project status report](https://www.kanera.app/prompts/claude-prompt-weekly-project-status-report)[Claude prompt for project risk register](https://www.kanera.app/prompts/claude-prompt-project-risk-register)[ChatGPT prompt to chase client for inputs](https://www.kanera.app/prompts/chatgpt-prompt-chase-client-for-inputs)

## Machine-readable resources

- [Kanera AI index](https://www.kanera.app/llms.txt)
- [Kanera documentation index](https://www.kanera.app/docs/llms.txt)
- [Agent discovery guidance](https://www.kanera.app/agents.md)