review-all-gdds

Review all system GDDs for cross-document consistency and design holism.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents costly downstream design mistakes by detecting inconsistencies and design-theory problems that only become visible when all system GDDs are read together.

Core Features & Use Cases

  • Cross-GDD consistency audit: flags dependency asymmetry, rule contradictions, stale references, ownership conflicts in tuning knobs, formula range mismatches, and acceptance-criteria conflicts across all GDDs.
  • Game design holism review: checks for progression-loop competition, cognitive load risk, dominant-strategy traps, economic imbalances, difficulty-curve inconsistencies, pillar drift, and player-fantasy coherence issues.
  • Interaction-boundary scenario walkthroughs: runs multi-system player-perspective scenarios to surface broken state transitions, undefined behavior, feedback contradictions, reward/double-dipping issues, and compounding spikes.

Quick Start

Run review-all-gdds with full coverage after your MVP GDDs are approved and before you start architecture, using the optional focus argument when you want faster consistency-only or design-theory-only passes.

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 cross-GDD contradictions before starting architecture?

A cross-GDD consistency audit checks multiple system design documents for dependency asymmetry, rule contradictions, stale references, and formula mismatches before architecture begins. It flags ownership conflicts and acceptance-criteria issues across all interdependent GDDs.

What is game design holism review and when do I need it?

Game design holism review evaluates progression-loop competition, cognitive load risk, dominant-strategy traps, and economic imbalances across all system GDDs. You need it after MVP GDDs are approved and before architecture to prevent costly downstream design mistakes.

How do I audit progression loops and economic balance across multiple game design documents?

Auditing progression loops and economic balance across game design documents involves reading all authoritative GDDs together to detect loop competition, tuning ownership conflicts, and reward double-dipping. The review produces a structured report with severity classification for each imbalance found.

Can I run a consistency-only check on my GDD set without the full design theory review?

Yes, you can run a consistency-only check using the optional focus argument for faster passes. This limits the review to cross-document dependencies, stale references, and formula compatibility, skipping the broader progression and player-fantasy coherence evaluations.

How do I identify dominant strategy risk and pillar drift in my systems design?

Identifying dominant strategy risk and pillar drift requires scanning the authoritative GDD set to evaluate multi-system interaction scenarios. This surfaces compounding spikes, undefined behavior, and feedback contradictions that only become visible when all systems are read together.

Best way to surface broken state transitions in multi-system game design interactions?

Interaction-boundary scenario walkthroughs run multi-system player-perspective scenarios to surface broken state transitions, undefined behavior, and feedback contradictions. This approach detects compounding spikes and reward double-dipping issues hidden within individual GDDs.