prd-to-issueslisted

# prd-to-issues Break a refined PRD into milestones and fully-specified GitHub issues that cold agents can implement one at a time. Every issue must be self-sufficient: an agent holding only the issue body and the PRD can build it correctly. **Load the `github-issue-format` skill before filing anything — mandatory.** ## Steps ### 1. Plan the breakdown (present before filing) - Derive **milestones** from dependency structure, not feature themes. Typical shape: `v0 — Foundation & core <surface>` (scaffold, schema, auth, core domain flows, payments happy path), `v1 — Lifecycle & delivery` (jobs, schedulers, notifications, end-of-life), `v2 — <second surface> parity`, `v3 — Post-MVP`. - Aim for **15–25 issues** total; each independently implementable and PR-sized. - Identify the **dependency spine** (issues everything else needs, built serially) vs **parallel waves** (dependency-free islands). For each planned issue, record its direct hard prerequisites separately from ordering-only predecessors. Name the risk concentrators — usually the schema and the money/pricing module. - Show the user the plan (titles, milestones, order) in chat before filing. Adjust on feedback. ### 2. Create milestones `gh api repos/<owner>/<repo>/milestones -f title='...' -f description='...'` — one per phase, descriptions listing the member issues' themes. ### 3. Write the issues Per `github-issue-format`: `[C<score>]` plain-language title, complexity rationale first line, then **Problem** (with