skills.rest
frabcd
frabcdCOMMUNITY
Explore all skills by this author →
GitHub

propagate-design-change

Identifies stale architecture decision records after a game design document revision.

13|Updated Jul 30, 2026
Search Tags:#architecture#adr#impact analysis#game design#traceability#change management#gdd
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill propagate-design-change-frabcd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/propagate-design-change
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill propagate-design-change-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Game Design Document (GDD) is revised, architecture decision records (ADRs) written against the old version can silently become outdated. This Skill detects which ADRs are affected by a GDD change and guides you through resolving each one. ## Core Features & Use Cases - Change Detection: Diffs the current GDD against its previous git version to summarize changed and unchanged sections. - Impact Classification: Scans all ADRs in docs/architecture and classifies each as Still Valid, Needs Review, or Likely Superseded based on referenced requirements. - Guided Resolution: Walks through each affected ADR individually, offering options to mark superseded, update in place, keep, or skip, then updates the traceability index. - Use Case: After revising your combat-system GDD, run this Skill to find that ADR-0003 assumed a hit-point formula that no longer exists, mark it superseded, and write a change impact report. ## Quick Start Run propagate-design-change on design/gdd/combat-system.md to find which architecture decisions are affected by my latest GDD revision.

Frequently Asked Questions about propagate-design-change

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

FAQPage Schema
How do I find which ADRs are affected by a GDD change?▼

Run the skill with the path to the revised GDD, for example design/gdd/combat-system.md. It diffs the file against its previous git version, scans all ADRs in docs/architecture, and reports which ones reference changed requirements.

How does design change impact analysis work with architecture decision records?▼

The skill compares each ADR's GDD Requirements Addressed table against the current GDD text. It classifies every affected ADR as Still Valid, Needs Review, or Likely Superseded, then asks you how to resolve each one individually.

Does propagate-design-change require git history for the GDD?▼

Yes, it runs git show HEAD on the GDD path to retrieve the previous committed version for comparison. If the file is new with no history, it reports there is nothing to propagate and stops.

Can the skill modify or delete my ADR files automatically?▼

No, it is non-destructive and asks for confirmation before every file write. It only adds Superseded by notes to ADR status lines and never deletes ADR content.

What happens if no traceability index exists in the project?▼

The skill still performs the full impact analysis using the ADRs' own requirement tables. Updating docs/architecture/architecture-traceability.md is conditional and only occurs if that file exists.

Related Skills

Explore More Software Engineering Skills→
Euraika-LabsEuraika-Labs
14

propagate-design-change

Detect and report ADRs impacted by revised game design documents.

Official
Advanced
rickardprickardp
2

blueprint:supersede

Replace or deprecate ADRs while preserving decision history and rationale.

Community
Advanced
imclabimclab
1

propagate-design-change

Compare revised GDDs against previous git versions to classify impacted ADRs.

Official
Advanced
thilthpc01208thilthpc01208

propagate-design-change

Scans ADRs and traceability index to identify architectural documents impacted by GDD changes.

Community
Advanced