plan-mode-review

A structured plan review applies a multi-phase examination to architectural changes, enforcing a Phase 0 self-review for outcome definition before proceeding to a 5-phase technical review covering architecture, code quality, tests, performance, and production readiness.

A production readiness assessment evaluates blast radius, rollback procedures, dependencies, data migrations, and success metrics to ensure cross-service changes are safe to deploy. This assessment acts as a final gate before code changes ship.

Start a multi-phase code review by providing the change plan and PR details, then initiate Phase 0 to define outcomes and options. This guides a structured examination through architecture, code quality, tests, performance, and production readiness with triage and decision logging.

You need a Phase 0 self-review before code changes when dealing with non-trivial architectural changes or cross-service work. It requires defining the expected outcome and available options to prevent shipping unclear or risky modifications.

Yes, plan mode review supports risk management by enforcing a production readiness gate. This gate examines blast radius, rollback strategies, dependencies, and data migrations to ensure deployment safety for non-trivial changes.

The best way to document decisions during a technical review is using structured triage and decision logging within a 5-phase examination framework. This ensures architecture, code quality, test, and performance assessments are recorded consistently using reference templates.