!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,review_gate,automation,automation_always_ask,workflow,system_overrides

Resolved above, use as-is; --review overrides review_mode for this run. No block → defaults in .claude/docs/config-resolution.md.

Ask with the question tool. Without one, list the options numbered and end your turn to wait. A skipped or dismissed question is not an answer: ask again in plain text.

Propagate Design Change

When a GDD changes, the architecture decisions written against it may no longer hold. This skill finds every ADR the change touches, compares what the ADR assumed with what the GDD says now, and walks the user through each one.

Example: /propagate-design-change design/gdd/combat-system.md

Asks follow .claude/docs/automation-modes.md (collaborative always asks, guided asks on major choices, autonomous logs and goes on; automation_always_ask categories always ask: an ADR impact here is schema_changes and architecture_decisions).

Tier. workflow for the changed GDD's system: its system_overrides row if there is one, else the project value. A system pinned minimal has no ADRs even on a standard project. full checks every ADR; standard checks the critical (Foundation-layer) ADRs and any ADR that names the changed GDD; minimal has nothing to check (Phase 4).

Phase 1: The GDD path

The text typed after the skill name, with any --review <mode> pair removed, is the changed GDD. It is required. Missing: "Usage: /propagate-design-change design/gdd/[system].md, give the path to the GDD that changed." Not a file: "[path] not found. Check the path and try again."

Phase 2: What changed

Ask git, never compare two whole documents by eye:

git diff HEAD -- design/gdd/[filename].md

Empty: the change may be committed already, so widen to the last commit that touched it: git diff HEAD~1 HEAD -- design/gdd/[filename].md.