gate
/gate
Run a milestone gate (G0 Concept, G1 Vertical slice/greenlight, G2 Content complete, G3 Polish/ship) — the Producer assembles the evidence packet against written acceptance criteria and asks the publisher to approve, cut, or kill. Use for "/game-studio:gate", "are we ready for the vertical slice", "greenlight review", "approve the milestone".
- Author
- per-simmons ↗
- Repository
- claude-game-studio ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run a milestone gate (G0 Concept, G1 Vertical slice/greenlight, G2 Content complete, G3 Polish/ship) — the Producer assembles the evidence packet against written acceptance criteria and asks the publisher to approve, cut, or kill. Use for "/game-studio:gate", "are we ready for the vertical slice", "greenlight review", "approve the milestone".
Triggers from the description
Arguments
/gate G0|G1|G2|G3 [approve|changes \"notes\"|kill]
Original author description
Run a milestone gate (G0 Concept, G1 Vertical slice/greenlight, G2 Content complete, G3 Polish/ship) — the Producer assembles the evidence packet against written acceptance criteria and asks the publisher to approve, cut, or kill. Use for "/game-studio:gate", "are we ready for the vertical slice", "greenlight review", "approve the milestone".
How it works
- Without a verdict: assemble the packet
- With a verdict (only from the user)
SKILL.md preview
---
name: gate
description: Run a milestone gate (G0 Concept, G1 Vertical slice/greenlight, G2 Content complete, G3 Polish/ship) — the Producer assembles the evidence packet against written acceptance criteria and asks the publisher to approve, cut, or kill. Use for "/game-studio:gate", "are we ready for the vertical slice", "greenlight review", "approve the milestone".
argument-hint: "G0|G1|G2|G3 [approve|changes \"notes\"|kill]"
---
# /game-studio:gate
The criteria are in `${CLAUDE_PLUGIN_ROOT}/skills/studio/references/operating-model.md` §4.
## Without a verdict: assemble the packet
1. Check each criterion against the evidence: files, `board.py list`, lint, tests, screenshots and the
fun audit. Mark each one ✓ or ✗. Add every open publisher note (`studio/notes/`) as PASS, PARTIAL or
FAIL, each with an evidence image from a real-click run on the deployed build.
2. Write `studio/gates/<G>.md`, at most 300 words:
- the criteria table;
- the decisions needed, each with a recommendation;
- the risks;
- **kill / continue / continue with cuts**.
3. Present it and stop. Never pass your own gate.
## With a verdict (only from the user)
- **approve:** `board.py milestone <next>`. Plan the next cycle and log the approval in the gate file.
- **changes:** turn the notes into tickets with owners.
- **kill:** write `studio/POSTMORTEM.md` (what went right and what went wrong, at least 5 each) and
archive the board.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · per-simmons/claude-game-studio | 90 | MIT |
| sh5623/e2e-rail | 100 | MIT |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| bitIO/wheelhouse | 100 | MIT |
| Perchusha/pitwall | 100 | MIT |
| jease0502/research-agent-kit | 100 | Apache-2.0 |
| jeffersonvalente/cardume | 100 | MIT |
| Vibecheck-QA/vibecheck | 100 | MIT |
| iankiku/forwward-teams | 100 | MIT |
Database snapshot: 13.11.2026 · package version ba9eec37c17e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 9030-game-delivery-evidence-and-greenlight-pack
Use when assembling or reviewing game greenlight, milestone, release, rights, security, player-research, build, test, live-operations, and independent-replication evidence without inflating capability claims. - 100milestone-review
Conducts a structured milestone review analyzing delivered features, metrics, blockers, and readiness for the next phase. Use when completing a milestone or when the user mentions milestone review or phase gate. - 96milestone-review
生成全面的里程碑进度审查,包括功能完整性、质量指标、风险评估和启动/不启动建议。在里程碑检查点或评估里程碑截止日期的准备情况时使用。 - 86next-tier
Move the game to its next scope tier (Toy -> Vertical slice -> MVP / Release) once the current tier is done. Use when the user says the toy or slice is done, "it's fun, let's develop it", "greenlight", "next tier", "move on to production", or when Claude keeps pushing back with… - 95complete-milestone
Orchestrate a cliban milestone end-to-end: one agent per ticket, dependency waves, isolated worktrees, integrated onto a milestone branch. Use when asked to run, drive, orchestrate, or complete a whole milestone. - 100release-readiness
WAY 12 — go / no-go report for a release or milestone. Use when the user says "release check", "go no go", "are we ready to release", "release readiness" with a milestone or version.