Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/design-review
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Passed 8 of 15 test cases with the skill, and 7 of 15 without it.
and 4 more in the full report
5 fixed7 passed either way8 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/11/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We ran a design review on `design/gdd/nonexistent-feature.md`, but the file is missing from disk. Should we report NEEDS REVISION or APPROVED with a warning?
| Checked | Without skill | With skill |
|---|---|---|
| Issues a final verdict of `NOT ASSESSED` when the target design document cannot be found or read. | Missed | Passed |
| Names the missing document and identifies which workflow skill produces it. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow,system_overrides
Resolved above — use as-is; --review overrides review_mode. --depth is
the pre-1.1 name for the same flag: treat --depth <mode> exactly as
--review <mode>, and say once that it was renamed. Given both, --review
wins and --depth is ignored — say so. No block → defaults in
.claude/docs/config-resolution.md.
See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
workflow for the GDD under review — use the system_overrides row for <system> if the block lists one, else the project value. Validation scope follows the tier:
full — all 8 sections validated; any missing section blocks approval.standard — the 5 required sections (Overview, Detailed Rules, Edge Cases,
Dependencies, Acceptance Criteria) block if missing; Formulas blocks only when
the system defines numeric rules (rates, curves, thresholds, costs — the
category is a hint, not the test); Player Fantasy and
Tuning Knobs are advisory (warn, never block) unless workflow_overrides
require them.minimal — no GDD is expected; if one exists, validate the 5 standard
sections advisorily.Resolved mode controls how thorough this review is:
full: Complete review — all phases + specialist agent delegation (Phase 3b)lean: All phases, no specialist agents — faster, single-session analysissolo: Phases 1-4 only, no delegation, no Phase 5 next-step prompt — use when called from within another skilltest cases passed, vs 7 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.