propagate-design-change
When a game design document is revised, architectural decisions built on it may become stale. This skill reads the changed GDD, compares it against all architecture decision records, and produces a detailed impact report classifying each ADR as still valid, needing review, or likely superseded. It then guides you through resolution decisions and updates your traceability index.
Propagate Design Change identifies which architectural decisions are affected when a game design document is revised.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-21
Propagate Design Change identifies which architectural decisions are affected when a game design document is revised. When a game design document is revised, architectural decisions built on it may become stale. This skill reads the changed GDD, compares it against all architecture decision records, and produces a detailed impact report classifying each ADR as still valid, needing review, or likely superseded. It then guides you through resolution decisions and updates your traceability index.
Use it when
- propagate-design-change identifies stale ADRs by comparing your updated GDD against all recorded architectural decisions.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
Donchitos/Claude-Code-Game-Studios/propagate-design-change · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to update ADRs when GDD changes?
propagate-design-change reads your revised game design document, cross-references every architecture decision record against the changes, and generates a detailed impact report. The skill classifies each ADR as valid, needing review, or likely superseded based on how the GDD revision affects its underlying assumptions. You then work through the guided resolution workflow to update your traceability index.
Which ADRs are stale after updating design document?
propagate-design-change identifies stale ADRs by comparing your updated GDD against all recorded architectural decisions. It flags ADRs whose assumptions no longer hold, whose context has shifted, or whose rationale conflicts with new design requirements. The skill presents these findings in a structured impact report so you can prioritize which decisions need immediate review or replacement.
Can propagate-design-change detect broken ADR assumptions?
Yes. propagate-design-change traces design changes through your architecture by analyzing how GDD revisions affect the premises each ADR was built on. It detects when assumptions are violated, when new constraints emerge, or when previously acceptable trade-offs become untenable. The skill flags these broken assumptions so you can decide whether to update, replace, or retire each affected decision.
What does the ADR impact report include?
propagate-design-change's impact report links each GDD update to the ADRs it affects, showing which decisions remain valid, which need review, and which are likely superseded. The report traces design changes through your architecture, explains why each ADR's status changed, and guides you through marking decisions as superseded and making replacement choices. It also updates your architecture traceability index.
How does propagate-design-change guide ADR supersession?
propagate-design-change marks ADRs as superseded when GDD changes invalidate their rationale, then walks you through replacement decision-making. The skill helps you understand what new architectural choice should replace the old one, ensures the new decision addresses the updated design context, and maintains continuity in your decision history so future changes can trace their lineage.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Propagate Design Change
When a GDD changes, architectural decisions written against it may no longer be valid. This skill finds every affected ADR, compares what the ADR assumed against what the GDD now says, and guides the user through resolution.
Usage: /propagate-design-change design/gdd/combat-system.md
1. Validate Argument
A GDD path argument is required. If missing, fail with:
> "Usage: /propagate-design-change design/gdd/[system].md
> Provide the path to the GDD that was changed."
Verify the file exists. If not, fail with: > "[path] not found. Check the path and try again."
2. Read the Changed GDD
Read the current GDD in full.
3. Read the Previous Version
Run git to get the previous committed version:
```bash git show
(truncated - see the full file via the links below)
File tree — 1 file
.claude/skills/propagate-design-change/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Find which architectural decisions are affected by a GDD revision”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Create Epics transforms approved design documents and architecture into named, bounded epics—one per architectural module. Each epic defines scope, identifies governing architecture decisions, flags engine risk, and traces requirements to decision coverage. Run this skill once per development layer after control manifest and architecture review pass; follow each epic with /create-stories to decompose into implementable work.
This skill guides you through authoring Architecture Decision Records (ADRs) that capture major technical choices with full context. It validates decisions against existing architectural stances, engine compatibility, and GDD requirements, then generates a structured record with status, dependencies, and consequences tracked. Use it to retrofit missing sections into existing ADRs or create new ones from scratch.
This skill transforms accepted architecture decision records into a single, layer-organized reference guide that tells programmers exactly what to do and what to avoid. It pulls rules from ADRs, technical preferences, and engine docs, then surfaces them by Foundation, Core, Feature, and Presentation layers—answering "what do I do?" faster than reading the reasoning behind each decision.
This skill captures architectural decisions made during coding sessions as structured ADR documents that live alongside your codebase. It detects decision moments, gathers context and alternatives, and maintains a searchable log so future developers understand the reasoning behind your architecture.
ADR Skill helps teams document architecture decisions as executable specifications for coding agents. It guides you through a four-phase workflow—scanning existing decisions, capturing intent through structured questions, drafting the record with implementation details, and validating against an agent-readiness checklist. Built for codebases where decisions must be explicit, measurable, and actionable.
Adr helps you systematically capture architecture decisions with context, options, and consequences. Create numbered decision records, browse your decision history, and search past choices to avoid redundant deliberation.