with one click
prd-to-plan
// Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.
// Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | prd-to-plan |
| description | Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan. |
| user-invocable | true |
| effort | high |
| argument-hint | [PRD issue number or paste PRD] |
| allowed-tools | Read, Grep, Glob, Bash, Agent |
$ARGUMENTS
Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in ./plans/.
/prd-to-plan [PRD issue number or description]
./plans/If not provided, ask for the PRD GitHub issue number or content. Fetch with gh issue view <number> if needed.
Use Agent (subagent_type=Explore) to understand current architecture, existing patterns, and integration layers.
Before slicing, identify decisions unlikely to change:
Break PRD into tracer bullet phases. Each phase is a thin vertical slice cutting through ALL layers end-to-end.
| Rule | Description |
|---|---|
| Complete path | Each slice delivers narrow but COMPLETE path through every layer (schema, API, UI, tests) |
| Demoable | A completed slice is demoable or verifiable on its own |
| Thin over thick | Prefer many thin slices over few thick ones |
| Durable | Do NOT include file names, function names, or implementation details likely to change |
| Include decisions | DO include durable decisions: route paths, schema shapes, data model names |
Present breakdown as numbered list. For each phase show:
Ask:
Iterate until approved.
Create ./plans/ if needed. Write as ./plans/{feature-name}.md.
# Plan: {Feature Name}
> Source PRD: #{issue-number}
## Architectural Decisions
Durable decisions that apply across all phases:
- **Routes**: ...
- **Schema**: ...
- **Key models**: ...
---
## Phase 1: {Title}
**User stories**: {list from PRD}
### What to build
Concise description of this vertical slice. End-to-end behavior, not layer-by-layer.
### Acceptance criteria
- [ ] Criterion 1
- [ ] Criterion 2
---
## Phase 2: {Title}
(repeat for each phase)
gh issue view <n> captures the body but not the comments. Crucial clarifications often live in the comments — include --comments or remind the user to paste important threads./prd-to-issues/write-a-prd/plan (general-purpose)/grill-me/refactor-plan (incremental commits, not tracer bullets)