Write release notes with AI
Explain completed changes through the outcomes your audience can actually see
Write release notes with AI by explaining what users can now do or which problem has been fixed. The po-release-notes skill takes completed work items, groups related changes into meaningful themes and drafts versions for customers, business colleagues or technical readers. The emphasis is the visible outcome rather than a list of implementation activities.
Inputs can be supplied manually or read through existing authorised Jira or Azure DevOps connections. Unfinished work should not appear as delivered functionality, and bug fixes remain distinct from new features. The output is a reviewable draft, not evidence that a release reached production. Posting or sending it requires a separate supported destination and request.
What it does
- Group changes by user-facing capability
- Describe fixes through their previous symptoms
- Separate new features from corrections
- Tailor technical detail to each audience
- Include relevant known limitations
- Prepare separate customer and internal versions
Install and use
- Load the folder and licence in a compatible agent such as Claude Code. Provide the version or period, audience and completed items; the manual route needs no project-management account, and the host processes supplied information.
- For example: “Write customer release notes for this reporting update. Separate the new CSV export from the date-display fix and exclude the unfinished item.”
- Review titles, types and descriptions. Optional authorised Jira or Azure DevOps connectors can gather them; verify completion and visible effects against actual release evidence.
- Check each audience version for accuracy, jargon and limitations. Prepare the final text for your chosen destination; publishing, uploading and sending remain separate actions.
FAQ
Source
Made by abrahamFerga. Original skill: po-release-notes, published on GitHub under the MIT licence.
View on GitHub