Skills
Release notes format skill
User-impact ordering, migration steps for breaking changes, and zero internal jargon.
Last reviewed July 17, 2026
A single-file skill template fixing the release notes format: impact-first ordering, the entry shape, and rules that keep internal jargon out.
SKILL.md
# Release notes format Apply when writing release notes or changelog entries. ## Ordering Breaking changes (with migration steps and dates), then new capabilities, then notable fixes, then a one-line everything-else. Never chronological, never by internal module. ## Entry shape Each entry: what changed in user vocabulary, who it affects, what to do (nothing, opt in, migrate by date). Lead with the user-visible effect, not the mechanism: "Exports finish in seconds on large workspaces" beats "Optimized export query batching". ## Rules - No internal codenames, ticket numbers, or team names. - A fix entry names the symptom users saw, not the bug's cause. - Refactors appear only when users can feel them, described by the felt change. - Dates are absolute (July 2026), never "recently". - Anything too cryptic to translate goes back to its author under "needs a human sentence"; never ship gibberish.
Set it up
- 1
Copy the skill body
Adjust ordering and shape to your product's conventions; keep the user-vocabulary rule non-negotiable.
- 2
Create the skill
Add it in the workspace Skills page; the release notes writer agent applies it automatically.