Menu
Break a plan/PRD into independent vertical-slice Beads issues with explicit dependencies.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | to-issues |
| description | Break a plan/PRD into independent vertical-slice Beads issues with explicit dependencies. |
Convert a plan, PRD, or feature brief into small, independently executable Beads tasks.
Use available material first:
bd show <id>)If user provides an external issue/URL, map it into local context before decomposition.
Each slice must be an end-to-end path through relevant layers (contract, logic, integration, verification), not a single-layer chunk.
Rules:
AFK: can execute without user interventionHITL: requires human decision/review checkpointPresent a numbered list with:
AFK/HITL)Refine until approved.
Create issues in dependency order so blockers exist first.
Use this issue body format:
## What to build Concise vertical-slice behavior description.Commands:
bd create --type task --title "<slice title>" --description "<template markdown>" --priority 2 --repo .
bd dep add <slice-id> --blocks <blocked-id>
If slices derive from a parent PRD/feature, attach children:
bd create --type task --parent <parent-id> --title "<slice title>" --description "<template markdown>" --priority 2 --repo .
bd children <parent-id> and/or bd graph)worklog: comment to parent summarizing decomposition decisionsRun red-green-refactor in vertical slices, emphasizing behavior-first tests and harness quality gates.
Synthesize current context into a PRD and file it as a Beads feature/epic issue.
Phase 2 of the Forge pipeline. Turn a research document into an implementation plan that is built around Beads issues and TDD. Reads plans/research/<slug>.md, designs the build, sets up red-green-refactor test strategy using the tdd skill, materializes a Beads epic/feature/tasks with dependencies and priorities, and defines demo/test checkpoints. Use when starting /forge-plan or the plan step of /forgemaster.
Fact-check an implementation plan against the real codebase and first-party documentation, flagging inaccuracies with what / why / evidence and a severity tier. Use when the user wants a plan reviewed or validated for accuracy, runs /review-plan, or wants a plan checked against real code before implementing. Accepts a Beads issue, a filesystem path, or a plan pasted into chat.
Phase 3 of the Forge pipeline. Execute the plan's Beads tasks with red-green-refactor TDD, committing per checkpoint and pausing at each natural stopping point so the user can run a live demo or test and see the work themselves. Use when starting /forge-implement or the implement step of /forgemaster.
Phase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.