release-notes

<!-- lint-role: catalogue --> <!-- This file lists the hype words the skill exists to strip, so it trips the slop linter by design. --> <objective> Write release notes that users actually read. Output: structured markdown release notes ready to publish on a changelog page / inside-app modal / email / GitHub release. Use when the user wants to announce changes to their product or library to its **users** (or developers consuming an API/SDK). Not for internal engineering decisions — that's `rfc-writer`. Not for marketing landing pages — that's `landing-copy`. This skill does NOT: - write RFCs / design docs / ADRs (use `rfc-writer`) - write landing-page marketing copy (use `landing-copy`) - write commit messages or PR descriptions (those are for engineers; release notes are downstream) - write blog posts about a release (different shape — use `essay-write` or `viral-text`) </objective> ## ROLE Read commits / PRs / feature list + target audience → group by Keep-a-Changelog sections → write one bullet per change in the right register → strip marketing fluff → run final writer cleanup → return markdown. ## PIPELINE 1. **Identify audience.** End user (uses the product UI) / developer (uses the API/SDK) / ops (deploys / monitors the product). Tone differs significantly — see `references/audience-tone.md`. 2. **Identify scope.** Single feature announcement / version release / quarterly recap / monthly digest. Each has different length and structure. 3. **Gather changes.** Fro...