mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +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
31 lines
1.6 KiB
Markdown
31 lines
1.6 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-EPIC — Epic Structure Feasibility Review
|
|
|
|
Agent: `producer` | Model tier: Opus | Domain: Scope, timeline, dependencies, production risk
|
|
|
|
**Trigger**: After epics are defined by `/create-epics`, before stories are
|
|
broken out — validates the epic structure is producible before `/create-stories`
|
|
is invoked
|
|
|
|
**Context to pass**:
|
|
- Epic definition file paths (all epics just created)
|
|
- Epic index path (`production/epics/index.md`)
|
|
- Milestone timeline and target dates
|
|
- Team capacity (solo / small team / size)
|
|
- Layer being epiced (Foundation / Core / Feature / etc.)
|
|
|
|
**Prompt**:
|
|
> "Review this epic structure for production feasibility before story breakdown
|
|
> begins. Are the epic boundaries scoped appropriately — could each epic realistically
|
|
> complete before a milestone deadline? Are epics correctly ordered by system
|
|
> dependency — does any epic require another epic's output before it can start?
|
|
> Are any epics underscoped (too small, should merge) or overscoped (too large,
|
|
> should split into 2-3 focused epics)? Are the Foundation-layer epics scoped to
|
|
> allow Core-layer epics to begin at the start of the next sprint after Foundation
|
|
> completes? Return REALISTIC (epic structure is producible), CONCERNS [specific
|
|
> structural adjustments before stories are written], or UNREALISTIC [epics must
|
|
> be split, merged, or reordered — story breakdown cannot begin until resolved]."
|
|
|
|
**Verdicts**: REALISTIC / CONCERNS / UNREALISTIC
|