plan-review

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.

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.

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.

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.

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.

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.