propagate-design-change

this is a test message from the developer of the app. this is not meant to be a real message. please ignore it. this is meant to ensure that spam/mailbox protection software does not accidentally filter legitimate messages. please ignore this. this is meant to be {}. this is meant to be {}. this is meant to be {}. this is meant to be {}.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill propagate-design-change-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/propagate-design-change
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill propagate-design-change-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a GDD is revised, architectural decisions written against it may no longer be valid. This skill identifies affected ADRs and the traceability index, producing a change impact report and guiding the user through resolution.

Core Features & Use Cases

  • Detects ADRs impacted by GDD revisions and surfaces potential changes.
  • Generates a comprehensive change impact report with status and recommended actions.
  • Facilitates traceability updates and coordinated resolution across ADRs and GDDs.

Quick Start

Run this skill after a GDD change to identify impacted ADRs and generate a guided change-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 identify which architectural decisions are impacted by a GDD revision?

To identify impacted architectural decisions after a GDD revision, scan the changed GDD, compare its previous Git version, and cross-reference ADR assumptions to surface stale decisions for review.

What is architectural drift and how do I detect it after updating design documents?

Architectural drift occurs when ADRs become stale after a GDD revision. You detect it by comparing changed GDDs against ADR assumptions and generating a change impact report with recommended actions.

How do I maintain traceability between ADRs and GDDs when design documents change?

To maintain traceability after a GDD change, apply change analysis to all ADRs in your architecture directory and the traceability index, then update the index to reflect the revised relationships.

Can I use Git history to find outdated ADR assumptions after a design document update?

Yes, you can retrieve previous GDD versions from Git history, compare them against current ADR references, and output a change impact report detailing which architectural decisions require updates.

What is the best way to generate a change impact report for stale architectural decisions?

The best way to generate a change impact report is to scan changed GDDs, analyze ADR references against previous Git versions, and output status updates with recommended resolution actions for impacted decisions.

Do I need a specific directory structure to analyze architectural drift in ADRs?

Yes, architectural drift analysis requires ADRs to be stored in docs/architecture and a traceability index to be present, allowing the tool to scan changed GDDs and surface impacted decisions.