Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From pm-execution
Generates user-facing release notes from tickets, PRDs, or changelogs. Categorizes changes into new features, improvements, fixes for announcing updates.
npx claudepluginhub phuryn/pm-skills --plugin pm-executionHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-execution:release-notesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.
Generates user-facing release notes from tickets, PRDs, changelogs, or Git logs. Organizes into categories like new features, improvements, bug fixes for product announcements.
Generates user-facing release notes from tickets, PRDs, changelogs, or Git logs. Categorizes into new features, improvements, bug fixes with benefit-focused summaries for product updates.
Generates user-facing release notes from changelogs, translating technical changes into user benefits for features, improvements, and fixes. Use when shipping updates to users or stakeholders.
Share bugs, ideas, or general feedback.
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.