prd-to-plan

Convert a PRD into a multi-phase implementation plan with vertical slices.

6|3|Updated Sep 13, 2017
One-click install
npx skills add https://github.com/tomholford/dotfiles --skill prd-to-plan-tomholford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-plan
Source: https://github.com/tomholford/dotfiles/tree/main/claude/skills/prd-to-plan
Command: npx skills add https://github.com/tomholford/dotfiles --skill prd-to-plan-tomholford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

Core Features & Use Cases

  • Confirm the PRD is in context and available to the planning session.
  • Explore the repository to understand current architecture, patterns, and integration points.
  • Identify durable architectural decisions (routes, data models, APIs) to anchor every phase.
  • Draft vertical slices that end-to-end cover all layers and are easily demoable.
  • Quiz the user and refine phases until alignment is achieved.
  • Write the plan to ./plans/ using a structured Markdown template.

Quick Start

Paste your PRD in context and run the skill to generate a Markdown plan under ./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 a multi-phase implementation plan?

To turn a PRD into a multi-phase implementation plan, apply a tracer-bullet approach to draft vertical slices covering architecture, API, UI, and tests, then save the structured Markdown plan in ./plans/.

What are tracer bullets in product management planning?

Tracer bullets in product management planning are end-to-end vertical slices that validate routes, data models, and APIs early, ensuring each phase is easily demoable.

How do I document architecture decisions when breaking down a PRD?

Document architecture decisions when breaking down a PRD by identifying durable choices like routes, data models, and APIs to anchor every phase, recording them within a structured Markdown plan file.

Does generating a plan from a PRD require any specific dependencies?

Generating a plan from a PRD requires no external dependencies, but you must paste your PRD into context and have a local ./plans/ directory to save the resulting Markdown file.

Can I refine implementation phases after the initial plan is generated?

You can refine implementation phases because the planning process quizzes you to align vertical slices with your needs, allowing adjustments to architecture, API, and UI phases before finalizing the Markdown plan.