review-all-gdds

Review all MVP GDDs for contradictions, outdated references, and design violations.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill review-all-gdds-brand6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-all-gdds
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/review-all-gdds
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill review-all-gdds-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs a cross-GDD consistency and design review across all MVP GDDs, scanning for contradictions, outdated references, ownership conflicts, formula incompatibilities, and design-theory violations (dominant strategies, economic balance, cognitive load, pillar drift). It runs after MVPs are drafted and before architecture begins to ensure alignment.

Core Features & Use Cases

  • Cross-GDD aggregation and validation to surface dependencies, references, and ownership inconsistencies.
  • Detection of conflicts across GDDs, stale references, and incompatible formulas to guide architectural decisions.
  • Output: a structured cross-GDD review report that informs design decisions and architecture planning.

Quick Start

Run the /review-all-gdds command to perform a cross-GDD check across all MVP documents.

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?

Cross-GDD consistency review scans all MVP game design documents to detect contradictions, outdated references, and ownership conflicts. It validates alignment with core pillars and aggregates findings into a structured report before architecture planning begins.

What is cross-GDD consistency review for MVP game design?

Cross-GDD consistency review is a validation process that checks MVP game design documents for formula incompatibilities and design-theory violations like dominant strategies. It surfaces dependencies and ownership inconsistencies to guide architectural decisions.

When should I run a cross-GDD design review in my development workflow?

Run a cross-GDD design review after drafting MVP game design documents and before architecture planning begins. This timing ensures all design documents align with core pillars and resolves formula incompatibilities prior to implementation.

How do I detect design-theory violations like dominant strategies across game design documents?

Cross-GDD review detects design-theory violations by scanning game design documents for dominant strategies, economic balance issues, cognitive load problems, and pillar drift. It aggregates these findings into a structured report with actionable recommendations.

Can I identify ownership conflicts and stale references across multiple game design documents?

Yes, cross-GDD aggregation and validation surfaces ownership conflicts, stale references, and cross-document dependencies. It scans all MVP game design documents to identify these inconsistencies and outputs a structured review report.

What is the best way to ensure formula compatibility across separate game design documents?

Cross-GDD consistency review identifies incompatible formulas across all MVP game design documents. It detects these mathematical conflicts during the post-drafting phase and provides actionable recommendations to resolve them before architecture planning.