propagate-design-change

Scan ADRs and traceability index to classify GDD change impacts.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill propagate-design-change-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/propagate-design-change
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill propagate-design-change-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about propagate-design-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify stale ADRs after revising a Game Design Document?

To identify stale ADRs after revising a Game Design Document, scan all architectural decision records and the requirements traceability index to detect references to the changed GDD, then perform a conceptual diff to pinpoint inconsistencies.

What is the best way to analyze the architectural impact of a GDD revision?

The best way to analyze the architectural impact of a GDD revision is to perform a conceptual diff between old and new versions, classifying each affected ADR by severity as Still Valid, Needs Review, or Likely Superseded.

How do I maintain requirements traceability when game design changes occur?

You maintain requirements traceability during game design changes by scanning the traceability index for affected decisions, generating a structured change impact report, and updating ADR statuses to preserve architectural consistency.

Can I automate ADR management to flag decisions invalidated by GDD updates?

Yes, you can automate ADR management to flag invalidated decisions by scanning existing records against the revised GDD, comparing conceptual differences, and generating resolution recommendations for mismatched architectural decisions.

Does tracking architectural decisions require a manual conceptual diff for every GDD update?

Tracking architectural decisions does not require a manual conceptual diff for every GDD update, as automated scanning of the traceability index and ADRs identifies affected records and classifies impact severity automatically.