patch-notes

## Phase 1: Parse Arguments - `version`: the release version to generate notes for (e.g., `1.2.0`) - `--style`: output style — `brief` (bullet points), `detailed` (with context), `full` (with developer commentary). Default: `detailed`. If no version is provided, ask the user before proceeding. --- ## Phase 2: Gather Change Data - Read the internal changelog at `production/releases/[version]/changelog.md` if it exists - Also check `docs/CHANGELOG.md` for the relevant version entry - Run `git log` between the previous release tag and current tag/HEAD as a fallback - Read sprint retrospectives in `production/sprints/` for context - Read any balance change documents in `design/balance/` - Read bug fix records from QA if available **If no changelog data is available** (neither `production/releases/[version]/changelog.md` nor a `docs/CHANGELOG.md` entry for this version exists, and git log is empty or unavailable): > "No changelog data found for [version]. Run `/changelog [version]` first to generate the > internal changelog, then re-run `/patch-notes [version]`." Verdict: **BLOCKED** — stop here without generating notes. --- ## Phase 2b: Detect Tone Guide and Template **Tone guide detection** — before drafting notes, check for writing style guidance: 1. Check `.claude/docs/technical-preferences.md` for any "tone", "voice", or "style" fields or sections. 2. Check `docs/PATCH-NOTES-STYLE.md` if it exists. 3. Check `design/community/tone-guide.md` if it exists. 4. If a...