propagate-design-change

To check which ADRs are affected by GDD changes, compare the revised GDD against its previous git version, load your ADRs and traceability index, then generate an impact report classifying each decision as Still Valid, Needs Review, or Likely Superseded.

Architectural traceability links design decisions to game design requirements, ensuring internal consistency. You need traceability when a GDD evolves, so you can detect which existing ADR assumptions have become stale and resolve the fallout systematically.

To keep ADRs aligned with an updated GDD, use git diff to identify revised requirements, load the architecture traceability index to find referenced ADRs, and walk through a human-in-the-loop workflow to update or supersede affected decisions.

Yes, this impact analysis workflow requires a git repository to access the previous committed version of the GDD, enabling an accurate revision diff to identify exactly what design changes occurred.

You can automate ADR validation after git diff detects GDD changes by loading the traceability index to classify affected ADRs, but a human-in-the-loop workflow is required to guide ADR-by-ADR resolution, supersession, and traceability updates.

The limitation of automated ADR impact classification is that it cannot autonomously finalize architectural decisions; it requires a human-in-the-loop resolution workflow and optionally invokes a technical director gate to validate updates before applying traceability changes.