Individual skill
release-notes
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.
pm-execution/skills/release-notes/SKILL.md
Source commit 2a12295a7717569baa7be181b4cfebe3ca38a6bb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27,849
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skill-repository Repository topic
- product-management Repository topic
- agent-skills Repository topic
- agentic-skills Repository topic
- claude-code-marketplace Repository topic
- claude-code-plugins Repository topic
- claude-cowork-plugin Repository topic
- writing Derived category
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,569 bytes
Read excerpt
## Release Notes Generator
Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.
### Context
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.
### Instructions
1. **Gather raw material**: Read all provided tickets, changelogs, or descriptions. Extract:
- What changed (feature, improvement, or fix)