Skip to content
Back to skills

Post Design Review

ASecurity

Review a game design document from an implementer's perspective — check self-consistency, playability, buildability, and codebase gaps. Use after writing a design doc, or when you want to validate an existing design against the current codebase.

  • 11 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
development

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add tykisgod/quick-question --skill post-design-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Post Design Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Post Design Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tykisgod-post-design-review/badge)](https://www.skillsdirectory.com/skills/tykisgod-post-design-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: "Review a game design document from an implementer's perspective — check self-consistency, playability, buildability, and codebase gaps. Use after writing a design doc, or when you want to validate an existing design against the current codebase."
---

> Run qq scripts as `${CLAUDE_PLUGIN_ROOT}/bin/<name>`: they are not on PATH, so a bare `qq-execute-checkpoint.py` exits 127.

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).

Review a game design document from an implementer's perspective.

Arguments: $ARGUMENTS (path to a design document, or empty to use the most recent design doc in `Docs/qq/`)

## Process

1. **Find the document:** if a path is given, read it. Otherwise, find the most recent `*_design.md` in `Docs/qq/`.
2. **Spawn a review subagent** (Agent tool) that reads [design-reviewer-prompt.md](design-reviewer-prompt.md) and the design document, checks the document's claims against the codebase itself, and returns the review in that prompt's format.
3. **Verify, then present:** check each finding yourself against the document and the code; the subagent can misread code or cite stale information. Present only the findings you confirmed, and say which ones you rejected and why.
4. **If verdict is HAS GAPS or NEEDS REWORK:** revise the document together with the user. Re-run the subagent review after revisions. Loop until SOLID or the user explicitly accepts the gaps. Items moved to the document's "Needs the user's decision" list count as resolved.
5. **If verdict is SOLID:** confirm and recommend `/qq:plan`. **If invoked with `--auto`:** run `qq-execute-checkpoint.py pipeline-advance --project . --completed-skill "/qq:post-design-review" --next-skill "/qq:plan"`, then invoke `/qq:plan --auto <document-path>`.

Files in this skill

  • SKILL.md2 KB
  • design-reviewer-prompt.md2.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.