propagate-design-change

To identify stale architecture decisions after a game design document revision, scan all architecture decision records and traceability indexes against the updated GDD. This process maps design changes to affected decisions, classifying each ADR as still valid, needing review, or likely superseded to eliminate manual cross-referencing.

Architecture traceability impact analysis in game development tracks dependencies between technical decisions and game design documents. It automatically flags invalidated architecture decision records when design changes occur, producing structured impact reports that classify ADR validity and guide resolution workflows.

To update architecture decision records when game design changes, run an automated scan against the revised game design document. This generates a change impact report classifying affected ADRs, then walks you through modifying superseded records and updating traceability indexes to reflect the new design.

Yes, you can map game design document changes to specific architecture decisions automatically by scanning existing ADRs and traceability indexes. The analysis matches GDD revisions against documented technical decisions, instantly flagging related records like combat networking or physics rules that require revision.

Stale ADR detection operates without external dependencies, scanning your local architecture decision records and traceability indexes directly. It processes your updated game design document path to generate impact reports and guide resolution workflows entirely within your existing game development environment.

You should run an architecture traceability scan immediately after any game design document revision to prevent misaligned technical architecture. Running this impact analysis detects invalidated ADRs early, guiding document updates and preventing wasted rework before development proceeds on outdated assumptions.