**User stories**: <list from PRD> ### What to build  ### Acceptance criteria - [ ] Criterion 1 - [ ] Criterion 2 - [ ] Criterion 3 ---  </plan-template>

# Prd To Plan > Turns a PRD into a phased implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets". - Skill: `rockclaver/prd-to-plan` (Agent Skill) - Install (CLI): `npx skillmds@latest add rockclaver/prd-to-plan` - Raw SKILL.md: https://api.skillmd.com/api/skills/rockclaver/prd-to-plan/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - Author: rockclaver (https://skillmd.com/u/rockclaver) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/rockclaver/prd-to-plan --- # PRD to Plan Break a PRD into phased vertical slices (tracer bullets) saved in `./plans/`. ## Process 1. Confirm PRD is in context; else ask the user for it. 2. Explore the codebase: architecture, patterns, integration layers. 3. Note durable decisions (routes, schema, models, auth, integrations). 4. Draft tracer-bullet phases cutting through ALL layers end-to-end, not one. - Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones - Do NOT include specific file/function names likely to change in later phases - DO include durable decisions: route paths, schema shapes, data model names 5. Quiz the user: list phases (title + stories), confirm granularity, iterate. 6. Write `./plans/.md` per the template below. # Plan: > Source PRD: ## Architectural decisions - **Routes**: ... - **Schema**: ... - **Key models**: ... - (add/remove as needed) --- ## Phase 1: **User stories**: <list from PRD> ### What to build  ### Acceptance criteria - [ ] Criterion 1 - [ ] Criterion 2 - [ ] Criterion 3 ---  </plan-template>