prd-to-issues

To break down a PRD into GitHub issues, you provide the PRD's issue number or URL to generate a tracer-bullet breakdown of actionable items. This process organizes product requirements into independently-grabbable vertical slices covering schema, API, UI, and tests.

Tracer-bullet vertical slices are deterministic, end-to-end work items that cut across all project layers including schema, API, UI, and tests. This slicing technique enables precise implementation planning by creating independently-grabbable issues for coordinated development.

Yes, you can convert product requirements into implementable work items for projects of varying sizes. The breakdown supports creating deterministic, end-to-end slices with structured GitHub issue formats ready for creation and coordinated development.

You generate actionable GitHub issues by supplying the PRD's GitHub issue URL. The system then parses the requirements and outputs a structured GitHub issue format, classifying slices as HITL or AFK and defining blockers and user stories coverage.

Yes, the generated GitHub issue format includes blockers and user stories coverage. It classifies the tracer-bullet vertical slices as HITL or AFK types and defines these elements to ensure the issues are ready for coordinated development.

The best way to slice product requirements across code, tests, and UI is using tracer-bullet vertical slices. This approach creates deterministic, end-to-end slices that cover all layers, ensuring each generated GitHub issue is independently-grabbable and ready for implementation.