skills.rest
striderZA
striderZACOMMUNITY
Explore all skills by this author →
WebsiteGitHub

propagate-design-change

Identifies ADRs affected by revised GDD files and classifies their staleness statuses.

72|7|Updated Apr 29, 2026
Search Tags:#adr#impact analysis#traceability#git diff#gdd#documentation governance#architecture change
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill propagate-design-change-striderza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/propagate-design-change
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill propagate-design-change-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents architectural drift by detecting which ADRs become stale after a GDD revision, then helps you resolve each impacted decision.

Core Features & Use Cases

  • Change impact analysis: Compares what a changed GDD section used to say versus what it says now, and summarizes the revision.
  • ADR traceability lookup: Loads ADRs and cross-references their “GDD Requirements Addressed” mappings to find which ADRs reference the modified GDD.
  • Staleness classification & guided resolution: Classifies each impacted ADR as still valid, needs review, or likely superseded, then asks you what to do per ADR.

Quick Start

Run the propagate-design-change skill with the revised GDD path, for example: /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 find out which ADRs are affected when a GDD markdown file is revised?▼

ADR traceability lookup scans requirement mappings in your architecture docs to identify which ADRs reference the modified GDD. It cross-references GDD Requirements Addressed fields to pinpoint impacted decisions after a revision.

What is the best way to prevent architectural drift after updating a design document?▼

Preventing architectural drift requires comparing current and previous GDD versions via git diff to classify impacted ADRs. The analysis flags ADRs as still valid, needing review, or likely superseded to guide resolution.

How does git diff help classify ADR staleness after a design change?▼

Git diff compares previous and current GDD versions to summarize section revisions. This comparison classifies ADR staleness by checking if updated GDD requirements invalidate existing architectural decisions or assumptions.

Can I automatically generate a change-impact document for stale ADRs?▼

You can generate a change-impact document after confirming the classified impact report. The skill produces this document to record which architectural decisions require updates based on the GDD revision analysis.

Do I need existing traceability mappings to run an architecture change impact analysis?▼

Yes, existing traceability mappings are required. The analysis loads ADR requirement mappings from your architecture docs to cross-reference modified GDD sections and detect which decisions have become stale.

What happens if I run impact analysis on an invalid GDD path?▼

The impact analysis validates the provided GDD path before proceeding. If the path is invalid, the process stops to ensure it only reads current and previous GDD versions from correct locations via git.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

propagate-design-change

Analyze revised GDDs to identify impacted ADRs and generate change-impact reports.

Community
Advanced
WindXRanWindXRan

propagate-design-change

Compare ADR assumptions against revised GDD text and classify impacts.

Community
Advanced
imclabimclab
1

propagate-design-change

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

Official
Advanced
sumilee-pcusumilee-pcu

propagate-design-change

Analyze GDD revisions against ADRs to identify and resolve architectural inconsistencies.

Community
Advanced