How do I install the Post Design Review skill?

Run npx skillmds@latest add tykisgod/post-design-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Post Design Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Post Design Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Post Design Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Post Design Review?

tykisgod (@tykisgod) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Post Design Review by tykisgod — Agent Skill

Name: Post Design Review
Author: tykisgod

Post Design Review

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.

tykisgod Updated Sep 17, 2026

File contents

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

Find the document: if a path is given, read it. Otherwise, find the most recent *_design.md in Docs/qq/.
Spawn a review subagent using the Agent tool. The subagent should:
- Read design-reviewer-prompt.md for the full review checklist
- Read the design document
- Independently explore the codebase (Services, configs, existing design docs) to verify claims — do not rely solely on what the document says exists
- Output the review in the format specified in the reviewer prompt
Verify the findings: as the main agent, independently spot-check the subagent's claims against the codebase. The subagent may misread code or reference stale information. For each finding, confirm or reject it with your own evidence before presenting to the user.
Present the verified review to the user — only include findings you confirmed. Note any subagent findings you rejected and why.
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.
If verdict is SOLID: confirm and recommend /qq:plan. If invoked with --auto (or called from a skill running in --auto mode): 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>.

---name: post-design-reviewdescription: 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.---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/`)## Process1. **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** using the Agent tool. The subagent should: - Read [design-reviewer-prompt.md](design-reviewer-prompt.md) for the full review checklist - Read the design document - **Independently** explore the codebase (Services, configs, existing design docs) to verify claims — do not rely solely on what the document says exists - Output the review in the format specified in the reviewer prompt3. **Verify the findings:** as the main agent, independently spot-check the subagent's claims against the codebase. The subagent may misread code or reference stale information. For each finding, confirm or reject it with your own evidence before presenting to the user.4. **Present the verified review** to the user — only include findings you confirmed. Note any subagent findings you rejected and why.5. **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.6. **If verdict is SOLID:** confirm and recommend `/qq:plan`. **If invoked with `--auto` (or called from a skill running in `--auto` mode):** 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>`.

Frequently asked questions