propagate-design-change

Detect stale ADRs after a Game Design Document revision by scanning all ADRs for references to the modified GDD and flagging those that require updates. This impact analysis identifies outdated architectural decisions and generates a clear report for teams to act on.

Analyze the impact of GDD changes on architecture traceability by generating a concise diff of the GDD revision and highlighting sections that affect the architecture. The Skill evaluates modified requirement IDs referenced by ADRs to maintain project consistency.

Update the architecture traceability index when ADRs become outdated by following a guided resolution workflow. This workflow helps users review, update, or supersede affected ADRs and automatically updates the traceability index to reflect the current design state.

Git access is required to trace GDD requirement IDs across ADR files because the Skill retrieves previous GDD versions for comparison. Read and write permissions for ADR files and the architecture traceability index are also necessary to execute the resolution workflow.

You can automate ADR staleness detection for version-controlled GDDs by running the Skill with the path to the revised GDD. It automatically scans all ADRs, evaluates the impact of the design changes, and presents a clear report of outdated records.

Supersede affected ADRs instead of updating them after a GDD change when the architectural decisions are fundamentally invalidated by the new design. The resolution workflow guides users through reviewing the diff to determine whether to update or supersede each flagged record.