design-review

Reviews game design documents for completeness, consistency, and implementability before programmer handoff.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill design-review-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/design-review
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill design-review-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game design documents often reach programmers with missing sections, broken dependency references, untestable acceptance criteria, or formulas that break at boundary values. This Skill catches those problems before implementation begins by running a structured multi-phase review of any GDD. ## Core Features & Use Cases - Structured Completeness Audit: Checks the document against an 8-section design standard covering overview, player fantasy, rules, formulas, edge cases, dependencies, tuning knobs, and acceptance criteria. - Adversarial Specialist Review: In full mode, spawns parallel domain subagents (game-designer, systems-designer, qa-lead, creative-director, and others) that challenge the design rather than validate it, then synthesizes a senior verdict. - Dependency and Re-review Tracking: Verifies that every referenced system GDD exists on disk, reads prior review logs to track whether earlier blocking items were resolved, and appends new verdict entries. - Use Case: Before handing a combat-system GDD to programmers, run the review to get a verdict of APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED, with source-tagged blocking items and a scope signal for sprint planning. ## Quick Start Ask the AI to run the design-review skill on your GDD file, for example: review design/gdd/combat-system.md at full depth and report the verdict.

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 before implementation?

Run the design-review skill on the GDD file path. It checks the document against an 8-section completeness standard, validates dependency references on disk, and returns a verdict of APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED with blocking items listed.

What is the difference between full, lean, and solo review depth?

Full mode runs all phases plus parallel specialist subagent review, typically taking 8-15 minutes. Lean mode runs all phases without specialist agents for faster single-session analysis. Solo mode runs phases 1-4 only, intended for invocation from within another skill.

Which specialist agents review a game design document?

Agents are selected based on GDD content: economy-designer for costs and rewards, systems-designer for formulas, qa-lead for acceptance criteria, narrative-director for story, ux-designer for UI, and others. Game-designer is spawned for any gameplay mechanics document.

Does the design review modify the GDD file during analysis?

No, the review phases are read-only and write nothing. Only after the verdict, with explicit user confirmation, does it update systems-index.md status or append an entry to the review log file.

How does re-review tracking work for previously reviewed GDDs?

The skill checks design/gdd/reviews/ for an existing review log, reads the most recent verdict and blocking items, then tracks whether those prior items were addressed in the current session and records the new verdict.