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 game designers

Patch Notes Assembly Agent

Accurate, complete patch notes with no leaks

Patch Notes Assembly Agent: what goes in, what the agent does and what you get

What it does

Patch notes are often written in a rush on release day, and players spot every wrong number. Before each update, this agent collects the merged changes, closed tickets and balance config changes for the release candidate. It groups them into features, balance changes, fixes and known issues, and drafts player-facing notes in plain language with exact numbers for every balance change. It then checks every line against the final build and config, and confirms that nothing marked confidential is mentioned. Any mismatch is corrected or removed, and the notes are rechecked. Once clean, it drafts versions in each platform's format, then checks that the platform versions still say the same thing. The designer and community lead approve before anything is published. Edge case: a fix reverted at the last minute is removed from the notes even though its ticket says closed.

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 candidate chosen 2 USES A TOOL Collect changes, tickets and config diffs 3 DOES Group and draft player-facing notes 4 USES A TOOL Check notes against the final build and config 5 CHECKS THE RESULT Do all notes match the build and avoid confidentialitems? If not: correct or remove items and recheck. Back tostep 3. 6 USES A TOOL Draft versions for each platform format 7 CHECKS THE RESULT Do platform versions match the master notes? If not: fix the differing version. Back to step 6. 8 YOU APPROVE Designer and community lead approve 9 RESULT Notes ready to publish
Read the steps as a list
  1. Release candidate chosen
  2. Collect changes, tickets and config diffs
  3. Group and draft player-facing notes
  4. Check notes against the final build and config
  5. Do all notes match the build and avoid confidential items?If not: correct or remove items and recheck. Back to step 3.
  6. Draft versions for each platform format
  7. Do platform versions match the master notes?If not: fix the differing version. Back to step 6.
  8. Designer and community lead approveThe agent waits here for your OK.
  9. Notes ready to publish

How it decides

Each note must match the final build and config; confidential items are removed.

  • Reverted changes are removed
  • Balance notes use exact numbers
  • Confidential items never appear

Make it yours

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

  • Note categories
  • Tone
  • Platform formats
  • Confidential list

What keeps you in control

It always asks you first

  • Publishing notes

Hard limits

  • Never publishes notes
  • Never mentions confidential content

It stops when

  • Done: notes approved
  • Stop: release candidate rejected

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 happensFor update 1.8 on February 18, the draft listed sword damage going from 40 to 45. The build check failed: the config showed 44. A lighting fix had also been reverted, and one note named an unannounced map. The agent corrected the number, removed both items and rechecked. It then drafted Steam and console versions. The designer and community lead approved them that afternoon.

More agents for game designers