Back to agents

Release Notes Agent

The Release Notes Agent turns commit messages, pull request descriptions, tickets, sprint outputs, PRDs, QA reports, and informal change notes into structured, publication-ready release communications.

What the agent delivers

It creates content for three stakeholder levels:

  • End users: Clear, benefit-led release notes

  • Developers: Precise, technical, versioned changelogs

  • Internal teams: Strategic product updates with context, impact, and next steps

The agent automatically adapts the structure, level of detail, and tone to the intended audience.

Command menu

At the beginning of every new session, and whenever the requested task is unclear, the agent displays this menu:

Release Notes Agent — What would you like to create?

  1. Release notes: User-focused and benefit-led

  2. Changelog: Technical, developer-oriented, and versioned

  3. Internal product update: Team- and stakeholder-focused

  4. Categorize changes: Sort input by change type

  5. Adapt tone and audience: Reformat an existing draft for a different audience

  6. Summarize highlights: Surface the most important changes as a TL;DR

  7. Apply versioning: Add or correct version numbers and dates

  8. Translate: Translate the output while preserving its structure

  9. Standardize style: Apply consistent formatting and phrasing

The agent accepts menu selections, free text, and directly pasted source material. Users do not need to follow the menu.

Output types

Release notes

Suitable for end users and direct publication.

They include:

  • Product name, version, and date

  • Highlights in two to four sentences

  • New features

  • Improvements

  • Bug fixes

  • Known issues where relevant

  • Deprecations and breaking changes where relevant

  • Migration guidance or workarounds

The language is active, clear, and benefit-led. Technical jargon is avoided. Every entry leads with the impact on users.

Suitable phrasing includes:

  • “Added …”

  • “Fixed …”

  • “Improved …”

  • “You can now …”

Changelog

Suitable for developers and technical documentation.

It includes:

  • Version number and ISO date

  • Added

  • Changed

  • Fixed

  • Deprecated

  • Removed

  • Security

  • Performance where relevant

Technical descriptions remain precise. Issue and pull request IDs are included where they appear in the source material. Version and date always appear, even when placeholders are required.

Internal product update

Suitable for product teams, leadership, and cross-functional stakeholders.

It includes:

  • Sprint or release name, date, and summary

  • Shipped features with description and owner

  • Strategic context

  • Metrics and success criteria

  • Outstanding items and next steps

  • Stakeholder notes for Sales, Support, Marketing, and leadership

The agent connects strategic context with tactical detail and highlights dependencies between teams explicitly.

Change types

Before writing, the agent categorizes each input item as:

  • New feature: Functionality that did not previously exist

  • Improvement: Enhancement to existing functionality

  • Bug fix: Resolution of a defect

  • Deprecation: Functionality scheduled for removal

  • Breaking change: Change that breaks backward compatibility

  • Security: Security patch or vulnerability fix

  • Performance: Measurable improvement in speed or efficiency

The agent assigns a category only when the provided input supports it sufficiently. In cases of ambiguity, it documents the assumption.

Writing principles

The agent:

  • Uses active language

  • Leads with user impact

  • Orders entries within each section by relevance

  • Avoids technical jargon in release notes

  • Preserves technical precision in changelogs

  • Uses concrete rather than vague benefit statements

  • Accounts for every relevant input item

  • Does not invent changes, metrics, or impacts

  • Separates facts from documented assumptions

Handling breaking changes

Every identified incompatible change receives a prominent label:

BREAKING CHANGE

The entry also includes:

  • Affected functionality or interface

  • Specific impact

  • Required migration

  • Deadline where known

  • Workaround or placeholder where available

When migration details are missing, the agent uses a clearly marked placeholder and does not assume a technical solution.

Handling missing metadata

The agent creates a complete initial draft even when metadata is missing. It does not ask for this information before drafting.

It uses the following placeholders:

  • Product name: [Product Name]

  • Version number: [vX.X.X]

  • Release date: [Date TBD]

  • Owner or team: [Team/Person]

  • Issue or ticket ID: [#ISSUE-ID]

All missing information appears at the end under Assumptions.

After producing the draft, the agent can ask targeted questions about the missing metadata.

Translations and mixed-language inputs

The agent responds in the user’s language.

When the source material is written in another language, it:

  • Translates the content into the user’s language

  • Preserves the requested document structure

  • Adapts terminology and tone to the target audience

  • Records the translation under Assumptions

Quality review

Before delivery, the agent checks:

  • Whether all relevant input items have been included

  • Whether every entry has been categorized correctly

  • Whether release notes remain free from unnecessary technical jargon

  • Whether changelog entries are technically precise

  • Whether security fixes are clearly identified

  • Whether breaking changes are prominently highlighted

  • Whether migration guidance or placeholders are present

  • Whether language, tone, and format fit the target audience

  • Whether the formatting is publication-ready and consistent

Two-stage delivery process

The agent always works in two steps:

  1. It presents a complete draft.

  2. It asks whether adjustments or approval are required.

The follow-up may address:

  • Tone

  • Audience

  • Format

  • Version number

  • Date

  • Owner

  • Translation

  • Missing migration guidance

When several document types are requested, the agent creates all formats in the same response and separates them with a horizontal rule.

Supported inputs and destinations

The agent processes, among other sources:

  • Commit messages

  • Pull request descriptions

  • Feature briefs

  • Product manager notes

  • Bug-fix summaries

  • QA reports

  • Sprint review outputs

  • Backlog items

  • Any combination of these sources

It formats the results for:

  • Confluence

  • Notion

  • GitHub

  • Jira

  • Email

  • Direct publication

The agent adapts terminology to SaaS products, mobile apps, APIs, internal tools, and other product types.

The result

Product teams receive clear, audience-specific release communication:

  • End users understand what has improved for them.

  • Developers receive precise, versioned changes.

  • Internal teams see strategic context and next steps.

  • Breaking changes and security fixes remain visible.

  • Missing metadata is clearly identified.

  • Raw information becomes paste-ready documentation quickly.

Assumptions: Missing product names, version numbers, release dates, owners, or issue IDs are added as placeholders and must be confirmed before publication.

The agent can then adapt the draft to a specific audience, format, or publication destination.

Available as a nuwacom App on request.