mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
`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
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
> Gate definition. The spawning skill passes this file's path to the director agent; the AGENT reads it — the parent session should not.
|
|
|
|
# TD-ARCHITECTURE — Architecture Sign-Off
|
|
|
|
Agent: `technical-director` | Model tier: Opus | Domain: Architecture, engine risk, performance
|
|
|
|
**Trigger**: After the master architecture document is drafted (`/create-architecture`
|
|
Phase 7), and after any major architecture revision
|
|
|
|
**Context to pass**:
|
|
- Architecture document path (`docs/architecture/architecture.md`)
|
|
- Technical requirements baseline (TR-IDs and count)
|
|
- ADR list with statuses
|
|
- Engine knowledge gap inventory
|
|
|
|
**Prompt**:
|
|
> "Review this master architecture document for technical soundness. Check: (1) Is
|
|
> every technical requirement from the baseline covered by an architectural decision?
|
|
> (2) Are all HIGH risk engine domains explicitly addressed or flagged as open
|
|
> questions? (3) Are the API boundaries clean, minimal, and implementable? (4) Are
|
|
> Foundation layer ADR gaps resolved before implementation begins? Return APPROVE,
|
|
> CONCERNS [list], or REJECT [blockers that must be resolved before coding starts]."
|
|
|
|
**Verdicts**: APPROVE / CONCERNS / REJECT
|