prd-to-issues
PRD to Issues
Break a PRD into independently-grabbable local Markdown issue files using vertical slices (tracer bullets).
The generated issues must be junior-developer-ready: each issue should explain what to build, why the work is ordered that way, what to verify, and what assumptions or pitfalls to avoid. A junior developer should be able to pick up a single AFK issue without rereading the whole conversation.
Process
1. Locate the PRD
Ask the user for the PRD file path (e.g. docs/prds/<slug>.md).
If the PRD is not already in your context window, read the file.
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. Use the project's domain vocabulary consistently, and respect any existing ADRs or architecture docs in the area being changed.