prd-to-issueslisted

# PRD to Issues Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets). ## Invocation Position This is a primary pipeline skill that normally follows `/write-a-prd` and precedes `/execute`. Use `/prd-to-issues` when a PRD is already shaped and you need implementation-ready slices with clear contracts between them. Do not use it as a substitute for shaping. If the PRD is still changing at the level of solution direction, rabbit holes, or appetite, go back to `/write-a-prd` first. ## Process ### 1. Locate the PRD Ask the user for the PRD GitHub issue number (or URL). If the PRD is not already in your context window, fetch it with `gh issue view <number>` (with comments). **Check for milestone.** After fetching the PRD, check whether it belongs to a GitHub milestone: `gh issue view <number> --json milestone`. If a milestone exists, note the milestone title for use in Step 6 — all slice issues should be attached to the same milestone. ### 2. Explore the Codebase (optional) If you have not already explored the codebase, do so to understand the current state of the code. ### 3. Draft Vertical Slices 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