mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 10:17:06 +00:00
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
This commit is contained in:
Donchitos
co-authored by
Claude Opus 5
Claude Opus 5
parent
984023ddac
commit
d05699707f
@@ -0,0 +1,48 @@
|
||||
> Gate definition, loaded by `/gate-check` for the TARGET PHASE ONLY.
|
||||
> Never load the other five — one gate applies per invocation.
|
||||
|
||||
|
||||
# Gate: Production → Polish
|
||||
|
||||
|
||||
**Required Artifacts:**
|
||||
- [ ] The code root has active code organized into subsystems
|
||||
- [ ] All core mechanics from GDD are implemented (cross-reference `design/gdd/` with the code root)
|
||||
- [ ] Main gameplay path is playable end-to-end
|
||||
- [ ] Test files exist in `tests/unit/` and `tests/integration/` covering Logic and Integration stories
|
||||
- [ ] All Logic stories from this sprint have corresponding unit test files in `tests/unit/`
|
||||
- [ ] Smoke check has been run with a PASS or PASS WITH WARNINGS verdict — report exists in `production/qa/`
|
||||
- [ ] At least one QA plan exists in `production/qa/` (generated by `/qa-plan`) covering this sprint, the final production sprint, or this production phase — run `/qa-plan` if missing (CONCERNS — advisory, not blocking)
|
||||
- [ ] QA sign-off report exists in `production/qa/` (generated by `/team-qa`) with verdict APPROVED or APPROVED WITH CONDITIONS
|
||||
- [ ] At least 3 distinct playtest sessions documented in `production/qa/playtests/`
|
||||
- [ ] Playtest reports cover: new player experience, mid-game systems, and difficulty curve
|
||||
- [ ] Fun hypothesis from Game Concept has been explicitly validated or revised
|
||||
|
||||
**Quality Checks:**
|
||||
- [ ] Tests are passing (run test suite via Bash)
|
||||
- [ ] No critical/blocker bugs in any bug tracker or known issues
|
||||
- [ ] Core loop plays as designed (compare to GDD acceptance criteria)
|
||||
- [ ] Performance is within budget (check `performance.*` in `project.yaml`, else technical-preferences.md targets)
|
||||
- [ ] Playtest findings have been reviewed and critical fun issues addressed (not just documented)
|
||||
- [ ] No "confusion loops" identified — no point in the game where >50% of playtesters got stuck without knowing why
|
||||
- [ ] Difficulty curve matches the Difficulty Curve design doc (if one exists at `design/difficulty-curve.md`)
|
||||
- [ ] All implemented screens have corresponding UX specs (no "designed in-code" screens)
|
||||
- [ ] Interaction pattern library is up-to-date with all patterns used in implementation
|
||||
- [ ] Accessibility compliance verified against committed tier in `design/accessibility-requirements.md`
|
||||
|
||||
## 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`** — core mechanics + Logic/Integration tests + smoke check (PASS) + QA sign-off + 3+ playtests all required
|
||||
- **`standard`** — QA sign-off + per-story test coverage → recommended;
|
||||
**core mechanics + smoke check + playable end-to-end + 1+ documented
|
||||
playtest + no critical/blocker bugs** required
|
||||
- **`minimal`** — **smoke check + playable end-to-end + no critical/blocker
|
||||
bugs** required; the core-mechanics cross-check → recommended; everything
|
||||
else **drops**. Reductions relax what must *exist*, never what must *work* —
|
||||
a gate that closes production on "it boots" alone has not asked whether the
|
||||
game plays.
|
||||
@@ -0,0 +1,67 @@
|
||||
> Gate definition, loaded by `/gate-check` for the TARGET PHASE ONLY.
|
||||
> Never load the other five — one gate applies per invocation.
|
||||
|
||||
|
||||
# Gate: Technical Setup → Pre-Production
|
||||
|
||||
|
||||
**Required Artifacts:**
|
||||
- [ ] Engine chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)
|
||||
- [ ] Project config populated (`project.yaml` has engine/naming/performance set, or legacy `.claude/docs/technical-preferences.md` populated)
|
||||
- [ ] Art bible exists at `design/art/art-bible.md` with at least Sections 1–4 (Visual Identity Foundation)
|
||||
- [ ] At least 3 Architecture Decision Records in `docs/architecture/` covering
|
||||
Foundation-layer systems (scene management, event architecture, save/load)
|
||||
- [ ] Engine reference docs exist in `docs/engine-reference/[engine]/`
|
||||
- [ ] Test framework initialized: `tests/unit/` and `tests/integration/` directories exist
|
||||
- [ ] CI/CD test workflow exists at `.github/workflows/tests.yml` (or equivalent)
|
||||
- [ ] At least one example test file exists to confirm the framework is functional
|
||||
- [ ] Master architecture document exists at `docs/architecture/architecture.md`
|
||||
- [ ] Architecture traceability index exists at `docs/architecture/requirements-traceability.md`
|
||||
- [ ] `/architecture-review` has been run (a review report file exists in `docs/architecture/`)
|
||||
- [ ] `design/accessibility-requirements.md` exists with accessibility tier committed
|
||||
- [ ] `design/ux/interaction-patterns.md` exists (pattern library initialized, even if minimal)
|
||||
|
||||
**Quality Checks:**
|
||||
- [ ] Architecture decisions cover core systems (rendering, input, state management)
|
||||
- [ ] Technical preferences have naming conventions and performance budgets set
|
||||
- [ ] Accessibility tier is defined and documented (even "Basic" is acceptable — undefined is not)
|
||||
- [ ] At least one screen's UX spec started (often the main menu or core HUD is designed during Technical Setup)
|
||||
- [ ] All ADRs have an **Engine Compatibility section** with engine version stamped
|
||||
- [ ] All ADRs have a **GDD Requirements Addressed section** with explicit GDD linkage
|
||||
- [ ] No ADR references APIs listed in `docs/engine-reference/[engine]/deprecated-apis.md`
|
||||
- [ ] All HIGH RISK engine domains (per VERSION.md) have been explicitly addressed
|
||||
in the architecture document or flagged as open questions
|
||||
- [ ] Architecture traceability matrix has **zero Foundation layer gaps**
|
||||
(all Foundation requirements must have ADR coverage before Pre-Production)
|
||||
|
||||
**ADR Circular Dependency Check**: run the deterministic graph builder rather than
|
||||
reading every ADR to trace the graph by hand — a manual trace across a dozen ADRs
|
||||
eventually misses an edge; the script cannot:
|
||||
```
|
||||
Bash: bash .claude/scripts/adr-dep-graph.sh
|
||||
```
|
||||
It prints `ADRS`, `EDGES` (one `adr-A -> adr-B` per Depends-On reference),
|
||||
`NO_DEPS_SECTION` (ADRs with no Depends On), and a `CYCLE:` line per node in any
|
||||
dependency cycle.
|
||||
- **Any `CYCLE:` lines → FAIL**: "Circular ADR dependency: [the nodes on the
|
||||
`CYCLE:` lines]. Neither can reach Accepted while the cycle exists. Remove one
|
||||
'Depends On' edge to break the cycle."
|
||||
- No `CYCLE:` lines → this check passes. But the acyclic result is only as
|
||||
trustworthy as the dependency sections are complete: if `NO_DEPS_SECTION` lists
|
||||
many ADRs, surface that as a CONCERNS note rather than a clean pass.
|
||||
|
||||
**Engine Validation** (read `docs/engine-reference/[engine]/VERSION.md` first):
|
||||
- [ ] ADRs that touch post-cutoff engine APIs are flagged with Knowledge Risk: HIGH/MEDIUM
|
||||
- [ ] `/architecture-review` engine audit shows no deprecated API usage
|
||||
- [ ] All ADRs agree on the same engine version (no stale version references)
|
||||
|
||||
## 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`** — engine + art bible §1–4+ + 3+ ADRs + architecture + UX specs started + accessibility doc + traceability index all required
|
||||
- **`standard`** — art bible required **only if visual-asset stories exist**; ADRs reduced to **critical (Foundation-layer) only**; UX-specs-started, accessibility doc, interaction-patterns, traceability index → recommended
|
||||
- **`minimal`** — only **engine configured** required (the minimal floor); everything else **drops**
|
||||
@@ -0,0 +1,78 @@
|
||||
> Gate definition, loaded by `/gate-check` for the TARGET PHASE ONLY.
|
||||
> Never load the other five — one gate applies per invocation.
|
||||
|
||||
|
||||
# Gate: Pre-Production → Production
|
||||
|
||||
|
||||
**Required Artifacts:**
|
||||
- [ ] Vertical slice exists in `prototypes/` with a REPORT.md (run `/vertical-slice`) — **recommended, not blocking**; if absent, surface as CONCERNS
|
||||
- [ ] First sprint plan exists in `production/sprints/`
|
||||
- [ ] Art bible is complete (all 9 sections) and AD-ART-BIBLE sign-off verdict is recorded in `design/art/art-bible.md`
|
||||
- [ ] Entity inventory exists at `design/assets/entity-inventory.md` (recommended — run `/asset-spec` with no arguments to generate collaboratively from GDDs + art bible)
|
||||
- [ ] All MVP-tier GDDs from systems index are complete
|
||||
- [ ] Master architecture document exists at `docs/architecture/architecture.md`
|
||||
- [ ] At least 3 ADRs covering Foundation-layer decisions exist in `docs/architecture/`
|
||||
- [ ] All Foundation and Core layer ADRs have status `Accepted` (not `Proposed`) — stories cannot be unblocked until their governing ADR is accepted
|
||||
- [ ] Control manifest exists at `docs/architecture/control-manifest.md`
|
||||
(generated by `/create-control-manifest` from Accepted ADRs)
|
||||
- [ ] Epics defined in `production/epics/` with at least Foundation and Core
|
||||
layer epics present (use `/create-epics layer: foundation` and
|
||||
`/create-epics layer: core` to create them, then `/create-stories [epic-slug]`
|
||||
for each epic)
|
||||
- [ ] Vertical Slice build exists and is playable (not just scope-defined) — **recommended, not blocking**; if absent, surface as CONCERNS
|
||||
- [ ] Vertical Slice has been playtested with at least 1 documented session — **recommended, not blocking**; if absent, surface as CONCERNS
|
||||
- [ ] Vertical Slice playtest report exists at `production/qa/playtests/` or equivalent — **recommended, not blocking**; if absent, surface as CONCERNS
|
||||
- [ ] UX specs exist for key screens: main menu, core gameplay HUD (at `design/ux/`), pause menu
|
||||
- [ ] HUD design document exists at `design/ux/hud.md` (if game has in-game HUD)
|
||||
- [ ] All key screen UX specs have passed `/ux-review` (verdict APPROVED or NEEDS REVISION accepted)
|
||||
|
||||
**Quality Checks:**
|
||||
- [ ] **Core loop fun is validated** — playtest data confirms the central mechanic is enjoyable, not just functional. Explicitly check the Vertical Slice playtest report.
|
||||
- [ ] UX specs cover all UI Requirements sections from MVP-tier GDDs
|
||||
- [ ] Interaction pattern library documents patterns used in key screens
|
||||
- [ ] Accessibility tier from `design/accessibility-requirements.md` is addressed in all key screen UX specs
|
||||
- [ ] Sprint plan references real story file paths from `production/epics/`
|
||||
(not just GDDs — stories must embed GDD req ID + ADR reference)
|
||||
- [ ] **Vertical Slice is COMPLETE**, not just scoped — the build demonstrates the full core loop end-to-end. At least one complete [start → challenge → resolution] cycle works.
|
||||
- [ ] Architecture document has no unresolved open questions in Foundation or Core layers
|
||||
- [ ] All ADRs have Engine Compatibility sections stamped with the engine version
|
||||
- [ ] All ADRs have ADR Dependencies sections (even if all fields are "None")
|
||||
- [ ] Manual validation confirms GDDs + architecture + epics are coherent
|
||||
(run `/review-all-gdds` and `/architecture-review` if not done recently)
|
||||
- [ ] **Core fantasy is delivered** — at least one playtester independently described an experience that matches the Player Fantasy section of the core system GDDs (without being prompted).
|
||||
|
||||
**Vertical Slice Validation** (only run these checks if a Vertical Slice was built):
|
||||
- [ ] A human has played through the core loop without developer guidance
|
||||
- [ ] The game communicates what to do within the first 2 minutes of play
|
||||
- [ ] No critical "fun blocker" bugs exist in the Vertical Slice build
|
||||
- [ ] The core mechanic feels good to interact with (this is a subjective check — ask the user)
|
||||
|
||||
> **Verdict rules for Vertical Slice:**
|
||||
> - **Slice was built AND any validation item is NO** → verdict is automatically FAIL. A broken
|
||||
> or unfun vertical slice should not advance to Production.
|
||||
> - **Slice was not built (skipped)** → downgrade to CONCERNS only, not FAIL. Surface the risk
|
||||
> clearly: "Advancing without a validated Vertical Slice increases the risk of late-stage design
|
||||
> pivots. Recommended before committing full production scope." The user decides.
|
||||
> - Skipping is a valid solo dev or time-constrained call. Shipping a broken one is not.
|
||||
|
||||
## 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`** — sprint plan + complete (9-section) art bible + epics + 3+ playtests + UX specs + control manifest all required; **Vertical Slice keeps its Section 2 status** (see note)
|
||||
- **`standard`** — **1+ playtest** required (not 3); epics + sprint plan required; art bible complete + UX specs + control manifest → recommended
|
||||
- **`minimal`** — only **sprint plan** required (the minimal floor); epics, playtests, art bible, UX, control manifest all **drop**
|
||||
|
||||
> **The Vertical Slice keeps its Section 2 status at every tier.** The
|
||||
> Pre-Production → Production "prototype/Vertical Slice" floor is NOT upgraded to
|
||||
> blocking by the tier table — the Vertical Slice artifacts stay *recommended,
|
||||
> not blocking* (absent → CONCERNS, not FAIL) exactly as Section 2 defines, at
|
||||
> `full`, `standard`, and `minimal` alike. The genuinely-required floor item at
|
||||
> this gate is the **sprint plan**. The one hard rule that binds at every tier:
|
||||
> if a Vertical Slice *was built* and any of its validation items is NO, the
|
||||
> verdict is FAIL regardless of tier — tier reductions relax what must *exist*,
|
||||
> never what must *work*.
|
||||
@@ -0,0 +1,41 @@
|
||||
> 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**
|
||||
@@ -0,0 +1,33 @@
|
||||
> Gate definition, loaded by `/gate-check` for the TARGET PHASE ONLY.
|
||||
> Never load the other five — one gate applies per invocation.
|
||||
|
||||
|
||||
# Gate: Concept → Systems Design
|
||||
|
||||
|
||||
**Required Artifacts:**
|
||||
- [ ] `design/gdd/game-concept.md` exists and has content
|
||||
- [ ] Game pillars defined (in concept doc or `design/gdd/game-pillars.md`)
|
||||
- [ ] Visual Identity Anchor section exists in `design/gdd/game-concept.md` (from brainstorm Phase 4 art-director output)
|
||||
|
||||
**Recommended (not blocking):**
|
||||
- [ ] Concept prototype exists in `prototypes/` with a REPORT.md showing PROCEED verdict
|
||||
(`/prototype [core-mechanic]`) — skipping this means GDDs may be written for an
|
||||
idea that hasn't been played. Acceptable if the concept is proven by other means.
|
||||
|
||||
**Quality Checks:**
|
||||
- [ ] Game concept has been reviewed (`/design-review` verdict not MAJOR REVISION NEEDED)
|
||||
- [ ] Core loop is described and understood
|
||||
- [ ] Target audience is identified
|
||||
- [ ] Visual Identity Anchor contains a one-line visual rule and at least 2 supporting visual principles
|
||||
|
||||
## 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`** — game-concept.md + pillars + Visual Identity Anchor all required
|
||||
- **`standard`** — pillars + Visual Identity Anchor → recommended; `game-concept.md` stays required
|
||||
- **`minimal`** — gate target is **`design/game-brief.md`** (not `game-concept.md`); the GDD / pillars / Visual Identity Anchor checks **drop** (a brief with content = PASS). `/brainstorm` writes `design/game-brief.md` at this tier (Option A); `game-concept.md` remains the `standard`/`full` concept doc.
|
||||
@@ -0,0 +1,36 @@
|
||||
> Gate definition, loaded by `/gate-check` for the TARGET PHASE ONLY.
|
||||
> Never load the other five — one gate applies per invocation.
|
||||
|
||||
|
||||
# Gate: Systems Design → Technical Setup
|
||||
|
||||
|
||||
**Required Artifacts:**
|
||||
- [ ] Systems index exists at `design/gdd/systems-index.md` with at least MVP systems enumerated
|
||||
- [ ] All MVP-tier GDDs exist in `design/gdd/` and individually pass `/design-review`
|
||||
- [ ] A cross-GDD review report exists in `design/gdd/` (from `/review-all-gdds`)
|
||||
|
||||
**Quality Checks:**
|
||||
- [ ] All MVP GDDs pass individual design review (8 required sections, no MAJOR REVISION NEEDED verdict)
|
||||
- [ ] `/review-all-gdds` verdict is not FAIL (cross-GDD consistency and design theory checks pass)
|
||||
- [ ] All cross-GDD consistency issues flagged by `/review-all-gdds` are resolved or explicitly accepted
|
||||
- [ ] System dependencies are mapped in the systems index and are bidirectionally consistent
|
||||
- [ ] MVP priority tier is defined
|
||||
- [ ] No stale GDD references flagged (older GDDs updated to reflect decisions made in later GDDs)
|
||||
|
||||
## 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`** — systems-index + all MVP GDDs at 8 sections + cross-GDD review report all required
|
||||
- **`standard`** — MVP GDDs validated at the **5 standard sections** (+ conditional Formulas); cross-GDD review report → recommended
|
||||
- **`minimal`** — **gate not applicable** — no gate between brief and code; auto-PASS with a note (see below)
|
||||
|
||||
> **`minimal` "not applicable" gate.** The Systems Design → Technical Setup gate
|
||||
> has no meaning at `minimal` (no GDDs exist by design). Return a PASS verdict
|
||||
> with the note: *"No design gate at minimal workflow — minimal skips the
|
||||
> Systems Design phase; advancing brief → code."* The Section 6 stage write still
|
||||
> applies on user confirmation. Do NOT flag absent GDDs as blockers.
|
||||
Reference in New Issue
Block a user