design-review

## Phase 0: Parse Arguments Extract `--depth [full|lean|solo]` if present. Default is `full` when no flag is given. **Note**: `--depth` controls the *analysis depth* of this skill (how many specialist agents are spawned). It is independent of the global review mode in `production/review-mode.txt`, which controls director gate spawning. These are two different concepts — `--depth` is about how thoroughly *this* skill analyses the document. - **`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 --- ## Phase 1: Load Documents Read the target design document in full. Read CLAUDE.md to understand project context and standards. Read related design documents referenced or implied by the target doc (check `design/gdd/` for related systems). **Dependency graph validation:** For every system listed in the Dependencies section, use Glob to check whether its GDD file exists in `design/gdd/`. Flag any that don't exist yet — these are broken references that downstream authors will hit. **Lore/narrative alignment:** If `design/gdd/game-concept.md` or any file in `design/narrative/` exists, read it. Note any mechanical choices in this GDD that contradict established world rules, tone, or design pillars. Pass this context to `game-designer` in Phase 3b. **Prio...