gate-check

Validate project readiness between development phases using artifact and director assessments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you determine whether a game project is ready to advance to a specified next development phase by checking for required artifacts, quality expectations, and actionable blockers.

Core Features & Use Cases

  • Phase-gated readiness validation: Produces a PASS/CONCERNS/FAIL verdict for transitions like Concept → Systems Design, or Technical Setup → Pre-Production.
  • Artifact + quality checks: Verifies existence and meaningful content for key docs (GDDs, architecture docs, ADRs, UX specs) and performs targeted cross-document consistency checks.
  • Director panel assessment: Summons creative, technical, producer, and art directors to assess readiness in parallel and summarizes their readiness signals before finalizing the verdict.
  • Stage update on pass: When the gate passes and you confirm, it updates production/stage.txt with the next stage name.

Quick Start

Run gate-check for the next phase by asking the AI: "Check if we can advance to Production using lean review mode."

Frequently Asked Questions about gate-check

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

FAQPage Schema
How do I check if my game project is ready to move to the next development phase?

Phase-gate readiness validation checks artifact presence, content quality, and actionable blockers to produce a PASS, CONCERNS, or FAIL verdict for advancing between game development phases.

What is a phase gate review in game development?

A phase gate review validates project readiness to advance between development phases by verifying required artifacts like GDDs and ADRs, performing cross-document consistency checks, and assessing quality expectations.

How do I validate required artifacts like GDDs and architecture docs before starting pre-production?

Artifact and quality checks verify the existence and meaningful content of key documents like GDDs, architecture docs, ADRs, and UX specs, while performing targeted cross-document consistency checks before phase advancement.

Can I use director panel assessments for project readiness validation?

Yes, director panel assessments summon creative, technical, producer, and art directors to assess readiness in parallel, summarizing their readiness signals before finalizing the phase-gate verdict.

Does phase-gate logic require YAML definitions to validate stage transitions?

Yes, phase-gate logic requires YAML-defined rules to validate project readiness, utilizing conditional prompts for unverifiable items and parallel director execution to assess stage transitions.

When should I not auto-detect the current development stage for phase gate reviews?

Auto-detection of the current stage is optional and requires explicit user confirmation, meaning you should bypass it when your stage tracking is ambiguous or you need to manually enforce a specific transition checkpoint.