review-all-gdds
Skill1 starsChanged 30 days agoMITView on GitHub
Holistic cross-GDD review — contradictions between systems, dominant strategies, economic imbalance, cognitive overload, pillar drift.
9 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiosedited, first seen Nov 9, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- ShiningPlague/shiningplague-studiotheir own version, first seen Oct 11, 2026
- HunLuanZhiZhu/Game-Studios-Plugintheir own version, first seen Oct 5, 2026
- dawn840705/claude-code-studiostheir own version, first seen Aug 28, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Donchitos/Claude-Code-Game-Studios★ 39k98% same
Wrote their own version · 8
- striderZA/OpenCodeGameStudios★ 124same name
- dawn840705/codex-code-studios★ 17same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- hongyuanc/codex-game-studios★ 5same name
- chuanglibs/Claude-Code-Game-Studios-Codex★ 1same name
- dawn840705/claude-code-studios★ 1same name
- HunLuanZhiZhu/Game-Studios-Plugin★ 1same name
- ShiningPlague/shiningplague-studio★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CCGS Skill Testing Framework/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- design/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-auditSkill
- asset-specSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- bug-triageSkill
- changelogSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- estimateSkill
- gate-checkSkill
- helpSkill
- hotfixSkill
- launch-checklistSkill
- localizeSkill
- map-systemsSkill
- milestone-reviewSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- playtest-reportSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- prototypeSkill
- qa-planSkill
- quick-designSkill
- regression-suiteSkill
- release-checklistSkill
- retrospectiveSkill
- reverse-documentSkill
- review-all-gddsSkill
- scope-checkSkill
- security-auditSkill
- settingsSkill
- setup-engineSkill
- skill-improveSkill
- skill-testSkill
- smoke-checkSkill
- soak-testSkill
- sprint-planSkill
- sprint-statusSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 2 are common, 2 are distinctive, and 4 are very specific to this project.
2
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 27
After all MVP-tier GDDs are individually approved
- Common: line 28
After any GDD is significantly revised mid-production
- Very specific: line 29
Before /create-architecture begins (architecture built on inconsistent GDDs inherits those inconsistencies)
- Very specific: line 32
Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and …
- Very specific: line 43
since-last-review: Only GDDs modified since the last review report (git-based) - Very specific: line 80
Do not rely on the subagent to re-read these files — it has its own context window and cannot access Phase 1 results unless they are …
- Distinctive: line 110
First, verify the artifact: If the return contract named a path, check the path exists before treating the phase as done — a named artifact …
- Distinctive: line 118
If any spawned agent returns BLOCKED, errors, or fails to complete: surface it immediately, don't proceed past a dependency it blocks, and …
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,system_overrides
Review All GDDs
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-architecturebegins (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 onlysince-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
sections across all GDDs. At standard, validate the 5 required sections;
optional sections (Player Fantasy, Tuning Knobs, conditional Formulas) are
surfaced as advisory only. At minimal, this skill is not applicable (no GDDs).
Phase 1: Load Everything
Read references/1-load.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Parallel Execution
Phase 2 (Consistency) and Phase 3 (Design Theory) are independent — they read
the same GDD inputs but produce separate reports. Spawn both as parallel Agent
agents simultaneously rather than waiting for Phase 2 to complete before
starting Phase 3. Collect both results before writing the combined report.
Spawn both as game-designer sub-agents (subagent_type: game-designer) — GDD
consistency and design-theory review is its domain.
When spawning the Phase 2 and Phase 3 agents, always pass:
- The loaded GDD content each phase needs — not file paths. Paste the sections; the sub-agent has its own context and cannot re-read Phase 1's results, so a path forces a full re-read (and contradicts the "do not re-read" rule below). Pass only the phase's slice: Phase 2 (consistency) needs each GDD's Dependencies, Detailed Design/Rules, Formulas, Tuning Knobs and Acceptance Criteria; Phase 3 (design theory) needs Player Fantasy, progression/reward structure and the game pillars.
- The full entity registry contents (
design/registry/entities.yaml) if loaded in Phase 1b (paste the registry text, not just a file path) - The specific checklist items assigned to that agent's phase (Phase 2 gets 2a–2f; Phase 3 gets 3a–3g)
- The engine name and version —
engine.nameandengine.versionfromproject.yaml, resolving each field independently (if its key is absent or empty, use.claude/docs/technical-preferences.md) — plusdocs/engine-reference/[engine]/VERSION.md
Do not rely on the subagent to re-read these files — it has its own context window and cannot access Phase 1 results unless they are explicitly passed in the Agent prompt.
Phase 2: Cross-GDD Consistency
Read references/2-consistency.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 3: Game Design Holism
Read references/3-design-holism.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 4: Cross-System Scenario Walkthrough
Read references/4-scenarios.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 5: Output the Review Report
Read references/5-report.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 6: Write Report and Flag GDDs
Read references/6-write.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 7: Handoff
Read references/7-handoff.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Error Recovery Protocol
First, verify the artifact. If the return contract named a path, check the path exists before treating the phase as done — a named artifact that is not on disk is a failed phase, however fluent the response reads. An agent can burn a full phase and return a plausible preamble having written nothing, which is neither BLOCKED nor an error nor "fails to complete", so the trigger below never fires. Resume it naming the unmet contract; the context is usually still there.
If any spawned agent returns BLOCKED, errors, or fails to complete: surface it
immediately, don't proceed past a dependency it blocks, and always produce a
partial report (retry scope here = fewer GDDs / single-system). Full procedure:
.claude/docs/error-recovery-protocol.md.
Collaborative Protocol
In collaborative mode (the default). For guided and autonomous modes,
see .claude/docs/automation-modes.md. In autonomous mode the
PASS/CONCERNS/FAIL verdict is still printed and logged — only the closing
handoff widget is skipped.
- Read silently — load all GDDs before presenting anything
- Show everything — present the full consistency and design theory analysis before asking for any action
- Distinguish blocking from advisory — not every issue needs to block architecture; be clear about which do
- Don't make design decisions — flag contradictions and options, but never unilaterally decide which GDD is "right"
- Ask before writing — confirm before writing the report or updating the systems index
- Be specific — every issue must cite the exact GDD, section, and text involved; no vague warnings
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

