deliver-release-notes

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Release Notes
3 
4Release notes communicate product changes to users in a way that highlights value and builds excitement. Unlike changelogs (which document what changed technically), release notes translate changes into user benefits. Good release notes help users discover new capabilities, understand improvements, and trust that issues are being addressed.
5 
6## When to Use
7 
8- Shipping product updates to customers
9- Communicating changes to internal stakeholders
10- Preparing app store update descriptions
11- Writing customer-facing email announcements
12- Documenting changes for support and sales teams
13 
14## When NOT to Use
15 
16- You are updating internal stakeholders on progress rather than announcing shipped changes -> use `foundation-stakeholder-update`
17- You need the technical record of changes for developers -> keep the engineering changelog; this skill translates changes into user benefits
18- You are coordinating launch readiness rather than communicating the ship -> use `deliver-launch-checklist`
19- Nothing user-visible shipped (a pure internal refactor): release notes that stretch to find a benefit erode trust; skip the cycle or fold it into the next one
20 
21## Instructions
22 
23When asked to create release notes, follow these steps:
24 
251. **Gather the Changelog**
26…