prd-to-plan

Convert a PRD into a multi-phase implementation plan saved as Markdown.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/raphaelmans/agent-skills --skill prd-to-plan-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-plan
Source: https://github.com/raphaelmans/agent-skills/tree/main/prd-to-plan
Command: npx skills add https://github.com/raphaelmans/agent-skills --skill prd-to-plan-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a Product Requirements Document (PRD) into a structured, multi-phase implementation plan using durable vertical slices, saved as a local Markdown file in ./plans/.

Core Features & Use Cases

  • Vertical-slice planning: Decompose PRDs into end-to-end slices that cut across architecture, API, UI, and tests.
  • Durable decisions: Capture decisions like routes, schemas, data models to guide future work.
  • Use Case: When a team has a PRD and needs a concrete, phased plan to guide development and milestones.

Quick Start

Paste your PRD and I will generate a multi-phase tracer-bullet plan saved in ./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 convert a PRD into a phased implementation plan?

Vertical-slice planning decomposes a PRD into end-to-end slices that cut across architecture, API, UI, and tests. This approach captures durable decisions like routes, schemas, and data models to guide future development work and milestones.

What's the best way to break down product requirements into vertical slices?

Yes, tracer-bullet plans enforce durable decisions by explicitly capturing routes, schemas, and data models during decomposition. These decisions are documented within the generated Markdown file to guide subsequent development phases.

Where does the generated PRD plan file get saved?

The generated PRD plan file is saved as a local Markdown file in the ./plans/ directory. This ensures the structured, multi-phase implementation plan is readily accessible for local development and version control.

Do I need any specific dependencies to generate a plan from a PRD?

No specific dependencies are required to generate a plan from a PRD. You simply need to paste your Product Requirements Document to produce the structured Markdown plan file output in your local environment.