review-design

Review design and implementation documents for quality and technical soundness.

147|31|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/serpro69/claude-toolbox --skill review-design-serpro69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-design
Source: https://github.com/serpro69/claude-toolbox/tree/main/kodex-plugin/skills/review-design
Command: npx skills add https://github.com/serpro69/claude-toolbox --skill review-design-serpro69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review design, implementation, and task documents produced during design to ensure quality, consistency, and feasibility before coding.

Core Features & Use Cases

  • Gate design reviews between the design and implementation stages to ensure completeness, clarity, and feasibility.
  • Support Standard and Isolated review modes with structured findings, provenance, and author context.
  • Produce actionable feedback and risk signals that help teams align on design intent before coding.

Quick Start

Invoke review-design with a feature name to start the gate and generate a structured findings report.

Frequently Asked Questions about review-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a design review gate in software architecture?

A design review gate is a quality checkpoint between design and implementation stages that ensures documentation completeness and feasibility. It coordinates parallel reviews of architecture documents to produce actionable feedback and risk signals before code is written.

How do I generate a structured findings report for code quality risk management?

To generate a structured findings report for code quality risk management, invoke a design review with a feature name. The review assesses documentation quality and consistency, returning provenance-backed findings and risk signals to align teams on design intent.

Can I run isolated design reviews for separate feature workflows?

Yes, you can run isolated design reviews for separate feature workflows. The review process supports both standard and isolated modes, allowing you to assess technical soundness and document quality independently while maintaining structured findings and author context.

Do I need existing SKILL.md and process files to assess architecture documentation?

Yes, you need existing SKILL.md and process files to assess architecture documentation effectively. The review assembles documentation and context directly from these feature files to evaluate consistency, completeness, and technical feasibility before generating the final report.

What are the limitations of automated design document reviews?

Automated design document reviews are limited to assessing the quality and consistency of existing implementation and task documents. They cannot fix architectural flaws directly or generate missing design specifications, but instead highlight risk signals and actionable feedback for the team.