Explore all skills by this author →

Verified:GitHub

propagate-design-change

Scan ADRs and GDD revisions to identify stale architectural decisions.

Updated Mar 26, 2026

Search Tags:#architecture #adr #traceability #report #resolution #gdd #change-impact

Ready to run

npx skills add https://github.com/LordKuper/agentic-game-studio --skill propagate-design-change-lordkuper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/propagate-design-change
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill propagate-design-change-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a GDD is revised, architectural decisions linked in ADRs and the traceability index may become outdated. This skill scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale, and it produces a change impact report to guide the user through resolution.

Core Features & Use Cases

Scans ADRs and the traceability index to identify stale architectural decisions after a GDD revision.
Generates a comprehensive change impact report outlining affected ADRs and suggested actions.
Guides users through resolution with recommended updates or replacements and keeps traceability in sync.

Quick Start

Run /propagate-design-change design/gdd/combat-system.md to begin.

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 a GDD revision?▼

To identify stale ADRs after a GDD revision, scan your architecture decision records and traceability index to find outdated decisions. This process compares GDD versions to produce a change impact report detailing affected artifacts and resolution guidance.

What is architectural change impact analysis for game design documents?▼

Architectural change impact analysis for game design documents is the process of scanning ADRs and GDD revisions to detect stale decisions. It analyzes design-traceability to produce a report outlining affected artifacts and recommended resolution actions.

How do I keep architecture traceability in sync when design documents change?▼

To keep architecture traceability in sync when design documents change, scan all ADRs against the revised GDD. This generates a change impact report that guides you through necessary updates or replacements to maintain traceability.

How do I generate a change impact report for outdated architecture decisions?▼

To generate a change impact report for outdated architecture decisions, load your architecture inputs and compare ADR versions against recent GDD revisions. The resulting report identifies stale decisions and provides recommended resolution actions.

Do I need a traceability index to analyze architectural change impact?▼

Yes, a traceability index is needed to analyze architectural change impact effectively. The skill scans both the traceability index and ADRs alongside GDD revisions to accurately identify which architectural decisions are now potentially stale.

Related Skills

Explore More Design & Creative Skills→

jmagly

175

architecture-evolution

Analyze architecture change impact and generate ADRs and migration plans.

Community

Advanced

HechaoYannet