review-all-gdds

Analyze multiple system GDDs for rule contradictions and design inconsistencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented game design where individual documents contradict each other, leading to broken mechanics, unbalanced economies, and scope creep that only becomes visible when viewing the entire project holistically.

Core Features & Use Cases

  • Cross-GDD Consistency: Automatically detects rule contradictions, stale references, and ownership conflicts between multiple system documents.
  • Game Design Holism: Analyzes progression loops, player attention budgets, and economic balance to ensure the game remains cohesive and fun.
  • Scenario Walkthrough: Simulates player actions across multiple systems to identify race conditions, compounding difficulty spikes, and undefined behaviors.

Quick Start

Run the review-all-gdds skill to perform a full consistency and design theory check on all system 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 game design consistency across multiple GDDs?

Game design consistency is checked by analyzing relationships between multiple system GDDs to automatically detect rule contradictions, stale references, and ownership conflicts before implementation begins.

What is cross-document game design review and when do I need it?

Cross-document game design review identifies fragmented design, economic imbalances, and competing progression loops by validating system dependencies holistically across all project documents.

How do I identify economic imbalances and progression loop conflicts in indie game design?

Economic imbalances and progression loop conflicts are identified by analyzing player attention budgets and simulating multi-system scenario walkthroughs to detect compounding difficulty spikes and race conditions.

Can I simulate player actions across game systems to find undefined behaviors?

Simulating player actions across game systems validates architectural integrity by performing multi-system scenario walkthroughs that expose race conditions, undefined behaviors, and competing progression loops.

What is the best way to validate system dependencies before game implementation?

Validating system dependencies before implementation is best achieved by performing a holistic cross-document consistency review that detects rule contradictions and scope creep across all system GDDs.

Why does my game design feel fragmented despite having individual system documents?

Game design feels fragmented when individual documents contradict each other, creating broken mechanics and unbalanced economies that only become visible when viewing the entire project holistically.