What problem does it solve?
When a Game Design Document (GDD) is revised, architectural decision records (ADRs) written against the old version may become invalid, leading to inconsistent system architecture, wasted development effort, and technical debt if mismatches are not caught early.
Core Features & Use Cases
- Stale ADR Detection: Scans all ADRs and the requirements traceability index to identify which architectural decisions reference the changed GDD.
- Conceptual Diff Analysis: Compares the previous committed version of the GDD to the current revision to pinpoint exactly what changed.
- Impact Classification: Rates each affected ADR as Still Valid, Needs Review, or Likely Superseded, and generates a full change impact report with recommended resolution actions.
- Use Case: If you revise the combat system GDD to add a new stamina mechanic, this skill will automatically flag any existing ADRs related to combat that assume the old stamina rules, saving hours of manual cross-referencing.
Quick Start
Use the propagate-design-change skill to analyze the impact of the revised GDD located at design/gdd/combat-system.md.