Escalate and resolve blockers by identifying type, documenting in state/STATE.md, proposing resolutions, assigning to specialists, and tracking to closure. Triggers: blocker, blocked, impediment, stuck, can't proceed
Identify, document, and drive resolution of project blockers.
Classify the blocker:
| Type | Examples |
|---|---|
| Technical | Bug, missing API, infrastructure issue |
| Dependency | Waiting on another team, external service, third-party |
| Resource | Missing knowledge, tooling, access permissions |
| Decision | Pending architectural or product decision |
Add the blocker under a ## Blockers section:
### Blocker: [Title]
- **Type:** [technical/dependency/resource/decision]
- **Blocking:** [what work is blocked]
- **Since:** [date]
- **Owner:** [who is responsible for resolution]
- **Status:** Open
Route to the appropriate agent:
| Blocker Type | Agent |
|---|---|
| Technical (API) | api-specialist |
| Technical (DB) | database-specialist |
| Technical (infra) | devops-specialist |
| Security | security-specialist |
| Design | ui-ux-specialist |
| Architecture | solution-architect |
| Decision | tech-lead or product-manager |
logs/claude_log.md.