deliver-release-notes

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Release Notes Release 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. ## When to Use - Shipping product updates to customers - Communicating changes to internal stakeholders - Preparing app store update descriptions - Writing customer-facing email announcements - Documenting changes for support and sales teams ## When NOT to Use - You are updating internal stakeholders on progress rather than announcing shipped changes -> use `foundation-stakeholder-update` - You need the technical record of changes for developers -> keep the engineering changelog; this skill translates changes into user benefits - You are coordinating launch readiness rather than communicating the ship -> use `deliver-launch-checklist` - 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 ## Instructions When asked to create release notes, follow these steps: 1. **Gather the Changelog** Collect all changes included in this release: features, improvements, and bug fixes. Work from engineering changelogs, completed tickets, or pul...