propagate-design-change

Compare revised GDDs against previous git versions to classify impacted ADRs.

1|Updated May 3, 2026

Search Tags:#developer workflow #adr #impact analysis #traceability #gdd #architecture governance #version diff

Ready to run

npx skills add https://github.com/imclab/xrA1-swarm --skill propagate-design-change-imclab

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

Prevents architectural drift by identifying which ADRs may no longer match your updated GDD and guiding you through safe resolution.

Core Features & Use Cases

Change impact analysis: Compares the revised GDD against its previous git version to detect changed sections that could invalidate architectural assumptions.
ADR traceability scanning: Loads ADRs and the architecture traceability index to find every ADR referencing the changed GDD requirements.
Decision classification & resolution guidance: Classifies each impacted ADR as Still Valid, Needs Review, or Likely Superseded, then orchestrates per-ADR user decisions and (optionally) traceability index updates.

Quick Start

Use /propagate-design-change design/gdd/combat-system.md to generate a design change impact report for the revised combat system GDD.

Frequently Asked Questions about propagate-design-change

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

FAQPage Schema

How do I update ADRs when my GDD changes?▼

To update ADRs when your GDD changes, compare the revised GDD against its previous git version to detect altered sections, scan the traceability index for impacted ADRs, and classify each as Still Valid, Needs Review, or Likely Superseded.

What is design change impact analysis for architecture governance?▼

Design change impact analysis for architecture governance identifies which Architectural Decision Records no longer match an updated Game Design Document, preventing architectural drift by evaluating stale requirement assumptions and guiding safe resolution.

How do I trace GDD requirement changes to specific ADRs?▼

Trace GDD requirement changes to specific ADRs by loading the architecture traceability index and retrieving related ADRs, which maps the revised design document sections to the architectural decisions that reference them.

Does ADR impact classification require a git repository?▼

ADR impact classification requires a git repository to retrieve the previous version of the revised GDD, performing a version diff to detect changed sections that could invalidate architectural assumptions before classifying impact status.

What's the best way to prevent architectural drift in spec-driven development?▼

Preventing architectural drift in spec-driven development is best achieved by propagating revised design documents into architecture records, classifying impacted decisions, and orchestrating a guided resolution workflow with traceability index updates.

Can I automatically generate a change-impact document for stale ADRs?▼

You can generate a change-impact document for stale ADRs by running the propagation workflow, which produces guided resolution steps and optionally writes traceability index and change-impact documents after classifying each impacted decision.