Menú
Show unblocked tasks ready to work on
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Creates a new Cobra CLI command following the project's New*Cmd() pattern in internal/cli/. Handles command registration in root.go, flag setup, output rendering, and test scaffolding. Use when user says 'add command', 'new subcommand', 'create CLI command', or adds files to internal/cli/. Do NOT use for MCP tools or hooks.
Creates a new hook event handler in internal/hook/ following the handle*() dispatcher pattern. Adds event constant to events.go, handler function, dispatcher case, and tests using fake bd binary. Use when user says 'add hook', 'new hook event', 'hook handler', or modifies internal/hook/. Do NOT use for MCP tools, CLI commands, or graph queries.
Creates a new MCP tool following the handle*() pattern in internal/mcp/. Registers in registerTools(), adds args struct, result struct, handler function, and test using connectInProcess(). Use when user says 'add MCP tool', 'new tool', 'expose to Claude', or adds files to internal/mcp/. Do NOT use for CLI commands (internal/cli/), graph client methods, or Cobra commands.
Build modular CLI applications with Cobra framework. Use when structuring CLI commands, implementing modular command architecture, handling flags and arguments, or when user mentions Cobra, CLI modularity, command registration, or spf13/cobra.
Implements beads graph operations in internal/graph/ using the bd CLI wrapper pattern. Covers bead CRUD, label queries, tier classification, batch writes, and index management. Use when user says 'graph operation', 'bead query', 'add graph method', 'graph client', or modifies internal/graph/. Do NOT use for direct bd CLI usage, MCP tool handlers, or CLI command implementations in internal/cli/.
Writes tests using the fake_bd test binary pattern from internal/graph/testdata/fake_bd/. Covers building fake binary, setting FAKE_BD_* env vars for canned responses, capture files for arg/env verification, and serverState/hookState setup. Use when user says 'write tests', 'add test', 'test coverage', or needs to test graph/mcp/hook code that calls bd. Do NOT use for tests that don't invoke the bd CLI binary (e.g., pure utility functions, config parsing, CLI flag tests).
| name | ready |
| description | Show unblocked tasks ready to work on |
| disable-model-invocation | false |
| argument-hint | [phase_number] |
Display unblocked tasks that are ready to execute. Phase number is $ARGUMENTS (optional — omit to show all phases).
Display unblocked tasks in GSD wave format. This is a thin wrapper over existing infrastructure. Never mention beads or graph structures to the developer.
Check if $ARGUMENTS contains a phase number. Store it for filtering in Step 3 if present.
Call the list_ready MCP tool with no arguments. It returns all ready beads across all phases.
Group results by phase and display in GSD wave format:
## Ready Tasks
### Phase {N}: {phase_title}
| Task | Title | Reqs |
|---------|--------------------------------|--------------|
| {plan_id} | {title} | {req_ids} |
If $ARGUMENTS contains a phase number, filter to show only that phase.
Include a summary line at the end: Total: {count} task(s) ready
If no tasks are ready, display:
No tasks ready. All tasks are either blocked by dependencies or already complete.
After displaying the table, display:
CLI alternative: gsdw ready
Or if a phase was specified:
CLI alternative: gsdw ready --phase {N}