gate-check
Skill9 starsChanged 7 months agoMITView on GitHub
Stage gate check — does the project meet criteria to advance to the next production phase (pre-prod → prod → polish → live)?
21 other projects use a version of this.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- supernovae-st/nikatheir own version, first seen Nov 12, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- microsoft/cat-agent-skillstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
Used with
Projects with it also use setup-engine, team-level and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
lilangMaxSkillasset-spec
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Also in 10 projects that use this
lilangMaxSkillcreate-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Also in 10 projects that use this
- +1 more from CoralGame
- +5 more from lilangMax
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- microsoft/cat-agent-skills★ 108same name
- supernovae-st/nika★ 100same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- phj128/autoworker★ 18same name
- dawn840705/codex-code-studios★ 17same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 66
Run /project-stage-detect if unclear.
- Distinctive: line 78
If ALL criteria met → Go
- Distinctive: line 79
If some criteria missed → No-go with blockers listed
- Distinctive: line 80
If close but not complete → "Go with caveats" (user decides risk tolerance)
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/gate-check — Stage Gate Review
Delegate to: producer (with technical-director, qa-lead, creative-director for respective areas)
Purpose
Stage gates force a deliberate decision about whether to move to the next production phase. Without gates, projects drift — always "almost ready" to start production, or "almost ready" to ship.
Stages
Pre-production → Production
Gate criteria:
- Master GDD exists and reviewed
- Creative pillars defined (3-5, 1 phrase each)
- Core loop defined (30s / 5min / session / meta)
- Target audience identified
- Monetization strategy drafted
- Target metrics set (retention, session, revenue if applicable)
- Tech stack decided (sync tool, UI framework, packages)
- Systems-index exists with priority
- 2-3 top systems have detailed GDDs
- Prototype or proof-of-concept validates core loop
- Team capacity matches estimated scope (or scope cut accordingly)
Production → Polish
Gate criteria:
- All core systems implemented (from systems-index P0/P1)
- Game is playable end-to-end (intro → core loop → meta)
- No S0 bugs open
- All planned features either done or explicitly cut
- Basic performance targets met (30 FPS mobile, server heartbeat < 33ms)
- Security audit has been run at least once
- DataStore schema is frozen (no more breaking changes)
- Analytics events implemented
- At least one external playtest (not just devs) completed
Polish → Live (Launch Ready)
Gate criteria:
- Zero S0 bugs
- Zero S1 bugs in critical paths
- Performance targets exceeded on target devices
- Security audit passed with no Critical findings
- Content policy review passed
- All launch marketing materials ready
- Community channels active
- Rollback plan tested
- Soft launch retention > target (D1 > 20%, ideally > 25%)
- Server costs projected and manageable
- Team ready for launch support
Live → Live Service Optimization
Gate criteria (do we continue investing?):
- Retention trending up or stable
- Revenue meets minimum threshold
- Community engaged (growing Discord, positive reviews)
- Technical debt manageable
- Team has capacity for sustained live-ops
Steps
1. Current Stage
Run /project-stage-detect if unclear. Get the current stage.
2. Target Stage
"What stage are you trying to advance to?"
3. Run the Checklist
For the target transition, go through each criterion:
- Verify each item
- Delegate to the relevant specialist for verification (e.g., security criteria → exploit-security-specialist)
- Record pass/fail/partial
4. Assess Readiness
- If ALL criteria met → Go
- If some criteria missed → No-go with blockers listed
- If close but not complete → "Go with caveats" (user decides risk tolerance)
5. Generate Gate Report
# Gate Check: [Current Stage] → [Target Stage]
**Date**: YYYY-MM-DD
**Reviewer**: [user]
## Current Status
[Summary of current state]
## Criteria
| Criterion | Status | Notes |
|-----------|--------|-------|
| Master GDD exists | ✅ | |
| Core loop defined | ⚠️ Partial | Meta loop undefined |
| Creative pillars | ✅ | |
| ... | ... | ... |
## Met
[List of passing criteria]
## Not Met / Blockers
1. [Blocker with specific remediation]
2. [Blocker with specific remediation]
## Recommendation
[ ] **PASS** — advance to next stage
[X] **HOLD** — address blockers first
[ ] **PASS WITH CAVEATS** — advance accepting documented risks
## Next Steps (if HOLD)
1. [Action item]
2. [Action item]
## Target Re-review Date
YYYY-MM-DDSave to production/gates/gate-<stage>-<date>.md on approval.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

