prd-to-plan

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD into a build order often produces horizontal task lists that defer integration risk until late in the project. This Skill sequences work into vertical slices so each phase is demoable and de-risks the next. ## Core Features & Use Cases - Tracer-bullet slicing: Designs thin vertical slices that cut through all integration layers, with the first slice proving the riskiest assumption. - Four anchors per slice: Every slice gets a design anchor, data anchor, done anchor, and process anchor tied to the to-be process map, plus a Leaf node or Core architecture classification. - Deliverables and phase records: Groups slices into Screen, Logic, and Integration deliverables, writes phase records, and updates docs/backlog.md with exact section headers. - Use Case: After design review, you have a backlog of Ready slices and a to-be process map. Invoke this Skill to produce an approved phased plan with deliverables, then optionally convert it into GitHub issues in dependency order. ## Quick Start Ask the AI to turn the approved PRD into a phased implementation plan using the slices in docs/backlog.md and the to-be process map.

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?

Read the backlog, to-be process map, and tech context, then map each Ready slice to a process step, design vertical tracer-bullet slices, group them into deliverables, and sequence phases by risk and process order. The approved plan is written back into docs/backlog.md.

What is a tracer-bullet vertical slice in software planning?

A tracer-bullet slice cuts through all integration layers end-to-end, delivering a narrow but complete and demoable path. The first slice must prove the riskiest assumption, and horizontal slices like building all database models first are not allowed.

When should a slice be classified as Core architecture?

Classify a slice as Core architecture when it defines a data model, implements shared logic, sets up infrastructure, or is listed as a dependency by other slices. When uncertain, default to Core architecture, which triggers principal engineer review before build.

Can integration deliverables be planned before data questions are resolved?

No. If the data questions log has open entries, the integration deliverable cannot be fully scoped. Resolve the questions through a research spike or direct API check before defining that deliverable.

What happens if the to-be process map is missing?

The process stops. The to-be process map is the sequencing foundation, and without it slices would be ordered by comfort rather than by the process they implement.