propagate-design-change

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.

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.

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.

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.

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.

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.