!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. --depth is the pre-1.1 name for the same flag: treat --depth <mode> exactly as --review <mode>, and say once that it was renamed. Given both, --review wins and --depth is ignored, say so. No block → defaults in .claude/docs/config-resolution.md.

Design Review

Phase 0: Parse Arguments

See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md, the spawned agent reads its own gate file; do not read it in the parent session.

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).

workflow for the GDD under review, use the system_overrides row for <system> if the block lists one, else the project value. Validation scope follows the tier:

• full, all 8 sections validated; any missing section blocks approval.
• standard, the 5 required sections (Overview, Detailed Rules, Edge Cases, Dependencies, Acceptance Criteria) block if missing; Formulas blocks only when the system defines numeric rules (rates, curves, thresholds, costs, the category is a hint, not the test); Player Fantasy and Tuning Knobs are advisory (warn, never block) unless workflow_overrides require them.
• minimal, no GDD is expected; if one exists, validate the 5 standard sections advisorily.

Resolved mode controls how thorough this review is:

• full: Complete review, all phases + specialist agent delegation (Phase 3b)
• lean: All phases, no specialist agents, faster, single-session analysis
• solo: Phases 1-4 only, no delegation, no Phase 5 next-step prompt, use when called from within another skill

---