Release notes people read
Turns a changelog or list of merged PRs into short release notes written around what users can now do.
Use it when
Shipping weekly and the changelog reads like commit messages.
What you fill in
- changes Merged PRs, tickets or a raw changelog
- audience Who reads the notes
The prompt
Write release notes for audience from these changes: changes 1. A one-line headline for the most valuable change. 2. "New": up to 5 items, each starting with a verb the user does ("Export…", "Invite…"), one sentence each. 3. "Improved" and "Fixed": short bullets, merged where similar. 4. Leave out internal refactors, dependency bumps and anything a user cannot notice. Plain words, no hype, under 200 words. Before you answer, check your draft against every instruction above and fix anything that misses.
Why it works
- Frames each change as something the user can now do.
- Filters out invisible internal work.
- Hard word limit.