propagate-design-change

Propagate GDD changes to ADRs and generate a change-impact report.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill propagate-design-change-solace-ill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/propagate-design-change
Command: npx skills add https://github.com/solace-ill/vector-flow --skill propagate-design-change-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a GDD revision occurs, architectural decisions built against it may become outdated. This skill scans all ADRs and the traceability index to identify potentially stale decisions and produces a change impact report with guided resolution.

Core Features & Use Cases

  • Detects ADRs affected by GDD changes by comparing ADR assumptions with the updated GDD.
  • Generates a comprehensive Change Impact Report summarizing changed sections, unchanged sections, and architectural implications, then guides resolution.
  • Provides an end-to-end workflow to review, approve, and update ADRs and traceability where needed.

Quick Start

Execute propagate-design-change with the path to the changed GDD to produce the impact report.

Frequently Asked Questions about propagate-design-change

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

FAQPage Schema
How do I trace the impact of a GDD revision on existing architecture decisions?

To trace the impact of a GDD revision on architecture decisions, you can automate propagation by comparing current versus previous GDD content against ADR assumptions to produce a change-impact report with recommended actions.

How do I update stale ADRs after modifying a game design document?

Updating stale ADRs after modifying a game design document involves scanning the traceability index to identify affected decisions and guiding end-to-end resolution workflows to review, approve, and update the records.

What is architectural traceability analysis for design changes?

Architectural traceability analysis for design changes is the process of scanning ADRs and traceability indexes to detect outdated architectural assumptions and summarize architectural implications with a comprehensive change impact report.

Does this impact analysis workflow require a specific directory structure for ADRs?

Yes, this impact analysis workflow requires ADRs to be stored in the docs/architecture directory and requires an existing architecture-traceability index to successfully compare GDD content and output the report.

What is the best way to identify which ADRs are affected by a game design document update?

The best way to identify which ADRs are affected by a game design document update is to automate the comparison of ADR assumptions with the updated GDD sections to detect potentially stale decisions and generate guided resolutions.