design-reviewer — Claude Code subagent: what it does, how to install
design-reviewer audits feature designs and implementation plans without conversational bias. Flags ambiguities, missing edge cases, and contradictions before implementation begins.
Elastic-2.0 ★ 155 updated 2026-10-29
/plugin marketplace add serpro69/claude-toolbox
/plugin install kk@claude-toolboxWhat design-reviewer does
The subagent inspects feature documentation, including design.md, implementation.md, and tasks.md. It remains structurally isolated from the earlier planning discussion. Because it lacks access to meeting notes or discarded alternatives, it judges specifications solely on written text.
The review workflow enforces strict sequence. It first retrieves design-review-criteria.md alongside verification-policy.md. Document evaluation never starts before these rules load. The agent then scans the repo with Read, Grep, and Glob to confirm that referenced files actually exist. Background context comes from capy_search targeting kk:arch-decisions and kk:review-findings.
The subagent lacks shell execution rights, stopping immediately if review criteria files cannot be located instead of guessing rules. It groups issues into taxonomy codes like INCOMPLETE or TECH_RISK, assigning severities from P0 to P3 and confidence scores up to 10.
What it helps with
- spot conflicting requirements across design and task files
- detect missing error handling or omitted migration pathways
- verify that documented functions exist in current source code
- evaluate architectural readiness without relying on unwritten chat context
Example prompts for the agent
- Review design.md and tasks.md for the new billing service
- Evaluate the storage migration implementation plan against repository patterns
- Inspect the feature specification and list any P0 or P1 architectural concerns
How to install design-reviewer
1Plugin marketplace
/plugin marketplace add serpro69/claude-toolbox/plugin install kk@claude-toolbox2Manually: put the files in place
.claude/agents/design-reviewer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/design-reviewer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/design-reviewer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about design-reviewer
How to install design-reviewer in Claude Code?
Run /plugin marketplace add serpro69/claude-toolbox in your environment, then execute /plugin install kk@claude-toolbox to complete installation.
What does design-reviewer do?
It reads engineering planning documents, verifies their claims against the repository, and reports specification defects categorized by severity.
Why is chat history hidden from this subagent?
Omitting conversational background prevents authorship attachment. If an architectural tradeoff was discussed verbally but omitted from the document, the subagent flags it as missing.