plan-mega-review

To review an architecture proposal for failure modes, apply a mode-driven plan review to surface security gaps, observability blindspots, and ambiguous scope, producing an error and rescue registry with explicit rollback steps.

A plan review for software deployment is a systematic audit of design documents and deployment strategies to map exhaustive errors and rollback posture. You need one when shipping complex features that require confidence in failure remediation.

To conduct a scope reduction review on a pull request, run a mega plan review in SCOPE REDUCTION mode to audit the changes, producing prioritized TODOs.md entries, ASCII data-flow diagrams, and explicit stop-gate questions before proceeding.

Yes, the architecture review process supports observability runbook generation by analyzing deployment plans to identify blindspots and outputting explicit alerts, tests, and runbook recommendations alongside the remediation plan.

The best way to make deployment plans bulletproof is to run a rigorous audit that maps exhaustive failure modes, generating error registries, ASCII diagrams, and rollback procedures to ensure teams ship with confidence and clear remediation paths.

When using HOLD SCOPE mode for design document reviews, the audit posture and depth are fixed to the current boundaries, meaning it will not surface out-of-scope architectural risks or propose scope expansions beyond the original design document.