| name | worker-blocked |
| description | Report a blocker to supervisor via Beads |
Worker: Handle Blockers
Command: pasture:worker:blocked — Report a blocker to supervisor via Beads
-> Full workflow in PROCESS.md <- Phase 9
[wblk-update-status]
- Given: a blocker
- When: reporting
- Then: update Beads task status and document details
- Should not: guess or work around the blocker
[wblk-wait-for-response]
- Given: blocker sent
- When: waiting
- Then: wait for supervisor response
- Should not: continue with incomplete info
When to Use
Cannot proceed due to missing dependency, unclear requirement, or need changes in another file.
Steps
-
Identify what's blocking (missing type, unclear requirement, file dependency)
-
Update Beads task:
bd update <task-id> --status=blocked
bd update <task-id> --notes="Blocked: <reason>. Missing: <dependency or clarification needed>"
-
Document the blocker in the task:
bd comments add <task-id> "BLOCKED: <reason>. Need: <dependency or clarification>"
-
Wait for supervisor or dependency resolution — check with bd show <task-id>
Common Blockers
- Missing type definition from another file
- Unclear requirement in acceptance_criteria
- Need interface defined in dependent file
- Conflicting constraints in validation_checklist