skills.rest
kay6198835
kay6198835COMMUNITY
Explore all skills by this author →
GitHub

propagate-design-change

Cross-reference ADRs and traceability index to identify impacted architectural decisions.

Updated Feb 8, 2024
Search Tags:#architecture#ADR#traceability#propagation#change-impact#GDD
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill propagate-design-change-kay6198835
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propagate-design-change
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/propagate-design-change
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill propagate-design-change-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a GDD is revised, architectural decisions may become invalid. This skill scans all ADRs and the traceability index to identify which decisions are potentially stale and flags the necessary updates.

Core Features & Use Cases

  • Change impact detection: Finds ADRs affected by GDD revisions and surfaces the exact areas of drift.
  • Impact analysis & reporting: Generates a structured change impact report with statuses and recommended actions.
  • Guided resolution: Walks the user through resolution steps to re-align ADRs with the changed GDD and updated traceability.

Quick Start

Run the propagate-design-change command with the path to the changed GDD to start the analysis.

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 a GDD revision?▼

To identify stale ADRs after a GDD revision, cross-reference the updated GDD with the traceability index to surface impacted architectural decisions and flag drift. It compares the revised GDD against the version each ADR assumed.

What is architectural change impact analysis for design documents?▼

Architectural change impact analysis detects which architectural decisions become invalid when a design document changes. It generates a structured report classifying each affected ADR as Still Valid, Needs Review, or Likely Superseded.

How do I trace design changes to existing architectural decisions?▼

Trace design changes to existing architectural decisions by cross-referencing ADRs and the traceability index. This analyzes variations between the updated GDD and the version each ADR originally assumed to guide resolution steps.

Can I generate a change impact report for outdated ADRs?▼

Yes, you can generate a change impact report for outdated ADRs by analyzing the revised GDD. The report classifies each affected ADR and provides actionable recommendations for updates or replacements.

What are the limitations of automated ADR staleness detection?▼

Automated ADR staleness detection relies on cross-referencing a traceability index and the revised GDD, meaning it requires an existing traceability mapping to function. Without previously established links between ADRs and the GDD, drift cannot be surfaced.

Related Skills

Explore More Software Engineering Skills→
johnatas-henriquejohnatas-henrique

propagate-design-change

Scan ADRs and traceability index to classify GDD change impacts.

Community
Advanced
jmaglyjmagly
175

architecture-evolution

Analyze architecture change impact and generate ADRs and migration plans.

Community
Advanced
MichaelSolatiMichaelSolati

propagate-design-change

Identify stale architecture decision records affected by game design document revisions.

Community
Advanced
LordKuperLordKuper

propagate-design-change

Scan ADRs and GDD revisions to identify stale architectural decisions.

Community
Advanced