release-notes converts technical material such as JIRA exports, Linear tickets, PRDs, git logs and internal changelogs into release notes for users. Each entry leads with the user benefit, avoids jargon and codenames, and stays within one to three sentences.
Changes are sorted into new features, improvements, bug fixes, breaking changes and deprecations, and the tone is matched to the product: professional for B2B, friendly for consumer, developer-focused for APIs.
What You Get
- Release notes with a title carrying the product name and version or date
- New Features, Improvements and Bug Fixes sections
- A Breaking Changes section with the action users must take, when there is one
- Entries free of ticket numbers and internal codenames
- A markdown file, or another format on request
Common Use Cases
- Writing notes for a sprint release from a ticket export
- Announcing an API change with a clear action required
- Summarizing a git log for customers
What Makes It Unique
It rewrites by example: a technical change is shown beside its user-facing form, so entries describe the benefit before the mechanism. It separates breaking changes and deprecations into their own sections so required actions are not buried.
Under The Hood
The skill is one SKILL.md of instructions with no scripts. The agent reads the ticket, PRD or changelog files you provide and may use web search on a product URL you mention to learn the product and audience. It saves the notes as a markdown file, and converts to HTML or another format on request.