Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/allbeads:blockedThe summary Claude sees in its command listing — used to decide when to auto-load this command
Show beads that are blocked by dependencies across all AllBeads contexts. Run `allbeads blocked` to find issues that cannot proceed due to blockers. For each blocked issue, show: - Bead ID and title - What it's blocked by - Context (repository) This helps identify: - Cross-repo blocking relationships - Bottlenecks in the workflow - Issues that need attention to unblock downstream work
Show beads that are blocked by dependencies across all AllBeads contexts.
Run allbeads blocked to find issues that cannot proceed due to blockers.
For each blocked issue, show:
This helps identify:
npx claudepluginhub thrashr888/allbeads --plugin allbeads/blockedShows all issues blocked by open dependencies. Inverse of bd ready; identifies stuck work and critical path items for dependency resolution.
/epic-unblockSweeps blocked epic issues and reopens any whose dependencies are closed. Updates labels, comments, and local snapshots.
/blockedLists blocked tasks from SonIA kanban board using Python helper script or project docs if needed. States if none exist and shows next recommended command.
/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.