Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From beads
Lists unblocked issues ready for work, showing ID, title, priority, and type. Prompts to claim one and start work atomically via claim tool.
npx claudepluginhub gastownhall/beads --plugin beadsHow this command is triggered — by the user, by Claude, or both
Slash command
/beads:readybeads/commands/The summary Claude sees in its command listing — used to decide when to auto-load this command
Use the beads MCP server to find tasks that are ready to work on (no blocking dependencies). Call the `ready` tool to get a list of unblocked issues. Then present them to the user in a clear format showing: - Issue ID - Title - Priority - Issue type If there are ready tasks, ask the user which one they'd like to work on. If they choose one, use the `claim` tool to start work atomically. If there are no ready tasks, suggest checking `blocked` issues or creating a new issue with the `create` tool.
/figure-out-what-to-work-onSuggests the highest-priority unblocked task to work on next using P0-P4 order, checking blockers, questions, and dependencies first.
/pickupLists ready tasks by priority, recommends or accepts task-id, shows details/context/learnings, then starts the task.
/flux-statusDisplays current Flux board status: tasks in progress, blocked, ready to start, recently completed, plus next task suggestion based on impact and dependencies.
/workAuto-classifies tasks from descriptions, folder paths, or issue identifiers (GitHub/Jira/Azure DevOps) and routes to workflow orchestrators. Resumes existing tasks.
/readyPerforms full production readiness audit: analyzes app structure and features, runs Pest/PHP tests and Playwright UI tests, fixes issues, verifies deployment readiness.
Share bugs, ideas, or general feedback.
Use the beads MCP server to find tasks that are ready to work on (no blocking dependencies).
Call the ready tool to get a list of unblocked issues. Then present them to the user in a clear format showing:
If there are ready tasks, ask the user which one they'd like to work on. If they choose one, use the claim tool to start work atomically.
If there are no ready tasks, suggest checking blocked issues or creating a new issue with the create tool.