- name
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creat
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 phuryn/pm-skills --skill release-notes -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill release-notes -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill release-notes -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill 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/phuryn/pm-skills/tree/HEAD/pm-execution/skills/release-notesFrom the publisher
Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.
You are writing release notes for $ARGUMENTS.
If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.
Gather raw material: Read all provided tickets, changelogs, or descriptions. Extract:
Categorize changes:
Write each entry following these principles:
Example transformations:
Technical: "Implemented Redis caching layer for dashboard API endpoints"
User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."
Technical: "Fixed race condition in concurrent checkout flow"
User-facing: "Fixed an issue where some orders could fail during high-traffic periods."
Structure the release notes:
# [Product Name] — [Version / Date]
## New Features
- **[Feature name]**: [1-2 sentence description of what it does and why it matters]
## Improvements
- **[Area]**: [What got better and how it helps]
## Bug Fixes
- Fixed [issue description in user terms]
## Breaking Changes (if any)
- **Action required**: [What users need to do]
Adjust tone to match the product's voice — professional for B2B, friendly for consumer, developer-focused for APIs.
Save as a markdown document. If the user wants HTML or another format, convert accordingly.
© 2026 Skills Rack.
---name: release-notesdescription: Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries…---# pm-execution/skills/release-notes/SKILL.mdOverview
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
FAQ
Download pm-execution/skills/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/phuryn/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.