review-all-gdds

Review all system GDDs to detect cross-document contradictions and holistic design failures.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill review-all-gdds-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-all-gdds
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/review-all-gdds
Command: npx skills add https://github.com/easonlao/jiazi-game --skill review-all-gdds-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent game design documentation from silently causing contradictory mechanics, broken dependencies, and imbalanced player experience during later production.

Core Features & Use Cases

  • Cross-GDD consistency validation: Finds contradictions across system GDDs, including dependency asymmetry, stale references, ownership conflicts, formula incompatibilities, and acceptance-criteria conflicts.
  • Game design holism review: Flags holistic issues that only appear when all systems are viewed together, such as competing progression loops, cognitive overload, dominant strategies, economic imbalances, difficulty-curve mismatches, pillar drift, and player-fantasy conflicts.
  • Multi-system scenario walkthrough: Steps through 3–5 key player moments where multiple systems interact to identify ordering/data-flow failures, race conditions, reward conflicts, undefined combined states, and compounding difficulty spikes.

Quick Start

Run the review-all-gdds skill after your MVP-tier system GDDs are approved and before starting architecture, using full focus or limiting scope to consistency or design theory.

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 for contradictions across multiple game design documents before starting architecture?

Cross-GDD consistency validation reviews all system GDD documents together to detect dependency asymmetry, stale references, formula incompatibilities, and ownership conflicts before architecture begins. It outputs a written report and optional systems-index status updates.

When do I need a holistic game design review for my project?

A holistic game design review is needed after MVP-tier system GDDs are drafted and optionally after mid-production revisions. It flags competing progression loops, economic imbalances, difficulty-curve mismatches, and player-fantasy conflicts that only appear when all systems are viewed together.

Can I limit the scope of a GDD review to just consistency checks or design theory?

Yes, you can run the review using full focus or limit the scope to specifically perform consistency checks or design-theory analysis. This flexibility applies to workflows after MVP-tier GDDs are approved and before architecture begins.

How do I identify undefined combined states and reward conflicts in my game mechanics?

Multi-system scenario walkthroughs step through key player moments where multiple systems interact to identify undefined combined states, reward conflicts, race conditions, ordering failures, and compounding difficulty spikes across your game design.

Does the GDD review process support git-based scope selection for mid-production revisions?

Yes, the GDD review process supports git-based scope selection, allowing you to apply cross-document contradiction detection and holistic design failure analysis specifically during mid-production revisions of your system documents.