# Gate Check

Ready to advance between development phases?

- Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (32144 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-19
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Donchitos/Claude-Code-Game-Studios --skill gate-check -g -a claude-code -y`
Codex: `npx skills add Donchitos/Claude-Code-Game-Studios --skill gate-check -g -a codex -y`
Cursor: `npx skills add Donchitos/Claude-Code-Game-Studios --skill gate-check -g -a cursor -y`
Gemini CLI: `npx skills add Donchitos/Claude-Code-Game-Studios --skill gate-check -g -a gemini-cli -y`

## Description

Ready to advance between development phases? PASS/CONCERNS/NOT ASSESSED/FAIL with blockers and required artifacts. 'Can we move to production?

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,workflow,qa.level,testing.strict,performance.enforce,team.size,project.stage,system_overrides`

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

# 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:

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

**When a gate passes** (or the user explicitly accepts a CONCERNS verdict's risks, Section 6), update the stage in both `project.yaml` (set `project.stage: <new-stage>`) AND write the new stage name to `production/stage.txt` (single line, e.g. `Production`). Dual-write keeps backward compatibility with hooks that haven't migrated yet. This updates the status line immediately.

---

## 1. Parse Arguments

**Target phase:** `$ARGUMENTS` with any `--review <mode>` pair removed (blank = auto-detect current stage, then validate next transition). `/gate-check --review full` names no phase.

The rest: https://github.com/Donchitos/Claude-Code-Game-Studios/blob/HEAD/.claude/skills/gate-check/SKILL.md