Propagate Design Change

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Propagate Design Change" for me. When a Game Design Document changes, it finds the architecture decisions (ADRs) the change makes stale and walks you through resolving each one. You give it the changed GDD's path (required). It reads what changed from git — git diff and git log on that file, never a by-eye comparison of whole documents — optionally checks design/registry/entities.yaml for other GDDs that use the changed facts, lists the in-scope ADRs with the template script .claude/scripts/adr-status.sh (scope depends on the workflow tier: every ADR at full, the critical ones at standard, none at minimal), and classifies each affected ADR Still Valid, Needs Review or Likely Superseded using .claude/scripts/md-section.sh. With skill-gates running, the template's technical-director agent reviews the impact report (gate TD-CHANGE-IMPACT). Resolution is per ADR and asked each time: the one direct write it makes is setting an ADR's Status section to Superseded via md-section.sh, after asking "May I set the Status of [ADR file] to Superseded?"; it also asks before adding rows to docs/architecture/requirements-traceability.md and before writing the impact report to docs/architecture/change-impact-[date]-[system-slug].md. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/propagate-design-change/ folder at the pinned commit: 1 file in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/propagate-design-change/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 bf110550ddd1ca9c8bbd266cda2808b40aec02646b6ff9886d850ab9f1f1d7c9 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time — the scripts it drives (adr-status.sh, md-section.sh) belong to the template, outside this folder. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no GDD or ADR of mine is read, no git command is run and nothing is modified. - Integrated-system reality, from the file: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys review_mode, review_gate, automation, automation_always_ask, workflow, system_overrides), is explicitly allowed git diff and git log in my project, drives the template scripts .claude/scripts/adr-status.sh and .claude/scripts/md-section.sh, reads docs/architecture/ and optionally design/registry/entities.yaml, and with skill-gates running hands its impact report to the template's technical-director agent — files, scripts and an agent that live outside this skill's folder and are absent in a standalone install, so it cannot run outside the full template. - At use time every write is asked first, one ADR at a time: replacing an ADR's Status section body with Superseded (via md-section.sh replace — the one write form the file names), adding rows to the traceability index when it exists, and writing the change-impact document under docs/architecture/. No third-party service, account or credential is named in the file. - Do not propagate any change, do not run git, any template script or agent, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole propagate-design-change folder into the agent's skills directory, in a folder named exactly "propagate-design-change", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: propagate-design-change), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it drives the template's adr-status.sh and md-section.sh scripts and yaml-helper hook and uses git in my project), and that every write — an ADR marked Superseded, traceability rows, the impact document — is asked first, one ADR at a time). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.