review-plan

To critique an implementation plan, you stress-test it for correctness, security, performance, and scope issues. This identifies missing edge cases and unsafe assumptions early, providing severity-prioritized feedback to refine your pre-implementation design.

Plan stress-testing is the process of analyzing a pre-implementation plan across multiple perspectives like architecture and testing to find improvement opportunities. You need it before building complex features to uncover over-engineering and avoidable rework.

Review an implementation plan by applying multi-perspective critique across security, performance, and architecture. This synthesizes feedback into actionable recommendations, highlighting missing edge cases and unsafe assumptions for concrete plan improvement.

Yes, you can use automated plan review for pre-implementation planning to analyze scope and duplication. It evaluates your design against multiple review perspectives and returns severity-prioritized feedback to refine your implementation strategy.

The best way to identify over-engineering and risks is through structured critique synthesis. By evaluating your plan across testing, architecture, and scope dimensions, you get severity-prioritized improvement recommendations that slow delivery.

Your implementation plan fails because it lacks multi-perspective stress-testing for performance and architecture constraints. Critiquing the plan before coding uncovers unsafe assumptions and delivers actionable recommendations to fix structural gaps.