prd-to-issues

To break a PRD into vertical slices for TDD implementation, the Skill generates thin, end-to-end slices that traverse schema, API, UI, and test layers. It organizes these slices with deterministic numbering and explicit dependency ordering to ensure correct sequencing.

Vertical-slice issues are independently-grabbable work units that cover all layers of an application end-to-end, including schema, API, UI, and tests. They ensure each slice delivers complete functionality and is ready for immediate development.

Yes, you can reference real issue IDs when establishing dependencies. The Skill enforces deterministic numbering and dependency ordering, allowing each generated vertical slice to indicate precise prerequisite relationships using actual issue identifiers.

Yes, the PRD breakdown handles collaboration and deployment readiness by labeling each vertical slice as either HITL (Human-in-the-Loop) or AFK (Away-from-Keyboard). This clarifies exactly which issues require manual intervention versus automated processing.

The best way to organize PRD issues for end-to-end delivery is by applying deterministic numbering and explicit dependency ordering across thin vertical slices. This preserves correct integration sequencing and ensures every layer from schema to UI is covered.

Yes, you need an existing PRD to generate ready-to-implement issues. You must paste the PRD directly or provide a reference ID so the breakdown process can extract and structure the vertical slices across all required technical layers.