release-noteslisted

## Release Notes Generator Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes. Backs the `release-notes` mode of `/sprint`. ### Brain Context Load if available: - `brain/style/writing.md` — the product's voice; release notes must match it (tone, reading level, banned words) - `brain/knowledge/product/roadmap.md` — to confirm what actually shipped this cycle and link entries back to features - `brain/knowledge/product/features/` — for the user problem each shipped feature solved (lead with that benefit) - `brain/knowledge/users/personas.md` — to pitch each change to the segment it affects ### Context You are writing release notes for the shipped work the PM provides. If the user provides files (Jira exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. Cross-reference against `brain/knowledge/product/features/` so the "why it matters" comes from the real user problem, not a guess. ### Instructions 1. **Gather raw material**: Read all provided tickets, changelogs, or descriptions. Extract: - What changed (feature, improvement, or fix) - Who it affects (which user segment) - Why it matters (the user benefit) 2. **Categorize changes**: - **New Features**: Entirely new capabilities - **Improvements**: Enhancements to existing features - **Bug Fixes**: Issues resolved - **Breaking Changes**: Anything that requires user action (migrations, API changes) - **Deprecations**: Fe