Files
Claude-Code-Game-Studios/.claude/skills/gate-check/references/gate-release.md
T
DonchitosandClaude Opus 5 d05699707f Release 1.1.0 — one config file, and a process weight you choose
`project.yaml` at the repo root is now the single source of truth for a
project's configuration, replacing `production/stage.txt`,
`production/review-mode.txt` and `.claude/docs/technical-preferences.md` (all
three still read as a fallback; nothing is force-deleted).

**`modes.rigor` — one question instead of six.** `minimal`, `standard` or
`full` fronts six knobs: `modes.workflow`, `docs.density`, `qa.level`,
`modes.story_granularity`, `modes.review_mode` and `team.size`. It defaults to
`minimal`, which is a change from 1.0's behaviour: the heavier tier was
measured costing several times more to reach working code without producing a
better result, and returning nothing when a fresh developer inherited the
project. Pin `modes.rigor: standard` to keep 1.0's process level.

Also in this release:

- `/settings` to view or change any setting, and `project.local.yaml` for
  per-developer preferences that should not be committed.
- `system_overrides` to hold one system to a higher standard than the rest of
  the project, and `testing.strict` to set per test type whether missing
  evidence blocks a story or warns.
- A story that changes anything the player sees is not closed until the game
  has been launched, observed, and a screenshot retained in
  `production/qa/evidence/`. A parse check is not a run. This holds at every
  rigor level, including `minimal`, where automated tests are waived but the
  look is not.
- The code root is engine-specific and enforced as such: Godot `src/`, Unity
  `Assets/`, Unreal `Source/<Module>/`. Two of the three will not build a
  project laid out any other way.
- Migration tooling for existing projects: `.claude/scripts/migrate-v1-config.sh`
  converts a 1.0 layout, non-destructively by default, with a report to review
  before `--finalize` deletes anything.
- Ask-before-write holds regardless of personal automation settings.

Upgrading from 1.0 or earlier: see UPGRADING.md. Full list of changes:
CHANGELOG.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016xvzG3i7pWQg4LjyDwWMXd
2026-09-23 12:25:11 +10:00

2.2 KiB

Gate definition, loaded by /gate-check for the TARGET PHASE ONLY. Never load the other five — one gate applies per invocation.

Gate: Polish → Release

Required Artifacts:

  • All features from milestone plan are implemented
  • Content is complete (all levels, assets, dialogue referenced in design docs exist)
  • Localization strings are externalized (no hardcoded player-facing text in the code root)
  • QA test plan exists (/qa-plan output in production/qa/)
  • QA sign-off report exists (/team-qa output — APPROVED or APPROVED WITH CONDITIONS)
  • All Must Have story test evidence is present (Logic/Integration: test files pass; Visual/Feel/UI: sign-off docs in production/qa/evidence/)
  • Smoke check passes cleanly (PASS verdict) on the release candidate build
  • No test regressions from previous sprint (test suite passes fully)
  • Balance data has been reviewed (/balance-check run)
  • Release checklist completed (/release-checklist or /launch-checklist run)
  • Store metadata prepared (if applicable)
  • Changelog / patch notes drafted

Quality Checks:

  • Full QA pass signed off by qa-lead
  • All tests passing
  • Performance targets met across all target platforms
  • No known critical, high, or medium-severity bugs
  • Accessibility basics covered (remapping, text scaling if applicable)
  • Localization verified for all target languages
  • Legal requirements met (EULA, privacy policy, age ratings if applicable)
  • Build compiles and packages cleanly

Workflow tier reductions

The checklist above is the full baseline. At lower tiers apply the reduction for the resolved tier; items not named keep their status above. Reductions only ever relax a requirement — workflow_overrides is the only thing that adds one.

  • full — all features + content complete + localization + QA sign-off + smoke (PASS) + no critical bugs all required
  • standard — content-complete audit + QA sign-off + localization → recommended; all features + smoke + no critical bugs required
  • minimal — only smoke + no critical bugs required; everything else drops