gate-check

# Phase Gate Validation This skill validates whether the project is ready to advance to the next development phase. It checks for required artifacts, quality standards, and blockers. **Distinct from `/project-stage-detect`**: That skill is diagnostic ("where are we?"). This skill is prescriptive ("are we ready to advance?" with a formal verdict). ## Production Stages (7) The project progresses through these stages: 0. **Exploration** — Pre-workflow: rapid prototyping multiple ideas (/explore) 1. **Concept** — Brainstorming, game concept document 2. **Systems Design** — Mapping systems, writing GDDs 3. **Technical Setup** — Engine config, architecture decisions 4. **Pre-Production** — Prototyping, vertical slice validation 5. **Production** — Feature development (Epic/Feature/Task tracking active) 6. **Polish** — Performance, playtesting, bug fixing 7. **Release** — Launch prep, certification **Special gate: `workflow-selection`** — Only valid from the Exploration stage. When it passes, it sets both `production/workflow-mode.txt` (hybrid or full) and `production/stage.txt` (Concept). See the Workflow Selection gate below. --- ## 1. Parse Arguments **Target phase:** `$ARGUMENTS[0]` (blank = auto-detect current stage, then validate next transition) Also resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` Note: ...