design-review

Review game design documents for missing sections, broken dependencies, and inconsistencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents late-stage engineering rework by reviewing a game design document for completeness, internal consistency, implementability, and alignment with project design standards.

Core Features & Use Cases

  • Structured GDD quality checklist: Validates required sections such as rules clarity, formulas, edge cases, dependencies, tuning knobs, and acceptance criteria.
  • Dependency graph verification: Confirms that referenced system GDD files exist in design/gdd/ to eliminate broken downstream references.
  • Cross-system and implementability scrutiny: Checks formulas, edge-case behavior, missing details, and interaction risks so programmers won’t have to guess.
  • Optional depth control: Supports full, lean, or solo modes to balance thoroughness vs. speed.
  • Adversarial specialist review (full mode): Uses domain specialists for critical, challenge-oriented feedback, then produces a senior synthesized verdict.

Quick Start

Use the command /design-review design/gdd/your-system-gdd.md --depth lean to quickly assess the document in one pass without spawning specialists.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I review a game design document for missing sections and broken dependencies?

To review a game design document, you can validate required sections, check referenced system files in design/gdd/, and surface broken dependencies. This structured GDD quality checklist identifies missing formulas, edge cases, and tuning knobs before programmers start coding.

What is the best way to check implementation readiness before handing a GDD to programmers?

The best way to check implementation readiness is performing a cross-system implementability scrutiny on the GDD. This process verifies formulas, edge-case behavior, and interaction risks so programmers won't have to guess during development.

How do I verify that referenced system GDD files exist in my project?

You can verify referenced system GDD files by performing a dependency graph verification. This checks that referenced system GDD files exist in the design/gdd/ directory via filesystem globbing to eliminate broken downstream references.

Can I run a quick consistency check on a game design document without a full specialist review?

Yes, you can run a quick consistency check using the lean depth mode. This mode assesses the document in one pass without spawning domain specialists, balancing thoroughness and speed for rapid validation.

How does adversarial specialist critique work during a design review?

Adversarial specialist critique works by using domain specialists to provide critical, challenge-oriented feedback during full mode analysis. It then produces a senior synthesized verdict with blocking and recommended revisions for the GDD.