Plan to Issues (To Issues)

To convert a PRD into implementation tickets, break the specification into vertically sliced tracer-bullet issues that cut through UI, API, and DB layers. This produces tracker-ready tickets with explicit dependencies and acceptance criteria for incremental delivery.

Vertical slicing in project planning breaks work into independently implementable tracer-bullet issues spanning UI to DB. It maps dependencies by defining blocked-by relationships, establishing a logical build order for implementation sequencing.

Label issue tickets using HITL (Human-in-the-Loop) and AFK (Away From Keyboard) tags. This separates tasks requiring human review from automated execution, clarifying execution readiness and incremental delivery expectations across integration layers.

Yes, PRD translation applies across UI, API, and DB integration layers. The process generates tracer-bullet issues that cut through these layers, ensuring end-to-end value delivery rather than fragmented tasks.

The best way to sequence implementation issues is by defining explicit blocked-by relationships during issue planning. This establishes dependency order, preventing stale tasks and ensuring logical build sequencing across integration layers.

To avoid stale hardcoded file paths when planning tracker-ready issues, generate tickets with acceptance criteria focused on integration layers rather than specific file locations. This maintains execution readiness as the codebase evolves.