Agent skill
blocked
Mark expedition as blocked with reason and optional unblock agent
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/blocked
SKILL.md
Mark as Blocked
Mark an expedition as blocked with a clear reason so other agents know why and who can help.
Required Arguments
EXP-XXX- The expedition ID to blockreason- Why it's blocked (quote if multiple words)
Optional Arguments
--unblock-by agent-X- Which agent can unblock this
Steps
1. Move to Blocked Status
yurtle-kanban move EXP-XXX blocked
2. Update Expedition File
Add a blocked section to the expedition file:
Find the expedition file and add after the frontmatter:
> **BLOCKED**: [reason]
> **Since:** YYYY-MM-DD
> **Can unblock:** [agent-X or "anyone"]
Also add a Ship's Log entry:
### YYYY-MM-DD: BLOCKED
**Reason:** [reason]
**Can unblock:** [who]
**Context:** [any additional context]
3. Commit and Push
git add kanban-work/expeditions/EXP-XXX*.md
git commit -m "blocked(exp-XXX): [short reason]
Co-Authored-By: Claude <[email protected]>"
git push origin HEAD
4. Confirm Block
Show:
- Current blocked items count
- Who can unblock
- Suggest notifying the unblocking agent
Common Block Reasons
| Reason | Who Can Unblock |
|---|---|
| "Waiting for GPU training to complete" | agent-a, agent-c |
| "Needs architecture decision" | agent-b, agent-d, captain |
| "Waiting for PR review" | any agent |
| "Blocked by EXP-XXX" | whoever finishes that expedition |
| "Needs Captain input" | captain |
| "External dependency" | depends |
Unblocking
When you unblock an item:
- Remove the
> **BLOCKED**section from the file - Add Ship's Log entry: "Unblocked: [what changed]"
- Move status:
yurtle-kanban move EXP-XXX in_progress
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?