review-all-gdds

Aggregate and analyze GDD documents to surface cross-GDD consistency and design-theory issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-GDD review is essential for ensuring consistency across all GDDs and surfacing design-theory issues early. It helps teams detect contradictions, stale references, and pillar misalignments that single-GDD reviews miss.

Core Features & Use Cases

  • Cross-GDD consistency checks to surface conflicts, missing dependencies, and stale references.
  • Design-theory holism to identify pillar drift, competing progression loops, and cognitive load risks.
  • Structured reporting, risk tagging, and optional revision flags to guide architecture readiness.

Quick Start

Open the project and run the cross-GDD review to generate the unified 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 check cross-GDD consistency for multiple game design documents?

Cross-GDD consistency checks aggregate multiple game design documents to surface conflicts, missing dependencies, and stale references that single-GDD reviews miss. This process detects contradictions and pillar misalignments early in the design pipeline.

What is cross-GDD review and when do I need it in game design pipelines?

Cross-GDD review is the process of analyzing multiple game design documents to ensure holism and identify design-theory issues. You need it for multi-GDD projects to detect pillar drift, competing progression loops, and cognitive load risks.

How do I generate a structured report with risk tagging for GDD revisions?

Generate a structured report by running a cross-GDD review to analyze documents and apply phase-based analysis, risk tagging, and optional revision flags. This guides architecture readiness and outputs a unified report.

Can I use cross-GDD review for large scale game design pipelines?

Cross-GDD review supports multi-GDD projects at scale within game design pipelines. It coordinates phase-based analysis, structured reporting, and gap analysis to manage consistency across all design documents.

What's the best way to identify pillar drift and competing progression loops?

The best way to identify pillar drift and competing progression loops is applying design-theory holism during a cross-GDD review. This surfaces cognitive load risks and misalignments across game design documents.

Can cross-GDD review write revision flags to design documents?

Cross-GDD review supports optional writes to design and GDD cross-review docs. It flags revisions and tags risks directly within the structured reporting output to guide architecture readiness.