Skip to content
Get packs

Propagate Design Change

Finds architecture decisions made stale by an edited game design doc and walks through fixes

Source Download skill
Repository
Donchitos/Claude-Code-Game-Studios
Stars
32,965
Licence
MIT
Files
1 file

What it does

When a game design document (GDD) changes, this skill makes the agent check which architecture decision records (ADRs) written against it may now be out of date. It reads the changed sections from git history, lists the affected decisions, compares what each assumed with what the design now says, and asks the user how to resolve each one. Outside the skill's own scripts, the agent only reads and edits project files and runs a few git and helper commands.

Great for

  • Solo or small teams running a Claude Code game-studio project with written GDDs and ADRs
  • Producers or leads who tweak a combat number or rule and need to know which architecture choices it affects
  • Teams that keep design and architecture docs in git and want a checklist before a production gate

Skip it if

  • Projects without GDD or ADR files: the skill stops immediately and has nothing to check
  • Users who want an automatic rewrite of decisions: each ADR is classified and then discussed with a human, and edits are made only with their input, but automation modes can log and continue on some choices, so review the log
  • Non-git projects: the skill relies on git diff and git log to see what changed

Try asking

  • “I changed the jump height in design/gdd/movement-system.md, which architecture decisions are now out of date?”
  • “Propagate the design change in design/gdd/combat-system.md to my ADRs”
  • “Check whether my ADRs still match the updated inventory GDD after the weight limit change”
Step-by-step guide: how to use Propagate Design ChangeInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    propagate-design-change.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip propagate-design-change.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip propagate-design-change.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Commit or stage your GDD edit first so git diff shows exactly what changed; otherwise the skill falls back to the last commit.
  • Pass --review lean or --review solo to change how many ADRs are checked and how many questions you are asked.
  • Read each ADR classification before accepting it; Needs Review means a human judgement is still required.

What's inside

  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.