propagate-design-change

Compare ADR assumptions against revised GDD text and classify impacts.

Updated Apr 4, 2026

Search Tags:#adr #impact analysis #git diff #gdd #architecture governance #decision review #traceability index

Ready to run

npx skills add https://github.com/WindXRan/y3td --skill propagate-design-change-windxran

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/propagate-design-change
Command: npx skills add https://github.com/WindXRan/y3td --skill propagate-design-change-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a GDD changes, architectural decisions captured in ADRs can become outdated or contradictory, causing teams to implement based on assumptions that are no longer true.

Core Features & Use Cases

Impact analysis across ADRs: Scans all ADRs and the traceability index to find which decisions reference the changed GDD.
Assumption vs. current-spec comparison: Compares what the ADR’s “GDD Requirements Addressed” section assumed against the GDD’s current content and classifies the impact as still valid, needs review, or likely superseded.
Resolution workflow with guardrails: Produces a change impact report, runs a technical-director gate for classification review, and then guides per-ADR resolution actions without destructive edits.

Quick Start

Use the propagate-design-change skill to analyze an updated combat-system GDD by running: /propagate-design-change design/gdd/combat-system.md

Frequently Asked Questions about propagate-design-change

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

FAQPage Schema

How do I detect stale ADRs after updating a game design document?▼

To detect stale ADRs after a GDD update, scan all ADRs and the traceability index to locate references to the changed design document and classify assumption impacts. This process compares prior assumptions against current GDD text to identify outdated architectural decisions.

What is the best way to perform impact analysis on architecture decisions when requirements change?▼

The best way to perform impact analysis on architecture decisions is to extract ADR traceability and compare assumptions against revised requirement specifications. This generates a classified impact report categorizing decisions as still valid, needing review, or likely superseded.

How do I compare previous GDD versions to current assumptions during architecture governance?▼

You compare previous GDD versions to current assumptions by retrieving the prior git-based version of the design document and matching it against ADR traceability. This comparison highlights conflicting assumptions caused by renamed requirements or adjusted tuning knobs.

Can I automatically update architectural decision records when formulas or acceptance criteria change?▼

You cannot automatically update architectural decision records, as the workflow uses a technical-director approval gate before writing any outputs. It guides per-ADR resolution actions and produces an impact report without making destructive edits to ensure safe governance.

Does the ADR impact analysis workflow support retrieving previous versions via git diff?▼

Yes, the ADR impact analysis workflow supports retrieving previous document versions via git diff to establish a baseline for comparison. This allows you to accurately identify which architectural decisions are affected by the latest design document edits.

When should I run an ADR traceability extraction for design document changes?▼

You should run ADR traceability extraction during architecture governance workflows whenever a GDD is edited, requirements are renamed or removed, formulas and acceptance criteria change, or tuning knobs are adjusted to ensure implementation consistency.