`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
Introduces a full shift-left QA pipeline with Story Type classification
as the backbone of the Definition of Done:
New skills:
- /test-setup: scaffold test framework + CI/CD per engine (Godot/Unity/Unreal)
- /qa-plan: generate sprint test plan classifying stories by type
- /smoke-check: critical path gate (PASS/PASS WITH WARNINGS/FAIL) before QA hand-off
- /team-qa: orchestrate qa-lead + qa-tester through full QA cycle
Story Type classification (Logic/Integration/Visual/Feel/UI/Config/Data):
- Logic and Integration: BLOCKING DoD gate — unit/integration test required
- Visual/Feel and UI: ADVISORY — screenshot + sign-off evidence required
- Config/Data: ADVISORY — smoke check pass sufficient
Updated skills: story-done (test evidence gate), story-readiness (Story Type
check), gate-check (test framework at Technical Setup, test evidence at
Polish/Release), create-epics-stories (Type field + Test Evidence section)
Updated agents: qa-lead (shift-left philosophy + evidence table),
qa-tester (automated test patterns for Godot/Unity/Unreal)
New templates: test-evidence.md (manual sign-off record), test-plan.md
(sprint-oriented QA plan replacing generic feature template)
Updated coding-standards.md: Testing Standards section with DoD table,
test rules, what NOT to automate, and engine-specific CI/CD commands
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
