review_plan

To review an architecture design document for security and performance risks, perform a skeptical check against your specification to identify injection points, authentication gaps, and latency bottlenecks before development begins.

Validating requirements coverage in a technical implementation plan requires applying structured checks to ensure every specification point is addressed and to flag missing modular design or redundant rewrites.

Checking if a migration plan includes a proper rollback strategy involves assessing the design document for backward compatibility, deployment impact, and explicit migration reversal steps to prevent data loss.

Yes, you can use a skeptical plan review for deployment and migration plans across software projects to validate completeness, consistency, and security by applying structured risk and requirements checks.

You need to perform a skeptical review of your technical specification when transitioning from design to coding, ensuring implementation plans are evaluated for correctness, security gaps, and performance bottlenecks.