prd-to-issues

To convert a PRD into actionable development issues, this Skill slices an approved PRD file into minimal, testable tracer-bullet issue files with end-to-end traceability to success criteria. It generates the issue list and writes files only after human approval.

Human-in-the-loop gating for product issue planning works by presenting a generated slice plan for your explicit approval before writing any issue files. This preserves review control and ensures you validate traceability and dependencies before changes are committed.

The best way to trace issues back to PRD success criteria is by slicing the approved PRD into tracer-bullet issues that enforce end-to-end traceability. Each generated issue file maps directly to the defined success criteria and includes dependency tagging.

Yes, you need an approved PRD file located at features/<slug>/prd.md to slice it into issues. After approval, the Skill writes the structured tracer-bullet issue files into the corresponding features/<slug>/issues/ directory.

No, you cannot automate writing issue files without manual review because this Skill enforces a mandatory HITL gate. It always presents the slice plan for human approval before creating any files to preserve review control over the workflow.

Tracer-bullet issues are used for product management planning to convert PRD criteria into minimal, testable slices that trace to success criteria. This approach enforces dependency tagging and structured output for better project traceability.