gate-check

Validates readiness to advance between game development phases with a formal verdict.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill gate-check-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-check
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/gate-check
Command: npx skills add https://github.com/onemanking/the-operator --skill gate-check-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game development projects often drift between phases without clear criteria, leading to premature production work or missing artifacts. This Skill provides a structured phase gate validation that checks required artifacts and quality standards before advancing to the next development stage. ## Core Features & Use Cases - Phase Gate Validation: Checks required artifacts and quality checks for six phase transitions, from Concept through Release, producing a PASS, CONCERNS, or FAIL verdict. - Artifact Verification: Uses file scanning to confirm GDDs, architecture decision records, sprint plans, prototypes, and test suites exist with real content rather than empty templates. - Stage Tracking: Writes the new stage name to production/stage.txt when a gate passes, keeping project status current. - Use Case: Before moving from Pre-Production to Production, run the gate check to confirm your prototype validates the core loop, sprint plans exist, and all MVP-tier GDDs are complete. ## Quick Start Ask the assistant to run a gate check for the production phase to verify the project is ready to advance.

Frequently Asked Questions about gate-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate readiness to move to the next game development phase?

Run the gate check with a target phase argument, such as production or polish. The skill scans for required artifacts like GDDs, sprint plans, and ADRs, runs quality checks, and returns a PASS, CONCERNS, or FAIL verdict with specific blockers.

What artifacts are required before entering game production?

The Pre-Production to Production gate requires at least one prototype with a README, a first sprint plan in production/sprints/, and all MVP-tier GDDs completed. Quality checks confirm the prototype validates the core loop and sprint plans reference real work items.

What is the difference between gate-check and project-stage-detect?

project-stage-detect is diagnostic, answering where the project currently stands. gate-check is prescriptive, answering whether the project is ready to advance with a formal verdict, blockers, and recommendations.

Does the gate check run tests automatically?

Yes, when a test runner is configured, the skill executes the test suite via Bash as part of quality checks for gates like Production to Polish. Failing tests are reported as blockers in the verdict output.

Can I advance phases even if the gate check fails?

Yes, the verdict is advisory and never blocks the user. The skill documents risks and unverifiable items as MANUAL CHECK NEEDED, then lets the user decide whether to proceed despite concerns.