gate-check

Validate project phase transitions by checking required artifacts and quality criteria.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill gate-check-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-check
Source: https://github.com/dnkrow/skill/tree/main/claude-global/gate-check
Command: npx skills add https://github.com/dnkrow/skill --skill gate-check-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents moving forward in a game project without the required design, technical, production, and QA artifacts in place, reducing costly rework and phase derailment.

Core Features & Use Cases

  • Phase-gated readiness verdicts: Produces a PASS/CONCERNS/FAIL assessment with specific blockers, tailored to the targeted transition (e.g., Systems Design → Technical Setup, Production → Polish).
  • Artifact + quality verification: Checks for the presence and meaningful content of phase-required files (GDDs, ADRs, tests, playtests, QA evidence, etc.), and flags what is missing or incomplete.
  • Director Panel synthesis: Runs parallel assessments from Creative, Technical, Producer, and Art directors to combine domain readiness signals into the final recommendation.
  • Stage progression update: When the gate passes and the user confirms, updates production/stage.txt to the new stage name.

Quick Start

Run the gate for the next transition by invoking gate-check with the target phase argument, for example: gate-check production.

Frequently Asked Questions about gate-check

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

FAQPage Schema
What is phase gating in game development and how does it validate project readiness?

Phase gating in game development validates project readiness by checking required artifacts and quality criteria before advancing between stages like concept, pre-production, production, and polish. It produces a PASS, CONCERNS, or FAIL verdict with specific blockers to prevent costly rework.

How do I check if my game project is ready to advance to the production phase?

To check project readiness for advancing to the production phase, you run a gate-check validation against required design, technical, and QA artifacts like GDDs, ADRs, and playtest evidence. It deterministically verifies file structures and flags missing or incomplete content.

What artifacts and QA evidence are required for a phase gate review?

Required artifacts for a phase gate review include Game Design Documents (GDDs), Architecture Decision Records (ADRs), tests, playtest reviews, and QA evidence. The gate verifies both the presence and meaningful content of these files to ensure phase readiness.

Can I run parallel director panel assessments for phase readiness validation?

Yes, you can optionally run parallel director panel assessments for phase readiness validation. The gate synthesizes domain readiness signals from Creative, Technical, Producer, and Art directors to combine their assessments into the final recommendation.

Does gate-check require a specific configuration format to validate phase transitions?

Gate-check requires a YAML-specified configuration to validate phase transitions. This configuration drives deterministic file-structure checks via reading and globbing to locate required artifacts and assess whether the project meets the criteria to advance.

What happens when a phase gate passes and the project is ready to advance?

When a phase gate passes and the user confirms, the system updates the production/stage.txt file with the new stage name. This stage progression update records the transition, such as moving from Systems Design to Technical Setup or Production to Polish.