prd-to-issues

To break a PRD into GitHub issues, apply tracer-bullet vertical slices to decompose requirements into end-to-end, verifiable tasks spanning API, UI, and data layers with clear dependency orders.

Tracer-bullet vertical slicing is a planning technique that converts a PRD into small, independently-grabbable, testable implementation steps spanning all integration layers to streamline execution and traceability.

You organize GitHub issues from a PRD by generating vertical slices classified as HITL or AFK, ensuring each work item is verifiable and mapped with a clear dependency order across integration layers.

Classify PRD tasks as HITL (human-in-the-loop) or AFK (automatic, non-blocking) during vertical slice creation to balance execution speed and governance within your GitHub issues.

Yes, you can use a PRD GitHub issue number or URL as the direct input to begin drafting end-to-end vertical slices and automatically generate actionable execution tickets.

You should slice PRD work items across API, UI, and data layers when you need independently-grabbable GitHub issues that provide end-to-end traceability and verifiable implementation steps.