propagate-design-change

Analyze Game Design Document changes and generate impact reports for architectural decisions.

Updated May 24, 2026
One-click install
npx skills add https://github.com/LeKay/ai-game --skill propagate-design-change-lekay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/propagate-design-change
Command: npx skills add https://github.com/LeKay/ai-game --skill propagate-design-change-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers manage changes in the Game Design Document (GDD) and its impact on architectural decisions made in the game, ensuring that the project remains aligned and cohesive.

Core Features & Use Cases

  • Impact Analysis: Automatically scan and analyze changes in the GDD and identify affected architectural decisions.
  • Change Impact Report: Generate a detailed report on the impact of changes, guiding users through the resolution process.
  • Resolution Workflow: Offer step-by-step instructions to update or resolve outdated architectural decisions.
  • Traceability Index Update: Update the traceability index to reflect the latest changes and decisions.

Quick Start

Use the /propagate-design-change design/gdd/combat-system.md command to identify and resolve the impact of changes to the combat system's GDD.

Frequently Asked Questions about propagate-design-change

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

FAQPage Schema
How do I analyze the impact of Game Design Document changes on architectural decisions?

This Skill scans GDD file history in git to analyze changes and identifies affected architectural decisions, generating a detailed change impact report for game development projects.

What is the best way to manage GDD change impact and resolve outdated architectural decisions?

The best way to manage GDD change impact is using a resolution workflow that provides step-by-step instructions to update outdated architectural decisions and refresh the traceability index.

Do I need git to track Game Design Document changes for impact analysis?

Yes, git is required to track Game Design Document changes because this Skill relies on accessing the GDD file and its version control history to perform architectural impact analysis.

How does change management for a Game Design Document work with version control history?

Change management works by scanning version control history to detect GDD modifications, mapping them to affected architectural decisions, and guiding users through a structured resolution process.

Can I update the traceability index automatically after resolving architectural decisions?

Yes, the traceability index is updated automatically to reflect the latest GDD changes and architectural decision resolutions after completing the resolution workflow.

When should I run impact analysis on my Game Design Document?

Run impact analysis whenever changes are committed to the Game Design Document to ensure the project remains aligned and architectural decisions are promptly updated accordingly.