Menu
Synthesize current context into a PRD and file it as a Beads feature/epic issue.
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
Run red-green-refactor in vertical slices, emphasizing behavior-first tests and harness quality gates.
Break a plan/PRD into independent vertical-slice Beads issues with explicit dependencies.
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.
| name | to-prd |
| description | Synthesize current context into a PRD and file it as a Beads feature/epic issue. |
Turn the current conversation and codebase context into a practical PRD without running a long interview.
Use what already exists in:
bd show <id>)knowledge/Ask clarifying questions only when a blocker prevents writing a useful PRD.
Identify major modules likely to be added/changed. Prefer deep modules (simple interface, hidden complexity).
Record:
Use this template:
## Problem StatementDescribe the user-facing problem in plain language.
Describe the intended user-facing outcome and core approach.
Provide a numbered, comprehensive set of stories:
Capture important decisions:
Do not hard-code exact file paths unless required.
Capture testing strategy:
Explicitly list exclusions for this increment.
Any assumptions, risks, migration notes, or open questions.
Create an issue in this harness (or target sub-repo when appropriate):
bd create --type feature --title "<PRD title>" --description "<full PRD markdown>" --priority 2 --repo .
If scope is multi-feature or strategic, use --type epic instead.
If implementation tasks are obvious, create child beads under the PRD issue:
bd create --type task --parent <prd-id> --title "<slice>" --description "<vertical slice>" --priority 2 --repo .
Add a worklog: comment summarizing key decisions.