skills.rest
packetalien
packetalienCOMMUNITY
Explore all skills by this author →
𝕏@packetmonkGitHub

propagate-design-change

Analyze revised GDDs against ADRs and generate change impact reports.

Updated Apr 25, 2026
Search Tags:#architecture#adr#traceability#impact-analysis#gdd#propagate#design-change
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill propagate-design-change-packetalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/propagate-design-change
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill propagate-design-change-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural changes often ripple into ADRs and GDDs, leaving decisions outdated. This skill automates propagation analysis to surface impacted decisions and guide resolution.

Core Features & Use Cases

  • Impact analysis: compares changed GDDs against ADRs to identify stale assumptions.
  • Report generation: produces a structured change impact report with recommended actions.
  • Traceability updates (optional): supports updating the traceability index and ADRs to reflect new constraints.

Quick Start

Invoke the propagate-design-change workflow to analyze a revised GDD against existing ADRs and generate a 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 stale ADRs after updating my GDD?▼

Impact analysis identifies stale ADRs by comparing revised GDD content against prior ADR assumptions across the full traceability set. It computes per-ADR validity and generates a structured change impact report to guide resolution.

What is architectural traceability and when do I need to propagate design changes?▼

Architectural traceability links design decisions (ADRs) to guiding documents (GDDs). You need to propagate design changes when architectural updates occur, leaving existing decisions outdated and requiring validation against the new constraints.

How do I generate a change impact report for outdated architectural decisions?▼

Generating a change impact report involves loading ADRs and revised GDDs, computing per-ADR validity, and enforcing git history checks. The analysis surfaces impacted decisions and optionally writes change-impact documents to reflect new constraints.

Does this impact analysis workflow require git history checks before processing ADRs?▼

Yes, the workflow enforces git history checks before loading ADRs and GDDs. This ensures the traceability analysis operates on the correct versioned state of your architectural decisions and design documents.

Can I automatically update the traceability index after fixing stale design decisions?▼

Yes, the workflow optionally updates the traceability index and ADRs to reflect new constraints after identifying stale decisions. This ensures your architectural documentation remains synchronized with the revised GDD content.

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
imgamerimgamer

propagate-design-change

Detect stale architectural decisions after Game Design Document revisions.

Community
Advanced
johnatas-henriquejohnatas-henrique

propagate-design-change

Scan ADRs and traceability index to classify GDD change impacts.

Community
Advanced
striderZAstriderZA
72

propagate-design-change

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

Community
Advanced