design-review

Reviews game design documents for completeness, consistency, and implementability against project standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game design documents often reach programmers with missing sections, vague rules, or contradictions with other systems, causing implementation delays and rework. This Skill audits a design document against an eight-section standard before handoff. ## Core Features & Use Cases - Completeness Checklist: Verifies the document contains Overview, Player Fantasy, Detailed Rules, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria sections. - Consistency and Implementability Analysis: Checks that formulas match described behavior, edge cases align with main rules, dependencies are bidirectional, and no hand-waved sections remain. - Structured Verdict Output: Produces a review report with completeness score, issues, balance concerns, prioritized recommendations, and an APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict. - Use Case: Before handing a new combat system GDD to programmers, run this Skill to catch a missing Formulas section and a contradiction with the existing damage system, then route the verdict back into the systems index. ## Quick Start Ask the assistant to run the design-review skill on design/gdd/combat-system.md 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 this Skill with the path to the design document. It reads the document, the master CLAUDE.md, and related GDDs, then checks an eight-section standard covering Overview, Rules, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria.

What sections should a game design document contain?

The standard requires eight sections: Overview, Player Fantasy, Detailed Rules, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria. The review reports how many of the eight are present and lists any that are missing.

Does the design review check consistency with other game systems?

Yes. It reads related documents in design/gdd/ and checks for conflicts with existing mechanics, unintended cross-system interactions, bidirectional dependencies, and alignment with the game's established tone and pillars.

Can this Skill update the systems index after a review?

No, the Skill is read-only. It recommends the appropriate status update for the systems index based on the verdict, but the user or the /design-system skill must perform the actual update.

What verdicts does the design review produce?

The review ends with one of three verdicts: APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED. It also outputs completeness score, consistency issues, implementability concerns, balance risks, and prioritized recommendations.