Release Notes Expert

Overview

Transform raw technical changes -- tickets, changelogs, git logs, PRDs -- into clear, user-benefit-oriented release notes. This skill ensures every release communicates value to the right audience in the right tone.

When to Use

• Product Releases -- Announcing new versions to customers, partners, or internal stakeholders.
• Sprint Demos -- Summarizing what shipped for sprint review audiences.
• Changelog Maintenance -- Keeping a running log of changes across releases.
• Customer Communication -- Preparing release announcements for email, in-app, or documentation.

Methodology

Step 1: Gather Raw Input

Collect all changes from the release cycle:

• Jira/Linear tickets -- Completed stories, bugs, and tasks
• Git log -- Merge commits since last release tag
• PRD references -- Feature specs that shipped
• Hotfix records -- Emergency fixes deployed between releases

Step 2: Classify Each Change

Assign every change to exactly one category:

Classification rules:

• If a change adds something entirely new, it is a New Feature.
• If it makes something existing better (faster, easier, more reliable), it is an Improvement.
• If it fixes something that was wrong, it is a Bug Fix.
• If users must change their behavior, configuration, or integration, it is a Breaking Change.
• If a feature still works but will be removed later, it is a Deprecation.

Step 3: Rewrite for User Benefit

The most critical step. Every entry must lead with the benefit to the user, not the technical change.

Rewriting principles:

1. Lead with the outcome. What can the user do now that they could not before, or what is better for them?
2. Use plain language. Avoid internal jargon, code references, or implementation details.
3. Keep it to 1-3 sentences. One sentence for minor items, up to three for significant features.
4. Include context when needed. If users need to take action, tell them exactly what to do.

Before and after examples:

/v2/preferences

Red flags that an entry needs rewriting:

• Mentions a class name, function, or library
• Starts with "Refactored," "Migrated," or "Updated" without stating impact
• Uses acronyms the target audience would not know
• Describes what the team did instead of what the user gains

Step 4: Adjust Tone for Audience

Step 5: Assemble the Release Notes

Use the output template below. Include only categories that have entries -- do not show empty sections.

Output Template

# [Product Name] v[X.Y.Z] Release Notes

**Release Date:** [YYYY-MM-DD]

---

## New Features

- **[Feature Name]** -- [1-3 sentence description of user benefit]. ([TICKET-ID])

## Improvements

- **[Improvement Name]** -- [1-2 sentence description of what is better]. ([TICKET-ID])

## Bug Fixes

- **[Bug Fix Name]** -- [1 sentence describing what was broken and that it is now fixed]. ([TICKET-ID])

## Breaking Changes

> **Action Required:** The following changes require updates on your end.

- **[Change Name]** -- [Description of what changed and exactly what the user must do]. ([TICKET-ID])

## Deprecations

> **Planned Removal:** The following features will be removed in a future release.

- **[Feature Name]** -- [What is being deprecated and when it will be removed. Recommend alternative if available]. ([TICKET-ID])

---

**Full changelog:** [link]
**Questions?** [support link or contact]

Python Tool

Use

scripts/release_notes_generator.py

# Generate from JSON input
python scripts/release_notes_generator.py --input changes.json --product-name "Acme App" --version "2.5.0"

# Run with demo data
python scripts/release_notes_generator.py --demo --product-name "Acme App" --version "1.0.0"

# Output as JSON instead of markdown
python scripts/release_notes_generator.py --input changes.json --format json --product-name "Acme App" --version "2.5.0"

See

scripts/release_notes_generator.py --help

Integration with Other Skills

• Use

  summarize-meeting/

  to capture release planning discussions.
• Use

  job-stories/

  or

  wwas/

  to trace features back to their original motivation.
• Pair with

  ../senior-pm/

  for stakeholder communication planning around major releases.

Troubleshooting

feature

improvement

bugfix

breaking

deprecation

improvement

breaking

breaking

improvement

--demo

--product-name

--version

--demo --product-name "App" --version "1.0.0"

Success Criteria

• Every release has structured notes published within 24 hours of deployment
• All entries lead with user benefit, not technical implementation details
• Breaking changes include explicit migration instructions with deadlines
• Deprecations include removal timeline and recommended alternatives
• Technical language flags reviewed and addressed before publication
• Release notes tone matches the target audience (B2B/consumer/developer/internal)
• Entries traceable to tickets via ticket_id for audit and context

Scope & Limitations

In Scope:

• Structured release note generation from JSON input with 5 entry categories
• Automatic technical language detection with rewriting suggestions
• Markdown and JSON output formatting with category grouping
• Audience tone guidance (B2B, consumer, developer, internal)
• Classification rules for New Features, Improvements, Bug Fixes, Breaking Changes, and Deprecations

Out of Scope:

• Automatic extraction of changes from git history (see

  sprint-retrospective/

  for git analysis)
• Jira/Linear ticket integration for pulling completed stories (manual JSON input required)
• Changelog maintenance across multiple releases (this tool generates per-release notes)
• Distribution to email, in-app, or documentation channels (output is markdown/JSON for further processing)

Important Caveats:

• The rewriting suggestions are pattern-based heuristics. They catch common technical language but cannot assess whether a description truly communicates user benefit.
• Semantic versioning alignment is the user's responsibility. The tool does not validate that version numbers follow semver conventions relative to the change types present.
• Breaking changes require special care. Always include: what changed, what the user must do, and by when. Vague breaking change notes erode user trust.

Integration Points

sprint-retrospective/

senior-pm/

execution/create-prd/

scrum-master/

summarize-meeting/

job-stories/

wwas/

Tool Reference

release_notes_generator.py

Generates formatted release notes from structured JSON input. Groups entries by category, formats into markdown or JSON, and flags entries that may need user-benefit rewriting.

--input

--demo

--product-name

--version

2.5.0

--format

text

text

json

--date

Input JSON schema:

{
  "entries": [
    {
      "title": "Feature Name",
      "description": "User-benefit description (1-3 sentences)",
      "type": "feature|improvement|bugfix|breaking|deprecation",
      "ticket_id": "PROJ-123 (optional)"
    }
  ]
}

References

• See

  references/release-notes-guide.md

  for best practices, audience guidance, and examples.
• See

  assets/release_notes_template.md

  for a ready-to-use document template.