Gate Check

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Gate Check" for me. It validates whether the project is ready to advance between development phases, with a formal verdict: PASS, CONCERNS, NOT ASSESSED or FAIL (NOT ASSESSED outranks PASS — a gate that could not check part of its scope has not established readiness). The SKILL.md is the frame: the per-gate checklists live in six files under references/ (gate-systems-design, gate-technical-setup, gate-pre-production, gate-production, gate-polish, gate-release — only the target gate's file is read), the procedure in five more (2b-workflow-tier, 3-run-gate-check, 4-assessment, 5-verdict, 6-update-stage, 7-next-steps), plus a CONTRACT.md. It runs the template's .claude/scripts/ checks (artifact-check.sh, gdd-structure-check.sh, adr-dep-graph.sh) and, for test checks, the project's test suite when a runner is configured; in lean and full review modes a panel of template director agents (creative, technical, producer, art directors) assesses the gate, while solo mode is artifact-existence checks only. It never auto-fixes a missing artifact to manufacture a PASS. The report is written to production/gate-checks/ only after the user approves ("May I write this gate check report…?"). On PASS with the user's confirmation — or on CONCERNS only when the user explicitly accepts the listed risks, never on FAIL or NOT ASSESSED — it advances the stage by running the template's set-stage.sh, which dual-writes project.stage in project.yaml and the legacy production/stage.txt and reads both back. Uniquely in this set, the skill declares itself exempt from the automation mode: its collaborative prompting always applies, because a phase gate is a deliberate human checkpoint. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/gate-check/ folder at the pinned commit: 14 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/gate-check/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - CONTRACT.md: SHA-256 efc3ec5e64ffe3fef6c5acb475d6f3d6246e9ac46ba877d45c780b0a28bbe380 - SKILL.md: SHA-256 e2ca66469e396bfd53de98fe3ba9761c24ce76b514cb933e5c5b00f17b36c8de - references/2b-workflow-tier.md: SHA-256 3daee07be4df4801b2d5295dbfee80d04cccb526ca37552fd32a3d3b101fc055 - references/3-run-gate-check.md: SHA-256 c1194a18249ee653ec5b582d66dc2499c48ef93b2d5224fb72b56bbb30e62bca - references/4-assessment.md: SHA-256 f3ebcc4955e4b76c1f20e8d417dcfc9a049dc627f9588d2a08db10c578bcd9d3 - references/5-verdict.md: SHA-256 d373188788563e8683727bd42baee68dcd82a0814174ebd5eaf79a242abc727c - references/6-update-stage.md: SHA-256 6f5039acd8c824e4a2ece527cb2bcf4c00571194cb6060e739ebea076c875b94 - references/7-next-steps.md: SHA-256 a1f9be494110861ce15ce0157e56b568fd42d12f0d0c396f0abd134b522966b1 - references/gate-polish.md: SHA-256 f55ab0697622578b8bf84b41806f9e17cd23247f81975e84031a299f0fc3d1e2 - references/gate-pre-production.md: SHA-256 6acf2cf7a92ed8ce4d2a77f8d75560fce49b98ad5218f2b06606a5ba0545786b - references/gate-production.md: SHA-256 9d77573b61576d4fb233ed9d3ee3f1efab81e26814c1596208fb408b57956e4a - references/gate-release.md: SHA-256 acc2705086afe5cf766b839fbfbe6dfd0b96039af56737e3d0726457b0a0973f - references/gate-systems-design.md: SHA-256 2472d9706f3b938c76eeb747b571d9a695232ada2ca05f4ecce4dffbd868be67 - references/gate-technical-setup.md: SHA-256 26279888b7a13b8b2f2ecbdc0105a1b743ddd39f621e304391d917df1d388bcb If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 14 files: SKILL.md, CONTRACT.md and 12 files under references/ — the 6 per-gate checklists, the tier adjustment, the run procedure, the collaborative assessment, the verdict, the stage update and the next steps. The SKILL.md reads and follows only the references its target gate needs. Nothing in the folder is a program; all 14 are instructions, checklists or contract text the skill reads at use time. Its model is opus, the heaviest in this set. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys review_mode, workflow, qa.level, testing.strict, performance.enforce, team.size, project.stage, system_overrides) and runs template scripts under .claude/scripts/ (artifact-check.sh, gdd-structure-check.sh, adr-dep-graph.sh, and set-stage.sh for the stage write), spawns template director agents in lean and full modes, and runs my project's test suite for its test checks — files, agents and commands that live outside this skill's folder and are absent in a standalone install, so it cannot run outside the full template. - At use time its writes are gated: the gate report goes to production/gate-checks/ only after I approve it, and the stage advance — a dual write of project.stage in project.yaml and production/stage.txt via set-stage.sh — happens only on PASS with my confirmation, or on CONCERNS when I explicitly accept the listed risks; FAIL and NOT ASSESSED can never be overridden into a stage change, and the skill never creates missing artifacts to manufacture a PASS. No third-party service, account or credential is named in the files I read. - Do not run any gate, do not run any template hook, script or agent, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole gate-check folder into the agent's skills directory, in a folder named exactly "gate-check", keeping its 14 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: gate-check), the 14 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone — that it belongs to the full Claude Code Game Studios template and may not run standalone (its checklists live in its references/ files and it runs the template's artifact, structure and stage scripts plus director agents), and that using it writes a gate report and, only on a confirmed PASS or an explicitly risk-accepted CONCERNS, advances the project stage in project.yaml and production/stage.txt). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.