review

Critique plans against clarity, testability, verification, and specificity criteria.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/suhwan/claude-registry --skill review-suhwan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/suhwan/claude-registry/tree/main/skills/quality/review
Command: npx skills add https://github.com/suhwan/claude-registry --skill review-suhwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Critically evaluate plans and designs to ensure they meet clear criteria and reduce risk before execution.

Core Features & Use Cases

  • Comprehensive critique against defined standards (clarity, testability, verification, specificity).
  • Actionable feedback to drive iterative improvements.
  • Use Case: product plans or design proposals are reviewed to surface ambiguities and missing requirements.

Quick Start

Feed a plan to Critic and request a formal, criteria-based review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I critique a proposed plan against predefined quality criteria?

To critique a proposed plan against predefined quality criteria, you input the plan for evaluation. The review assesses clarity, testability, verification, and specificity to surface ambiguities and missing requirements before execution.

What is a design review and how does it improve product plans?

A design review evaluates product plans or design proposals against rigorous quality standards to ensure they meet clear criteria. It outlines the plan's scope, typical use cases, and edge cases where the plan may fail, providing actionable feedback.

How do I verify the testability and specificity of a project plan?

Verifying the testability and specificity of a project plan requires checking it against defined quality criteria. The review process identifies missing requirements and outlines edge cases where the plan may fail, ensuring concrete verifications are satisfied.

When do I need a formal criteria-based review for my design proposals?

You need a formal criteria-based review for design proposals when you want to reduce risk before execution. It surfaces ambiguities and missing requirements by evaluating the proposal's scope and potential edge cases against strict quality standards.

What are the limitations of using automated plan critique for quality standards?

A limitation of criteria-based plan critique is that it only evaluates the proposed plan against predefined standards like clarity and testability. It outlines edge cases where the plan may fail, but does not execute the plan or guarantee real-world success.