propagate-design-change

Identifies stale architecture decision records after a game design document revision.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill propagate-design-change-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/propagate-design-change
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill propagate-design-change-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a game design document (GDD) is revised, architecture decision records (ADRs) written against the old version can silently become outdated. This Skill detects which ADRs are affected by a GDD change and guides you through resolving each one. ## Core Features & Use Cases - Change Detection: Diffs the current GDD against its previous git version and summarizes which sections, rules, and formulas changed. - Impact Analysis: Scans all ADRs in docs/architecture and the traceability index, classifying each affected ADR as Still Valid, Needs Review, or Likely Superseded. - Guided Resolution: Walks you through per-ADR decisions, updates superseded statuses, refreshes the traceability index, and writes a dated change impact report. - Use Case: After revising your combat-system GDD, run this Skill to find every ADR that assumed the old damage formula, review each one, and record the resolution in docs/architecture. ## Quick Start Run the propagate-design-change skill on design/gdd/combat-system.md to find which architecture decisions are affected by my latest design revision.

Frequently Asked Questions about propagate-design-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which ADRs are affected by a GDD change?

Run the skill with the path to the revised GDD, for example design/gdd/combat-system.md. It diffs the file against its previous git version, scans all ADRs in docs/architecture, and reports which ones reference the changed requirements.

How does design change impact analysis work with git history?

The skill runs git show HEAD on the GDD path to retrieve the previous committed version, then performs a conceptual diff of changed sections, rules, and formulas. If the file has no git history, it reports the GDD as new and stops.

What happens to ADRs that contradict a revised GDD?

Each affected ADR is classified as Still Valid, Needs Review, or Likely Superseded. For superseded ADRs, the skill updates the status line to note the pending replacement and suggests writing a new ADR, never deleting existing content.

Does this skill modify files without confirmation?

No. The skill presents the full impact report first and asks before every write, including ADR status updates, traceability index changes, and saving the change impact document. Declining a write results in a blocked verdict.

What are the limitations of GDD-to-ADR traceability checks?

The analysis only covers ADRs that explicitly reference the changed GDD in their requirements table, so undocumented assumptions may be missed. Classification of borderline cases still requires human judgment during the review workflow.