review-all-gdds

Reviews all game design documents for cross-document contradictions and design theory violations.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill review-all-gdds-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-all-gdds
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/review-all-gdds
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill review-all-gdds-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Individually approved game design documents can still contradict each other, reference stale mechanics, or combine into broken economies and dominant strategies that only become visible when all systems are reviewed together. ## Core Features & Use Cases - Cross-GDD Consistency Checks: Detects dependency asymmetries, rule contradictions, stale references, tuning knob ownership conflicts, formula range mismatches, and incompatible acceptance criteria across all GDDs. - Game Design Holism Analysis: Flags competing progression loops, cognitive overload, dominant strategies, economic source/sink imbalances, difficulty curve mismatches, pillar drift, and conflicting player fantasies. - Cross-System Scenario Walkthroughs: Steps through multi-system player moments to find race conditions, feedback loops, and undefined behavior, then produces a PASS/CONCERNS/FAIL verdict report. - Use Case: After writing all MVP-tier GDDs for a game, run this review before starting architecture so the technical design is not built on contradictory system definitions. ## Quick Start Ask the AI to run a full cross-GDD review of all documents in design/gdd and report any blocking contradictions before architecture begins.

Frequently Asked Questions about review-all-gdds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check multiple game design documents for contradictions?

Run a cross-GDD review that loads every system GDD and compares dependency sections, rules, tuning knobs, formulas, and acceptance criteria pairwise. This skill automates that process and reports blocking contradictions versus advisory warnings.

When should I run a cross-GDD review in game development?

Run it after all MVP-tier GDDs are individually approved, after any GDD is significantly revised mid-production, and before architecture work begins. Architecture built on inconsistent GDDs inherits those inconsistencies.

What is the difference between a single GDD review and a cross-GDD review?

A single GDD review checks one document for internal completeness. A cross-GDD review examines relationships between all documents, catching contradictions, stale references, and design issues like dominant strategies that only emerge when systems are viewed together.

Can I review only the GDDs that changed since the last review?

Yes, the since-last-review mode uses git log to identify GDDs modified since the previous review report, then scopes the full read to those documents plus their listed key dependencies.

What happens if fewer than two system GDDs exist?

The review stops and reports that cross-GDD review requires at least two system GDDs. You must write additional GDDs first, then re-run the review.

Does the review modify my GDD files automatically?

No. It asks for explicit approval before writing the review report or updating the systems index, and it never decides which GDD is correct when a contradiction is found.