Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula incompatibilities, and game design theory violations (dominant strategies, economic imbalance, cognitive overload, pillar drift). Run after all MVP GDDs are written, before architecture begins.
SkillScore65Maintained
Automatic
◆Product Management pack
Last verified 9/23/2026
What it changes
Passed 11 of 17 test cases with the skill, and 7 of 17 without it.
Without skill39%
With skill65%
Checks it passed that the model alone missed
Worker prompts pass the contents of design/registry/entities.yaml when the file exists.
Each engine parameter key resolves independently if missing from project configuration.
The unassessed status ranks above PASS but below CONCERNS and FAIL in severity ranking.
and 8 more in the full report
7 fixed8 passed either way7 still failing1 broke
Pass-rate lift
+26 pp
Tokens
+366%
Agent turns
0%
Response time
-61%
Model gemini-3.6-flashMeasured 9/23/2026v2 · latest is v415 of 23 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/15/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
After writing the cross-GDD review report to disk, what file must be updated to track session state, and what exact header section should be appended?
What was checked, without and with the skill
Checked
Without skill
With skill
The session state is recorded by appending an entry to production/session-state/active.md.
Missed
Passed
The appended entry begins with the header line ## Session Extract — /review-all-gdds [date].
Missed
Passed
case-18 · gemini-3.6-flash · 9/23/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
This skill reads every system GDD simultaneously and performs two complementary
reviews that cannot be done per-GDD in isolation:
Cross-GDD Consistency — contradictions, stale references, and ownership
conflicts between documents
Game Design Holism — issues that only emerge when you see all systems
together: dominant strategies, broken economies, cognitive overload, pillar
drift, competing progression loops
This is distinct from /design-review, which reviews one GDD for internal
completeness. This skill reviews the relationships between all GDDs.
When to run:
After all MVP-tier GDDs are individually approved
After any GDD is significantly revised mid-production
Before /create-architecture begins (architecture built on inconsistent GDDs
inherits those inconsistencies)
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Argument modes:
Focus:$ARGUMENTS (blank = full)
No argument / full: Both consistency and design theory passes
consistency: Cross-GDD consistency checks only (faster)
design-theory: Game design holism checks only
since-last-review: Only GDDs modified since the last review report (git-based)
workflow per GDD (per .claude/docs/workflow-modes.md): each GDD validates
against its effective tier — the project value, overridden per system by the
system_overrides row for that system when the block lists one. At full, validate all 8
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.