plan-reviewer

To review a plan for security and architecture risks, apply a multi-perspective critique using DevOps, Peer, Security, and Software Architect viewpoints to surface gaps and trade-offs, then produce an updated plan with concrete implementation guidance.

A multi-perspective plan critique is a review process that evaluates a proposal independently from DevOps, Peer, Security, and Software Architect viewpoints to identify weaknesses, risks, and improvement opportunities before implementation begins.

Yes, you can refine an existing plan by providing a plan.md and an optional implementation.md file, which the review process uses to generate in-place revisions and actionable implementation steps.

The best way to identify gaps in an implementation proposal is to apply a skeptical, multi-perspective peer review workflow that independently surfaces issues from SRE, security, and architectural viewpoints, resulting in actionable revisions.

Yes, the plan review process handles edge cases and staged changes by providing specific implementation guidance that includes notes on risks, decisions, and required changes for the updated plan.