review-all-gdds

Detect contradictions across dragon-forge system GDDs and report risks.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill review-all-gdds-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-all-gdds
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/review-all-gdds
Command: npx skills add https://github.com/scomofo/dragon-forge --skill review-all-gdds-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents design fragmentation by finding contradictions and inconsistencies across all system GDDs, so you do not build architecture on conflicting assumptions.

Core Features & Use Cases

  • Cross-GDD Consistency checks: Detect dependency asymmetry, rule contradictions, stale references, ownership conflicts for tuning knobs, formula compatibility issues, and acceptance-criteria conflicts.
  • Game design holism review: Identify competing progression loops, cognitive load risk, dominant strategy risks, economic imbalances, difficulty curve mismatches, pillar drift/anti-pillar violations, and player fantasy incoherence.
  • Cross-system scenario walkthrough: Walk key multi-system moments to surface interaction-boundary failures like race conditions, feedback loops, broken state transitions, contradictory messaging, compounding difficulty spikes, reward conflicts, and undefined combined states.
  • Report writing and revision flagging: Produces a dated cross-GDD review report and can update the systems index to mark affected GDDs as needing revision.

Quick Start

Run review-all-gdds in full focus to load all system GDDs and generate a cross-GDD consistency plus design-theory report before architecture begins.

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-document consistency issues across multiple game design documents?

Cross-document consistency checks validate dependency asymmetry, rule contradictions, stale references, and formula compatibility issues across all system GDDs before architecture begins. This prevents building architecture on conflicting design assumptions.

What is a GDD review and when do I need to run it?

A GDD review identifies design fragmentation risks like competing progression loops and economic imbalances. You need it after MVP GDD approval and before architecture work to ensure all system design documents align.

How do I detect difficulty curve mismatches and player experience risks in my game design?

Game design holism review identifies difficulty curve mismatches, cognitive load risks, dominant strategy risks, and pillar drift across your system GDDs. It surfaces player fantasy incoherence before development proceeds.

Can I perform a git-scoped analysis to only review recently changed game design documents?

Yes, the cross-GDD review supports optional git-scoped analysis since the last review. This validates dependencies and rules only in recently modified design/gdd/*.md files to save time.

How do I run a cross-system scenario walkthrough to find interaction-boundary failures?

Cross-system scenario walkthroughs walk key multi-system moments to surface race conditions, feedback loops, broken state transitions, and compounding difficulty spikes. They identify undefined combined states and reward conflicts across systems.

What are the limitations of relying on manual reviews for game economy balancing?

Manual reviews risk missing ownership conflicts for tuning knobs and acceptance-criteria conflicts across documents. Automated cross-GDD validation produces a dated report and updates the systems index to flag affected GDDs for revision.