Release Notes

Turn shipped work, a version bump, or a rough change list into clear release notes tailored to the audience.

Core rule

• Lead with what changed for the reader, not how the team built it.
• Default audience is external: write for customers who do not know your stack, sprint names, or internal systems.
• Strip internal-only work from external notes unless it has a direct customer effect.
• Translate engineering changes into user-visible outcomes before drafting.
• One release note should read like one coherent announcement, not a dump of tickets
• Do not publish laundry lists of platforms, pages, browsers, or variants when one consolidated bullet will do

Audience modes