to-issues

# to-issues — PRD/SPEC to Issues Decompose a PRD and/or technical SPEC into small, independent, implementable Issues, then create them in your chosen platform. Works standalone — you don't need to have run `/prd` first. --- ## The Job 1. **Locate input** — find a PRD or SPEC file (auto-detect or user-specified) 2. **Decompose into Issues** — break User Stories into implementable tickets 3. **Review with user** — present Issue list for approval and adjustment 4. **Choose platform** — GitHub / Local / Baidu iCafe 5. **Create Issues** — create all tickets and print summary --- ## Step 1: Locate Input Find the input document: ``` What should I base the Issues on? A. Auto-detect: scan tasks/ for recent PRDs and SPECs B. Specific PRD file (e.g., tasks/prd-priority-system.md) C. Specific SPEC file (e.g., tasks/spec-priority-system.md) D. Both PRD and SPEC (best: PRD for requirements, SPEC for technical contracts) E. Paste requirements directly ``` If auto-detecting, list available files and let the user choose. If both PRD and SPEC are available, use the SPEC's Section 10.2 (Issue Mapping) as the primary guide, supplemented by PRD's User Stories. If only PRD is available, generate Issues directly from User Stories. --- ## Step 2: Decompose into Issues Based on the input document(s), generate a list of Issues. Follow these rules: - **One Issue per User Story** — each US-XXX becomes at least one Issue - **Split large stories** — if a US has 5+ acceptance criteria or spa...