release-noteslisted

# Release Notes ## When to use Invoke this skill when tagging a release, writing a GitHub release, or announcing a change to users. ## Steps 1. Gather the diff/CHANGELOG since the last release and the linked issues. 2. Lead with the one or two changes users will care about most. 3. Use plain language: what's new, what changed, what to watch for (breaking changes). 4. Add upgrade steps when behaviour or config changed. 5. Keep it skimmable: short paragraphs or a bulleted list with links. ## Examples - "Draft release notes for v2.0" - "Write a launch post for this feature" ## References Write for the reader who skipped the changelog; call out breaking changes and required actions prominently.