Release Notes Writer
On each release, a writer agent pulls the merged work since the last release, drafts a user-facing changelog grouped into New, Improved, and Fixed in your house voice, self-edits against a quality bar, and lands one approval before you publish.
Saves you ~2.5 h / run
How it works
- Trigger
- When you start the “Draft release notes” workflow.
- Job
- Gather merged work, categorize, draft the changelog, and approve.
- Outcome
- A verified release-note and changelog draft grounded in shipped work.
What it installs
Agents 2
-
Release Notes Writer
Turns merged PRs and issues into a user-facing changelog in your house voice.
-
Release Notes Writer Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Release Notes Writer quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Draft release notes
Gather merged work, categorize, draft the changelog, self-edit against the quality bar, and approve.
Documents 1
-
Product-writing voice guide
Your house voice for release notes — fill in the tone, banned words, and example phrasings the writer should follow.
Goals 1
-
Every release ships with clear, user-facing notes
Release notes exist so users always know what changed and why it matters — no release should ship silently or with committer-speak nobody outside the team can read. Success looks like: Every release produces an approved changelog before publication, where each entry leads with a user benefit, internal chores are excluded, breaking changes carry their required action, the highlights are obvious, and the voice is plain and free of fluff and AI tells.
Skills 2
-
release-notes
Turn merged tickets, PRs, and changelogs into user-facing release notes: extract what changed / who it affects / why it matters, categorize into features, improvements, fixes, breaking changes, and deprecations, and lead every entry with the user benefit. Adapted from phuryn/pm-skills/release-notes.
-
product-writing-voice
Apply a plain, direct, honest product-writing voice: ban corporate fluff ('excited to announce', 'seamless', 'leverage'), lead with the problem or result, use numbers over adjectives, and strip AI tells (staccato fragments, three-beat reveals, parallel ad-copy). Adapted from getsentry/skills/blog-writing-guide.
Folders 1
-
Release Notes
Requirements
- Connected repository — The agent reads merged pull requests, commits, and closed issues from your connected repository to gather what shipped since the last release. It only reads and drafts — it never publishes — and pauses for your approval before anything goes out. Until you connect it, it works from the release exports you attach.
Setup guide
How to Write Release Notes With an Agent
A practical guide to turning merged work into clear release notes with repository context, house voice, and approval.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.