propagate-design-change

To trace GDD revision impact on architecture decision records, you need to load the current and previous committed GDD versions to identify requirement changes, then cross-reference the traceability index to find affected ADRs and generate a per-ADR change impact assessment report.

Maintaining ADR traceability during requirement changes involves comparing the revised GDD against the previous committed version, loading the architecture traceability index, and classifying each referenced ADR as Still Valid, Needs Review, or Likely Superseded to prevent architectural drift.

To update stale architecture decisions after modifying a game design document, you run an impact analysis workflow that classifies affected ADRs and asks per-ADR what resolution action to take, requiring explicit approval before writing any updates to the files.

The ADR impact analysis workflow requires a traceability index that links architecture decision records to the GDD, allowing the system to load referenced ADRs and quantify coverage scope when validating whether their assumptions still match the latest requirements.

You cannot fully automate superseding invalid architecture decisions because the workflow requires explicit per-ADR approval before writing files, classifying ADRs as Likely Superseded to guide you through the resolution process rather than auto-deleting or overwriting them.