ReddRadar
Agent skill
prd-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Install this agent skill to your Project
npx add-skill https://github.com/bamecho/my-claude-skills/tree/main/skill-en/prd-to-plan
SKILL.md
PRD to Plan
Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in ./plans/.
Process
1. Confirm the PRD is in context
The PRD should already be in the conversation. If it isn't, ask the user to paste it or point you to the file.
2. Explore the codebase
If you have not already explored the codebase, do so to understand the current architecture, existing patterns, and integration layers.
3. Identify durable architectural decisions
Before slicing, identify high-level decisions that are unlikely to change throughout implementation:
- Route structures / URL patterns
- Database schema shape
- Key data models
- Authentication / authorization approach
- Third-party service boundaries
These go in the plan header so every phase can reference them.
4. Draft vertical slices
Break the PRD into tracer bullet phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
5. Quiz the user
Present the proposed breakdown as a numbered list. For each phase show:
- Title: short descriptive name
- User stories covered: which user stories from the PRD this addresses
Ask the user:
- Does the granularity feel right? (too coarse / too fine)
- Should any phases be merged or split further?
Iterate until the user approves the breakdown.
6. Write the plan file
Create ./plans/ if it doesn't exist. Write the plan as a Markdown file named after the feature (e.g. ./plans/user-onboarding.md). Use the template below.
Source PRD:
Architectural decisions
Durable decisions that apply across all phases:
- Routes: ...
- Schema: ...
- Key models: ...
- (add/remove sections as appropriate)
Phase 1: <Title>
User stories: <list from PRD>
What to build
A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
Acceptance criteria
- Criterion 1
- Criterion 2
- Criterion 3
Phase 2: <Title>
User stories: <list from PRD>
What to build
...
Acceptance criteria
- ...
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
bamecho/my-claude-skills
decomposing-complex-problems
Deconstructs complex problems using the 'Polymath Investor' framework with a 5-step cognitive chain (First Principles → Modular Isolation → Pareto Filtering → Cross-Domain Mapping → Dynamic Zooming). Use when analyzing systems, architectures, businesses, or learning challenges; when seeking high-leverage insights or 'Alpha'; when applying first principles thinking; or when needing cross-disciplinary perspectives to reveal blind spots. Transforms overwhelming complexity into actionable levers.
bamecho/my-claude-skills
deep-analysis
Execute high-density architectural analysis on user ideas. Move from 'Vague' to 'Verified' using a 5-step logic chain: Calibration → Decomposition → Excavation → Re-Architecting → Inversion. This skill should be used when analyzing system architecture, validating technical ideas, or performing pre-mortems on solutions.
bamecho/my-claude-skills
nexus-prompt-engineer
4-D prompt engineering assistant that transforms vague requirements into high-precision prompts through guided interaction. Trigger when users need to: (1) craft high-quality system prompts, (2) optimize existing prompts, (3) use '/fast' for quick generation or '/audit' for prompt review. Applicable to any scenario requiring carefully designed prompts.
bamecho/my-claude-skills
round-table-analysis
Deep pre-execution analysis framework using four philosophers (Socrates, Aristotle, Feynman, Drucker) for structured critical thinking before implementing plans. Use when users need to thoroughly understand a topic, question assumptions, clarify objectives, or explore multiple perspectives before taking action. Triggered by phrases like "help me think through," "analyze this topic," "before we start," "I want to understand," or when complex decisions require deeper exploration.
bamecho/my-claude-skills
brainstorming
Use this when the user explicitly asks to brainstorm, or when the task is clearly about upfront design, solution exploration, or requirement shaping before implementation. Avoid loading it for routine implementation work unless that exploratory step is obviously needed.
bamecho/my-claude-skills
planning-with-files
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
Didn't find tool you were looking for?