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

Design Document Change Sync Agent

Design docs, tickets and config that agree

Design Document Change Sync Agent: what goes in, what the agent does and what you get

What it does

Game design docs change daily, and docs, balance sheets and tickets drift apart unnoticed. When a design doc is edited, this agent finds exactly what changed and which other docs, tickets and config values depend on it. It compares them and lists conflicts, such as a weapon's damage in the combat doc not matching the balance sheet, or a feature described in a doc but cut in tickets. It drafts updates for linked docs and comments for tickets. After the designer applies changes, it rechecks every linked item and lists anything that still disagrees. It also checks whether the change touches work already in production. Once everything agrees, it drafts a change note for art and code leads. The designer approves the note before it is posted. Edge case: a change to a feature already in production is flagged as needing a formal change request.

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 Design doc edited 2 USES A TOOL Find the change and dependent items 3 DOES Compare with linked docs, tickets and config 4 USES A TOOL Draft updates and ticket comments for conflicts 5 CHECKS THE RESULT Do all linked items agree after updates? If not: list remaining conflicts for the designer. Backto step 3. 6 CHECKS THE RESULT Does the change touch work already in production? If not: flag it as needing a change request. Back tostep 4. 7 USES A TOOL Draft the change note for art and code leads 8 YOU APPROVE Designer approves the change note 9 RESULT Change note posted
Read the steps as a list
  1. Design doc edited
  2. Find the change and dependent items
  3. Compare with linked docs, tickets and config
  4. Draft updates and ticket comments for conflicts
  5. Do all linked items agree after updates?If not: list remaining conflicts for the designer. Back to step 3.
  6. Does the change touch work already in production?If not: flag it as needing a change request. Back to step 4.
  7. Draft the change note for art and code leads
  8. Designer approves the change noteThe agent waits here for your OK.
  9. Change note posted

How it decides

It traces dependencies and flags any linked item that no longer matches the change.

  • Items in production need a change request
  • Config is the source of truth for numbers unless the designer says otherwise
  • Cut features are marked in docs

Make it yours

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

  • Linked sources
  • Who gets change notes
  • Conflict rules
  • Doc tool

What keeps you in control

It always asks you first

  • Change notes
  • Ticket updates

Hard limits

  • Never edits config
  • Never closes tickets

It stops when

  • Done: all items agree
  • Stop: doc locked for milestone review

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 happensOn September 2 the designer cut the grappling hook from the movement doc. The agent found 3 level docs using it, 2 open art tickets and a config flag. It drafted updates and ticket comments. On recheck, one level doc still mentioned the hook, so it listed it; the designer fixed it. The production check showed one art ticket was already in progress, so it was flagged. The designer approved the change note.

More agents for game designers