design-review

Execute a fleet of critics on code, diffs, or plan files.

4|Updated May 8, 2026

Search Tags:#code analysis #software design #design principles #design review #Git integration

Ready to run

npx skills add https://github.com/Tsadoq/claude-better-plan --skill design-review-tsadoq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/Tsadoq/claude-better-plan/tree/main/skills/design-review
Command: npx skills add https://github.com/Tsadoq/claude-better-plan --skill design-review-tsadoq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for thorough design reviews of code, diffs, or plan files, providing an in-depth analysis to ensure adherence to design principles and identify potential issues.

Core Features & Use Cases

Parallel Critic Fleet: Executes a fleet of critics to assess various aspects of design, including module depth, information hiding, and naming conventions.
Design Principle Validation: Reviews against a set of design principles derived from "A Philosophy of Software Design" by John Ousterhout.
Git Integration: Supports reviewing diffs from specific commits or ranges, as well as files and directories directly.
Plan File Review: Analyzes plan files for design quality and adherence to best practices.

Quick Start

Run a design review on the latest changes in the current branch:

/design-review

Frequently Asked Questions about design-review

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

FAQPage Schema

How do I conduct a software design review on my code?▼

To conduct a software design review, you can automate the process by running a fleet of parallel critics on your source code, diffs, or plan files to identify design flaws and validate adherence to software design principles.

What design principles are used during a code analysis?▼

Code analysis validates design principles derived from "A Philosophy of Software Design" by John Ousterhout, focusing on metrics like module depth, information hiding, and naming conventions to identify potential design flaws.

Can I review Git diffs for design flaws?▼

Yes, you can review Git diffs for design flaws by analyzing changes from specific commits or commit ranges. This Git integration allows targeted design validation on recent branch updates.

How do I analyze plan files for software design quality?▼

You can analyze plan files for software design quality by executing a critic fleet that evaluates the files against established design best practices and principles, ensuring structural soundness before implementation.

Does the design review process require access to the full source code?▼

Yes, the design review process requires access to the source code and plan files to execute its critics and provide an in-depth analysis of module depth, information hiding, and overall design adherence.

What is the best way to automate design principle validation?▼

The best way to automate design principle validation is executing a parallel critic fleet that assesses various aspects of design simultaneously, providing comprehensive identification of flaws across files or Git diffs.