mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 10:17:06 +00:00
DonchitosandClaude Opus 5
d05699707f
`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
26 lines
1.1 KiB
Markdown
26 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.
|
|
|
|
# PR-SCOPE — Scope and Timeline Validation
|
|
|
|
Agent: `producer` | Model tier: Opus | Domain: Scope, timeline, dependencies, production risk
|
|
|
|
**Trigger**: After scope tiers are defined (brainstorm Phase 6, quick-design, or
|
|
any workflow that produces an MVP definition and timeline estimate)
|
|
|
|
**Context to pass**:
|
|
- Full vision scope description
|
|
- MVP definition
|
|
- Timeline estimate
|
|
- Team size (solo / small team / etc.)
|
|
- Scope tiers (what ships if time runs out)
|
|
|
|
**Prompt**:
|
|
> "Review this scope estimate. Is the MVP achievable in the stated timeline for
|
|
> the stated team size? Are the scope tiers correctly ordered by risk — does each
|
|
> tier deliver a shippable product if work stops there? What is the most likely
|
|
> cut point under time pressure, and is it a graceful fallback or a broken product?
|
|
> Return REALISTIC (scope matches capacity), OPTIMISTIC [specific adjustments
|
|
> recommended], or UNREALISTIC [blockers — timeline or MVP must be revised]."
|
|
|
|
**Verdicts**: REALISTIC / OPTIMISTIC / UNREALISTIC
|