prd-to-issueslisted

# PRD to Issues Break a PRD into independently-grabbable issues using vertical slices (tracer bullets), written as local markdown files. ## Process ### 1. Locate the PRD Ask the user for the PRD file path (e.g. `issues/prd.md`). If the PRD is not already in your context window, read it from 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. ### 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 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> ### 4. Quiz the user Present the proposed breakdown as a numbered list. For each slice, show: - **Title**: short descriptive name - **Type**: HITL / AFK - **Blocked by**: which other slices (if any) must complete first - **User stories covered**: which user stories from the PRD this addresses Ask the user: - Does the granularity feel right? (too coarse / too fine) - Are