Break a PRD into independently-grabbable local issue files using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
Break a PRD into independently-grabbable issue files using vertical slices (tracer bullets).
The PRD should already be in the conversation. If it isn't, ask the user to point you to the file (e.g. ./prds/0001-user-authentication/PRD.md).
Read the PRD frontmatter to get the id — you will need it to set the prd field in each issue and to determine the output directory.
If you have not already explored the codebase, do so to understand the current state of the code.
Break the PRD into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
<vertical-slice-rules> - Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones </vertical-slice-rules>Present the proposed breakdown as a numbered list. For each slice, show:
Ask the user:
Iterate until the user approves the breakdown.
Storage rules:
./prds/NNNN-slug/ (same directory as the PRD)ISSUE-NNN-*.md, taking the max numeric prefix + 1. Default to 001 if none exist.001, 002...)ISSUE-NNN-slug.md where slug is the title lowercased, hyphenated, max 50 chars at word boundaryblocked_byIssue file frontmatter:
---