Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for technical writers

Release Notes Assembly Agent

Complete, readable release notes ready on release day

CreatingWritingIT and developmentWriters
See how it worksGet access
Release Notes Assembly Agent: what goes in, what the agent does and what you get

What it does

Each release contains dozens of tickets, but users need short, clear notes about what changed for them, not a list of ticket titles. When a release is tagged, this agent pulls the merged tickets and the feature flag status. It filters out internal work and features still behind a flag, groups the rest into breaking changes, new features, improvements and fixes, and drafts plain-language notes following the style guide. Breaking changes go first, and fixes describe the symptom users saw. It then compares the changed components with the draft to confirm every user-visible change is covered and nothing flagged is mentioned. If something is missing, it finds the tickets and adds them. A second check confirms wording follows the style guide. The writer edits and approves before publishing. Edge case: a flagged feature is held back until the flag is on for customers.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueYes, continueApprovedNoNo 1 STARTS WHEN Release tagged 2 USES A TOOL Pull merged tickets and feature flag status 3 DOES Filter internal work and flagged features and groupchanges 4 DOES Draft plain-language notes with breaking changesfirst 5 USES A TOOL Compare changed components with the draft 6 CHECKS THE RESULT Is every user-visible change covered and nothingflagged mentioned? If not: find missing tickets by component and add them,remove flagged items. Back to step 3. 7 CHECKS THE RESULT Does the wording follow the style guide? If not: rewrite the lines that break the guide. Back tostep 4. 8 YOU APPROVE Writer edits and approves notes 9 RESULT Release notes ready to publish
Read the steps as a list
  1. Release tagged
  2. Pull merged tickets and feature flag status
  3. Filter internal work and flagged features and group changes
  4. Draft plain-language notes with breaking changes first
  5. Compare changed components with the draft
  6. Is every user-visible change covered and nothing flagged mentioned?If not: find missing tickets by component and add them, remove flagged items. Back to step 3.
  7. Does the wording follow the style guide?If not: rewrite the lines that break the guide. Back to step 4.
  8. Writer edits and approves notesThe agent waits here for your OK.
  9. Release notes ready to publish

How it decides

It includes tickets that change what users see or do, excludes internal work and features still behind a flag.

  • Flagged features are held back
  • Fixes describe the symptom users saw
  • Breaking changes go first

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Labels that mark user-visible work
  • Style guide
  • Sections and order
  • Publish target

What keeps you in control

It always asks you first

  • Publishing the notes

Hard limits

  • Never publishes
  • Never names customers who reported bugs

It stops when

  • Done: approved notes
  • Stop: release is rolled back

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensRelease 5.8 had 64 tickets. The first draft missed three user-facing fixes that had no label, and it mentioned a scheduling feature still behind a flag. The coverage check failed. The agent compared changed components, found the three fixes and added them, and removed the scheduling item. The recheck passed. The writer tightened two lines and approved the notes on November 12.

More agents for technical writers

Compliance · Quality control

Editorial Revision Compliance Agent

A revision compliance map and response for the editor.

7 steps1 check7 jobs
Quality control · Writers

Article Structure Revision Agent

A tracked structural revision that keeps the argument fully supported.

7 steps1 check6 jobs
Compliance · Creatives

Copy Approval Chain Tracker Agent

One locked copy version with a complete record of who approved it

9 steps2 checks7 jobs
Quality control · Automation

Web Content Translation Sync Agent

Keep every translated page in sync with its source, with verified text and rendering.

10 steps2 checks7 jobs