How this command is triggered — by the user, by Claude, or both
Slash command
/beads:blockedThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Blocked Issues > Show all issues that are blocked by dependencies. Use `beads blocked` to see which issues have blockers preventing them from being worked on. This is the inverse of `beads ready` - it shows what's NOT ready. Blocked issues have one or more dependencies with type "blocks" that are still open. Once all blocking dependencies are closed, the issue becomes ready and will appear in `beads ready`. Useful for: - Understanding why work is stuck - Identifying critical path items - Planning dependency resolution
Show all issues that are blocked by dependencies.
Use beads blocked to see which issues have blockers preventing them from being worked on. This is the inverse of beads ready - it shows what's NOT ready.
Blocked issues have one or more dependencies with type "blocks" that are still open. Once all blocking dependencies are closed, the issue becomes ready and will appear in beads ready.
Useful for:
npx claudepluginhub shaneholloman/beads --plugin beads/blockedShows all issues blocked by open dependencies, helping identify stuck work and critical path items.
/epic-unblockResolves blocked GitHub issues by analyzing dependencies, verifying block validity, suggesting unblocking steps, updating labels, and outputting next actions.
/blockedLists blocked tasks from the SonIA kanban board by running a continuity helper script, with a manual fallback to project docs.
/epic-unblockScans epic issues in a repository, checks each blocked epic's dependency list, and moves fully unblocked epics to ready, updating labels, comments, and local snapshots.
/blockedLists all blocked profiles from ~/.claude/counsel-blocklist.json in a table (Name | Reason | Blocked On). Shows 'No blocked profiles' if empty or missing, with /hope:block and /hope:unblock hints.