review-all-gdds

Review all system GDDs for contradictions and dependency asymmetry.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill review-all-gdds-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-all-gdds
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/review-all-gdds
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill review-all-gdds-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent game design documents from silently combining into conflicting mechanics, progression, and economy rules that later derail architecture and production.

Core Features & Use Cases

  • Cross-GDD consistency review: Finds contradictions across system GDDs, including dependency asymmetry, stale references, ownership conflicts, formula incompatibilities, and acceptance-criteria clashes.
  • Game design holism checks: Surfaces systemic issues that only appear when all systems are considered together, such as competing progression loops, cognitive overload, dominant strategies, economic imbalance, difficulty curve mismatches, pillar drift, anti-pillar violations, and player-fantasy conflicts.
  • Multi-system scenario walkthroughs: Traces key player-facing moments across multiple systems to identify broken state transitions, feedback loops, reward conflicts, and undefined interaction behavior, with severity categorization (BLOCKER/WARNING/INFO) and explicit citations to the step and systems involved.

Quick Start

Run /review-all-gdds after all MVP-tier system GDDs are approved and before /create-architecture to generate a cross-GDD review report and flag any GDDs that must be revised.

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 before architecture starts?

Cross-GDD consistency review scans all system GDDs together to find contradictions, stale references, and rule incompatibilities before architecture begins. It generates a structured report with PASS, CONCERNS, or FAIL verdicts.

What is a GDD consistency check and when do I need to run it?

A GDD consistency check reviews all system design documents together for contradictions and rule incompatibilities. You need it during post-MVP GDD consolidation and as a pre-architecture gate once all system GDDs are approved.

How do I identify progression loop conflicts and economy balance issues across game systems?

Game design holism checks surface competing progression loops, economic imbalance, and dominant strategies by reviewing all systems together. Multi-system scenario walkthroughs trace key player moments to identify broken feedback loops and reward conflicts.

Can I use a GDD review tool if my game design documents include multiple interacting progression loops and tuning knobs?

Yes, this GDD review applies to designs containing multiple interacting systems, pillars, progression loops, economies, and tuning knobs. It uses fast manifest scanning and optional entity-registry preloading to manage complex document interactions.

What is the best way to gate game architecture against conflicting design rules and acceptance criteria?

Running a structured cross-GDD review before creating architecture generates a report with PASS, CONCERNS, or FAIL verdicts. This gates architecture by flagging dependency asymmetry, ownership conflicts, and acceptance-criteria clashes requiring revision.

Why does my game architecture fail when individual system GDDs seem fine on their own?

Individual system GDDs can hide dependency asymmetry and formula incompatibilities that only appear when reviewed together. Cross-GDD scenario walkthroughs trace state transitions across systems to identify broken feedback loops and undefined interaction behavior.