skills.rest
mia-cx
mia-cxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

prd-to-plan

Break down PRDs into tracer-bullet vertical slices with Markdown plans in .plans.

Updated Mar 23, 2026
Search Tags:#workflow#planning#architecture#prd#project-management#planning-tools#vertical-slices
One-click install
npx skills add https://github.com/mia-cx/.agents --skill prd-to-plan-mia-cx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-plan
Source: https://github.com/mia-cx/.agents/tree/main/skills/prd-to-plan
Command: npx skills add https://github.com/mia-cx/.agents --skill prd-to-plan-mia-cx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a product requirement document into a clear, end-to-end implementation plan using tracer-bullet vertical slices. Outputs one Markdown file per slice in .plans/, keeping plans as working documents (gitignored) that guide multi-phase delivery.

Core Features & Use Cases

  • Vertical-slice planning: each slice covers all layers (schema, API, UI) end-to-end.
  • Durable architectural decisions: captures decisions to reference across phases.
  • Artifact generation: creates per-slice Markdown files and a root README with the dependency graph.

Quick Start

Paste your PRD into the chat and request a tracer-bullet plan to generate .plans/ slices.

Frequently Asked Questions about prd-to-plan

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

FAQPage Schema
How do I break down a PRD into actionable implementation plans?▼

Break down a PRD by generating tracer-bullet vertical slices that cover architecture, API, and UI end-to-end. This produces per-slice Markdown files in a local `.plans/` directory, guided by a root README for phased delivery.

What are tracer-bullet vertical slices in project planning?▼

Tracer-bullet vertical slices are implementation phases where each slice delivers functionality end-to-end across all layers, including schema, API, and UI. This approach ensures end-to-end traceability and captures durable architectural decisions for subsequent phases.

How do I plan phased delivery for a project with architecture and UI requirements?▼

Plan phased delivery by parsing your PRD to specify durable architectural decisions and generate per-slice artifacts. Each slice creates a working document covering end-to-end dependencies, resulting in a root plan README with a dependency graph.

Can I use this to generate working documents for multi-phase project delivery?▼

Yes, you can generate working documents for multi-phase delivery by pasting your PRD to request a tracer-bullet plan. The output creates individual Markdown files per slice in the `.plans/` directory, designed to be gitignored working documents that guide implementation.

What is the best way to maintain traceability across architecture, API, and UI layers?▼

Maintain traceability by generating vertical slices that capture durable architectural decisions and per-slice artifacts. This creates a root plan README with a dependency graph, ensuring end-to-end traceability across architecture, API, and UI throughout the phased delivery.

Related Skills

Explore More Product & Management Skills→
raphaelmansraphaelmans

prd-to-issues

Convert PRDs into vertical-slice GitHub issues with dependencies.

Community
Intermediate
scott-rcscott-rc

plan

Slice briefs into phased implementation plans with commit checkpoints.

Community
Advanced
silvainfmsilvainfm
2

project-planner

Generate requirements, design, and implementation plan documents with traceability.

Community
Intermediate
mark22013333mark22013333
9

plan

Execute plan-spec, plan-db, and plan-arch sequentially with user confirmation.

Community
Advanced