propagate-design-change

Automating ADR impact analysis tracks GDD revisions by reading and comparing your Game Design Document content with existing Architecture Decision Records. It identifies outdated decisions, checks the traceability index, and generates a detailed report on potential architectural impacts.

A traceability index in game development architecture maps relationships between Game Design Documents and technical decisions. When a GDD is revised, the index is scanned alongside ADRs to detect which architectural decisions may be stale and require resolution guidance.

To update ADRs after changing a Game Design Document, run an automated impact analysis command targeting your GDD file path. This provides step-by-step resolution guidance for updating affected Architecture Decision Records and other relevant documents.

Yes, ADR impact analysis requires Git commands and YAML parsing to function properly. The automated scanning process also needs file read and write access to compare GDD content, check the traceability index, and update outdated architectural decisions.

The best way to identify outdated architectural decisions is to automate ADR impact analysis on GDD revisions. This approach automatically scans all Architecture Decision Records and the traceability index, detecting stale decisions and guiding users through the necessary updates.

You need to run ADR impact analysis whenever you revise a Game Design Document. This ensures that any changes to game design requirements are automatically checked against your traceability index and existing architectural decisions to prevent stale documentation.