propagate-design-change

Name: propagate-design-change
Availability: InStock
Author: easonlao

Detect stale ADRs after GDD revisions and categorize validity.

Updated Apr 25, 2026

Search Tags:#git #adr #impact analysis #traceability #decision records #gdd #architecture maintenance

Ready to run

npx skills add https://github.com/easonlao/jiazi-game --skill propagate-design-change-easonlao

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes references (resource) components.

What problem does it solve?

It prevents architectural drift by identifying which ADRs become stale after a GDD revision, then helps you reconcile the mismatches.

Core Features & Use Cases

Impact detection across architecture: Scans all ADRs and the architecture traceability index to find decisions tied to the changed GDD.
Validity classification: Compares what each ADR assumed versus what the current GDD now states, categorizing outcomes as Still Valid, Needs Review, or Likely Superseded.
Resolution guidance with traceability updates: Supports per-ADR resolution (keep, review/update, or supersede) and can update the traceability index and write a change impact report.

Quick Start

Run the command /propagate-design-change with the path to the revised GDD, and review the generated impact report before choosing how to update each affected ADR.

Frequently Asked Questions about propagate-design-change

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

FAQPage Schema

How do I check which ADRs are affected by a GDD revision?▼

To check which ADRs are affected by a GDD revision, scan your architecture traceability index to detect decisions referencing the changed GDD. The tool categorizes each ADR as Still Valid, Needs Review, or Likely Superseded by comparing assumed requirements against current GDD sections.

What is architectural drift and how do I prevent it when updating design documents?▼

Architectural drift occurs when existing ADRs become stale after GDD revisions. Prevent drift by propagating design changes to identify mismatched ADRs, classify their validity, and reconcile them through per-ADR resolution while updating the traceability index.

How to propagate design changes and update stale architectural decision records?▼

Propagate design changes by running the propagation command with your revised GDD path. It compares each referenced ADR against current GDD sections, generates a categorized change impact report, and supports per-ADR resolution to keep, update, or supersede decisions.

Can I validate ADR impact analysis results before finalizing architectural changes?▼

You can validate ADR impact analysis results by running an optional technical director gate for validation. This gate checks the categorized impact report before you choose how to resolve each affected ADR and commit traceability updates.

Does this architecture maintenance workflow require a git repository?▼

Yes, this architecture maintenance workflow requires git as a dependency to manage GDD revisions and ADR updates. It operates within your existing git-tracked repository to detect changes and maintain traceability across architectural documents.

When should I supersede an ADR instead of marking it for review after a GDD update?▼

Supersede an ADR when the current GDD sections directly contradict the assumed requirements of the decision. The propagation tool classifies this as Likely Superseded, whereas partial mismatches are categorized as Needs Review for targeted updates.