propagate-design-change

Analyze GDD diffs and traceability mappings to classify ADR impact statuses.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill propagate-design-change-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/propagate-design-change
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill propagate-design-change-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents architectural drift by identifying which ADRs become stale after a Game Design Document (GDD) revision.

Core Features & Use Cases

  • GDD revision impact analysis: Reads the changed GDD, compares it to the prior git version, and summarizes what sections changed.
  • ADR traceability-driven triage: Loads ADRs from docs/architecture/, finds which ADRs reference the changed GDD, and assesses whether each ADR is still valid, needs review, or is likely superseded.
  • Guardrailed resolution workflow: In technical impact review modes, routes the impact assessment through the technical director gate, then asks you per-ADR how to resolve updates and writes an optional change-impact report.

Real-world use case: You update combat rules in your GDD and want to know exactly which architecture decisions and ADRs need revision to match the new design.

Quick Start

Use /propagate-design-change 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 check which architecture decision records are affected by a game design document change?

ADR impact analysis identifies affected architecture decision records by comparing git diffs of your game design document against a traceability index, classifying each ADR as valid, needing review, or likely superseded.

What is ADR traceability and when do I need it for game development?

ADR traceability maps relationships between your game design document and architecture decision records. You need it when GDD revisions alter requirements, potentially invalidating prior architectural assumptions and acceptance criteria across your project.

How to propagate design changes to architecture decision records using a governance workflow?

Propagate design changes by loading the updated GDD diff and traceability index, classifying ADR impact status, then routing the assessment through an approval-gated technical review to guide per-ADR resolution updates.

Can I use git diff to automate ADR impact analysis for updated requirements?

Yes, the workflow reads your changed game design document, compares it to the prior git version to summarize section changes, and deterministically loads ADRs from docs/architecture/ to assess architectural drift.

Does the ADR resolution process require a technical director approval gate?

In technical impact review modes, the ADR resolution workflow routes the impact assessment through a technical director gate, then asks you per-ADR how to resolve updates and writes an optional change-impact report.

What are the limitations of using traceability mappings for ADR governance?

ADR governance via traceability mappings relies on deterministic loading from docs/architecture/ and a pre-existing traceability index. It cannot assess architectural drift if ADRs lack explicit references to the updated GDD sections.