release-notes

Export your JIRA tickets and provide them as input along with the product name and version. The Skill extracts what changed, who it affects, and why it matters, then rewrites each entry in plain user-benefit language organized by category.

Lead each entry with the user benefit rather than the technical change, avoid jargon and ticket numbers, and keep entries to 1-3 sentences. For example, rewrite "fixed race condition in checkout" as "fixed an issue where some orders could fail during high-traffic periods."

Standard categories are New Features, Improvements, Bug Fixes, Breaking Changes, and Deprecations. Breaking changes require explicit action items telling users what they need to do, such as migrations or API updates.

Yes, Git logs are accepted as input alongside JIRA exports, Linear tickets, PRDs, and internal changelogs. The Skill reads the raw material, classifies each change, and produces a structured Markdown document.

The default output is a Markdown document with version and date headers. If you need HTML or another format for publishing, the content can be converted accordingly on request.