prd-to-issues

To break a PRD into actionable engineering issues, convert the document into numbered, dependency-ordered tickets using vertical slices that span schema, logic, API, UI, and tests. This produces independently-grabbable items for reliable team planning and assignment.

Vertical-slice issues are tracer-bullet tickets that span schema, logic, API, UI, and tests so each work item is independently demoable and testable. They provide a structured method to translate long-form PRD content into verifiable engineering tasks.

Identify blockers and dependencies during PRD conversion by sequencing the generated vertical-slice issues. The process tags each issue as HITL or AFK, establishes dependency order, and flags overly coarse slices that need splitting before implementation.

PRD to issue conversion applies directly to repository workflows where a product requirements document must be converted into implementation tickets and ordered work items. It produces dependency-ordered issues with acceptance criteria and verification steps for development planning.

Classify engineering tasks as HITL or AFK during task breakdown by tagging each vertical-slice issue generated from the PRD. This classification distinguishes human-in-the-loop items from automated tasks, establishing clear dependency order and targeted assignment.

The best way to ensure issues generated from a PRD are verifiable is using a reusable template that includes acceptance criteria, verification steps, and PRD references. This provides traceability and confirms each vertical-slice item is demoable and testable.