skills.rest
lfuuu
lfuuuCOMMUNITY
Explore all skills by this author →
GitHub

prd-to-plan

Converts a PRD into a multi-phase implementation plan using vertical tracer-bullet slices.

Updated Jun 2, 2026
Search Tags:#markdown#project planning#implementation plan#prd#phases#vertical slice#tracer bullet
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill prd-to-plan-lfuuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-plan
Source: https://github.com/lfuuu/claude-rules/tree/main/global-skills/prd-to-plan
Command: npx skills add https://github.com/lfuuu/claude-rules --skill prd-to-plan-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a product requirements document into an actionable engineering plan is slow and error-prone, and horizontal layer-by-layer breakdowns often produce phases that cannot be tested or demonstrated independently. ## Core Features & Use Cases - Vertical Slice Decomposition: Splits a PRD into thin tracer-bullet phases that cut through all integration layers (schema, API, UI, tests) so each phase is independently demonstrable. - Stable Architecture Capture: Records durable decisions like route patterns, schema shapes, and data models in the plan header so every phase can reference them. - Interactive Refinement: Presents the proposed phase breakdown for user review and iterates on granularity before writing the final Markdown plan to ./plans/. - Use Case: After drafting a PRD for a user onboarding feature, run this Skill to produce ./plans/user-onboarding.md with phased acceptance criteria ready for implementation. ## Quick Start Ask the assistant to break the PRD in the current conversation into a phased implementation plan using vertical slices and save it to ./plans/.

Frequently Asked Questions about prd-to-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD into an implementation plan?▼

Provide the PRD in the conversation and invoke the prd-to-plan skill. It explores the codebase, identifies stable architectural decisions, proposes vertical-slice phases for your approval, then writes a Markdown plan to ./plans/.

What is a vertical slice or tracer bullet in project planning?▼

A vertical slice is a thin end-to-end increment that passes through all integration layers (schema, API, UI, tests) rather than completing one horizontal layer at a time. Each finished slice can be demonstrated and verified independently.

Where does the generated implementation plan get saved?▼

The plan is written as a Markdown file in the ./plans/ directory, named after the feature, such as ./plans/user-onboarding.md. The directory is created automatically if it does not exist.

Can I adjust the phase breakdown before the plan is written?▼

Yes. The skill presents the proposed phases as a numbered list with covered user stories and asks whether the granularity is right. You can request merging or splitting phases, and it iterates until you approve.

What are the limitations of vertical slice planning?▼

Vertical slices avoid naming specific files or functions, so implementation details are decided during each phase. The approach also requires the PRD to be available in context and works best when stable architectural decisions can be identified upfront.

Related Skills

Explore More Product & Management Skills→
d3mingd3ming

write-a-prd

Draft product requirements documents from user interviews and repository inspection.

Community
Advanced
fuxiang123fuxiang123

prd-to-issues

Convert PRDs into GitHub issues with tracer-bullet vertical slices.

Community
Intermediate
h4vzzh4vzz
33

Project Management

Create and manage software project plans with task breakdowns and status reports.

Community
Advanced
vickysrawatvickysrawat
1

ado-tasks

Generates Azure DevOps task breakdowns from approved ICEA documents per architecture layer.

Community
Advanced