propagate-design-change

Identify and report GDD change impacts on architectural decisions.

Updated May 16, 2026
One-click install
npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill propagate-design-change-seonghuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/SeongHuni/LightNShadowSurviver/tree/main/GameStudio/codex/skills/propagate-design-change
Command: npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill propagate-design-change-seonghuni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the identification of stale architectural decisions when a Game Design Document (GDD) is revised, streamlining the process of updating related architectural documents.

Core Features & Use Cases

  • Automated Impact Analysis: Identifies which architectural decisions are affected by changes in the GDD.
  • Change Impact Report: Generates a detailed report on the impact of GDD changes.
  • User Guidance: Provides step-by-step guidance for resolving the impact on architectural decisions.
  • Use Case: When a GDD is updated, this Skill can be used to automatically check all related architectural decision records (ADR) and update them as necessary.

Quick Start

Run the /propagate-design-change design/gdd/combat-system.md command to analyze the impact of changes on the combat system ADR.

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 architectural decisions after updating a Game Design Document?

To identify stale architectural decisions after a Game Design Document update, you need an automated impact analysis tool. This Skill detects which architectural decision records are affected by GDD revisions and generates a detailed change impact report for review.

Can I use Git to track the impact of GDD changes on architectural decisions?

Yes, you can use Git to track the impact of GDD changes on architectural decisions. This Skill utilizes Git for version control and diffing to automatically identify affected architectural decision records and output an impact report.

What is the best way to automate impact analysis for game design revisions?

The best way to automate impact analysis for game design revisions is using a dedicated tool that compares GDD versions. This Skill automates this process by diffing the Game Design Document and pinpointing exactly which architectural decisions require updates.

Do I need to manually check all ADRs when a Game Design Document is modified?

No, you do not need to manually check all ADRs when a Game Design Document is modified. This Skill automatically scans related architectural decision records, identifies the impact of the GDD changes, and provides step-by-step guidance for resolving the affected architectural decisions.

How do I generate a change impact report for architectural decisions based on GDD updates?

To generate a change impact report for architectural decisions based on GDD updates, you run the analysis command with your GDD file path. The Skill outputs a detailed report identifying affected architectural decisions and guiding you through the resolution process.

What format does the Game Design Document need to be in for automated impact analysis?

The Game Design Document needs to be in a Markdown file format for automated impact analysis. The Skill requires access to the GDD and its associated architectural decision records to perform Git version control diffing and generate the impact report.