prd-to-issues

To convert a PRD into GitHub issues, this tool decomposes product requirement documents into structured implementation tickets using vertical slice planning. It maps user stories, defines acceptance criteria, and establishes dependency relationships for actionable delivery planning.

Vertical slice planning breaks product requirements into tracer-bullet issues that deliver complete end-to-end functionality. This technique ensures engineering tasks remain independently implementable without losing user outcomes during PRD decomposition.

Break down product requirements by applying issue planning workflow steps: dependency analysis, HITL and AFK classification, and iterative review. This generates user story mappings with linked dependencies before GitHub ticket creation.

Task breakdown requires defining acceptance criteria for each implementation issue. The workflow guides you through specifying these criteria alongside user story mappings and issue templates to ensure independently grabbable engineering work items.

Yes, the issue planning workflow explicitly supports iterative review before GitHub ticket creation. It guides dependency analysis and task classification, allowing product teams to validate structured implementation issues against the approved PRD.

Avoid vertical slice planning for PRD decomposition when product requirements lack clear user outcomes or when engineering tasks cannot be structured into independently implementable tracer-bullet issues delivering end-to-end functionality.