plan-review

Automate structured design and code reviews with PDCA-driven decision making.

Updated Feb 2, 2026

Search Tags:#code-review #issue-tracking #architecture-review #design-review #plan-review #pdca

Ready to run

npx skills add https://github.com/gaegulgaegul/gaegulzip --skill plan-review-gaegulgaegul

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Review addresses the need for systematic, PDCA-aligned reviews of designs and code to improve quality and reduce rework.

Core Features & Use Cases

Dual-mode reviews (Design → Do and Analyze) with brief.md-based design reviews and code reviews focusing on architecture, test strategy, code quality, tests, and performance.
Change-size framing (BIG CHANGE vs SMALL CHANGE) with per-section issue analysis, trade-off recommendations, and user confirmations.
Workflow integration and explicit prompts like "리뷰해줘", "설계 리뷰", "코드 리뷰", "plan-review" to trigger the evaluation.

Quick Start

Use a single command to request a review: plan-review design {feature} or plan-review code {feature}.

Frequently Asked Questions about plan-review

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

FAQPage Schema

How do I conduct a structured design review for a new feature?▼

A structured design review evaluates a brief.md document to guide PDCA-driven decision making. It frames changes as BIG or SMALL, analyzes per-section issues, recommends trade-offs, and requires explicit user confirmation before proceeding.

What is the best way to automate code quality and architecture analysis?▼

Automated code quality analysis evaluates architecture, test strategy, and performance within a PDCA workflow. It captures findings, recommends trade-offs, and enforces consistent review outcomes through structured Analyze mode reviews.

How do I trigger a plan review for my code or design docs?▼

Trigger a plan review using commands like "plan-review design {feature}" or "plan-review code {feature}". You can also use prompts like "리뷰해줘", "설계 리뷰", or "코드 리뷰" to start the evaluation workflow.

Does this design review process support PDCA-driven decision making?▼

Yes, the design review process explicitly supports PDCA-driven decision making through dual-mode reviews: Design → Do and Analyze. It captures findings and integrates them into the PDCA cycle to drive actionable outcomes.

Can I use this code review tool for both big and small architectural changes?▼

Yes, the code review tool supports both BIG CHANGE and SMALL CHANGE frameworks. It provides per-section issue analysis and trade-off recommendations tailored to the scale of the architectural modification.

What do I need to prepare before starting a design review?▼

You need to prepare a brief.md document describing your feature design. The review process evaluates this document, frames the change size, and prompts for explicit user confirmation on trade-off recommendations.