propagate-design-change

To find outdated ADRs after updating a Game Design Document, scan the repository's `docs/architecture` directory and compare the current GDD against the previous Git version to identify impacted architectural decision records.

Maintaining traceability between GDD changes and architecture decisions requires scanning existing ADRs for references to the changed design document and updating the traceability matrix to reflect whether each record is still valid, needs review, or is likely superseded.

Generating an impact report for affected architectural decision records involves performing a conceptual diff between the current and previous GDD versions using Git history, then classifying each referenced ADR by its updated validity status.

Yes, Git access is required to detect stale architectural decision records because the Skill needs to retrieve prior versions of the Game Design Document from the repository history to perform the conceptual diff and determine ADR impact.

You can automate updating ADR status and traceability indexes after a game design document revision by applying the impact report results to amend the markdown ADR files and modify the traceability matrix directly within the repository.

Limitations when tracking architectural impact from GDD updates include the strict dependency on Git history for version comparison and the requirement that ADRs must reside in `docs/architecture` with existing traceability index files to be detected.