review-all-gdds

Identify cross-GDD inconsistencies, design theory gaps, and multi-system interaction risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-GDD review identifies and resolves contradictions, stale references, and ownership conflicts across multiple game design documents, ensuring a coherent overall design before architecture work begins.

Core Features & Use Cases

  • Phase-driven workflow across Phase 1 to Phase 7, enabling detection of cross-document dependencies, design-theory holism, and multi-system interaction issues.
  • Parallel analysis: runs consistency and design-theory checks in tandem to surface both structural and holistic risks.
  • Generates an actionable report and supports governance with a session-state update and handoff prompts.

Quick Start

Run the cross-GDD review to surface inconsistencies and provide an actionable report.

Frequently Asked Questions about review-all-gdds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify cross-GDD inconsistencies in multiple game design documents?

Cross-GDD inconsistencies are identified by analyzing dependency symmetry, rule contradictions, stale references, and ownership conflicts across all loaded GDDs to produce a structured review report.

What is design-theory holism and how does it impact game design review?

Design-theory holism measures the multi-system interaction risks and theoretical gaps across game design documents, ensuring a coherent overall design before architecture work begins.

How do I run a cross-GDD review to surface design contradictions and stale references?

Run the cross-GDD review by loading your GDD set to execute parallel consistency and design-theory checks, which surface structural and holistic risks across a phase-driven workflow.

When do I need a cross-GDD review for my game design documents?

You need a cross-GDD review when you must resolve contradictions, stale references, and ownership conflicts across multiple game design documents to ensure cohesive design before architecture work.

Can I use this cross-GDD review to detect multi-system interaction risks?

Yes, the cross-GDD review runs parallel analysis to detect multi-system interaction risks, design theory gaps, and dependency symmetry issues across all loaded game design documents.

What are the limitations of using a cross-GDD review for game design consistency?

The cross-GDD review relies on the loaded GDD set to surface actionable issues, meaning it cannot identify inconsistencies or stale references in game design documents that are not loaded into the session.