propagate-design-change

To trace architectural decisions affected by a GDD revision, analyze the revised GDD to surface impacted ADRs. The skill examines ADRs referencing the changed GDD, contrasts their assumptions, and outputs a change-impact report with resolution guidance.

ADRs become stale when a GDD is revised because existing architectural decisions were based on previous design assumptions. Without automatic traceability analysis, ADRs that reference the changed GDD are not updated to reflect new requirements.

Generate a change-impact report by scanning ADRs that reference the changed GDD and comparing their assumptions against the updated content. This produces a structured report with recommended resolutions and traceability adjustments.

Yes, you can analyze ADRs stored in docs/architecture against git history. The process requires access to the repository's ADR directory and reads git history to fetch previous GDD versions for assumption contrast.

The best way to maintain ADR traceability after modifying a GDD is to automatically identify affected ADRs and guide subsequent updates. This keeps design decisions aligned with the current GDD through structured resolution recommendations.

Yes, you need git history access to analyze architectural decision record impacts. Reading git history is required to fetch previous versions of the GDD and contrast their assumptions against the updated content.