Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/propagate-design-change
When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
2 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 2 comparable cases; this report requires 8.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Please run the design change propagation tool on our project without specifying a GDD file.
| Checked | Without skill | With skill |
|---|---|---|
| Displays error message stating that a GDD path argument is required. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow,system_overrides
Resolved above — use as-is; --review overrides review_mode for this run. No
block → defaults in .claude/docs/config-resolution.md.
When a GDD changes, architectural decisions written against it may no longer be valid. This skill finds every affected ADR, compares what the ADR assumed against what the GDD now says, and guides the user through resolution.
Usage: /propagate-design-change design/gdd/combat-system.md
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt — ADR/schema impacts here fall
under schema_changes and architecture_decisions).
Workflow tier: resolve for the changed GDD's system (per
.claude/docs/workflow-modes.md): use the
system_overrides row for that system if the block lists one, else the
project value. (A system pinned minimal has no ADRs even on a standard
project — so its change is N/A.) It scopes the cascade: full cascades across all
ADRs; standard checks only critical (Foundation-layer) ADRs plus any ADR
referencing the changed GDD; minimal is not applicable — no ADRs to cascade.
See Step 4.
A GDD path argument is required. If missing, fail with:
"Usage:
/propagate-design-change design/gdd/[system].mdProvide the path to the GDD that was changed."
Verify the file exists. If not, fail with:
"[path] not found. Check the path and try again."
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.