- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-release-notes -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-release-notes -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-release-notes -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add product-on-purpose/pm-skills --skill deliver-release-notes -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/product-on-purpose/pm-skills/tree/HEAD/skills/deliver-release-notesFrom the publisher
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.
foundation-stakeholder-updatedeliver-launch-checklistWhen asked to create release notes, follow these steps:
Gather the Changelog Collect all changes included in this release: features, improvements, and bug fixes. Work from engineering changelogs, completed tickets, or pull request descriptions.
Identify the Highlights Select 1-3 changes that deserve top billing. These should be changes users will notice and care about most. Lead with the most impactful change.
Translate to Benefits Rewrite each change in terms of user value. Instead of "Added pagination to search results," write "Find what you need faster with improved search that handles large result sets." Focus on what users can now do or what's now better.
Categorize Changes Group remaining changes into clear categories: New Features, Improvements, and Bug Fixes. Within each category, order by impact (most valuable first).
Write Scannable Descriptions Each item should be 1-2 sentences. Lead with the benefit, optionally followed by the "how." Users scan release notes - make each line valuable.
Acknowledge Known Issues If there are known limitations or issues, be transparent. Users appreciate honesty, and it reduces support burden.
Tease Coming Soon (Optional) If appropriate, hint at what's coming next. This builds anticipation and shows momentum, but don't over-promise.
Use the template in references/TEMPLATE.md to structure the output. Complete release notes fill the template sections: Highlights; New Features; Improvements; Bug Fixes; Known Issues; Coming Soon (optional); and Feedback.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or st
---name: deliver-release-notesdescription: Creates user-facing release notes that communicate new features, improvements, and fixes in clear…---# skills/deliver-release-notes/SKILL.mdOverview
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.
FAQ
Download skills/deliver-release-notes/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/product-on-purpose/pm-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.