10x-plan-review

Reviewing an implementation plan involves scanning internal consistency, detecting contradictions, grounding file and symbol claims, and verifying the riskiest assumptions against the codebase to confirm the plan is architecturally fit and executable.

Feasibility analysis checks a plan's substance by validating the desired end state, success criteria, and scope boundaries, ensuring architectural fitness and that the implementation can actually be executed without wasted engineering time.

You can check for contradictions by performing consistency and contract checks across defined endpoints and surfaces, detecting promise gaps and contract-break risks, and validating progress formatting against the required structure.

Yes, deep mode verifies the riskiest claims against the codebase by performing path and symbol grounding checks, providing concrete evidence that architectural assumptions hold true before implementation begins.

The required progress format is a structured `## Progress` section within plan.md that enforces specific formatting contracts, allowing the review process to extract end-state, success criteria, and progress data accurately.

Yes, loading plan.md is required to perform an architecture and feasibility review, while optional plan-brief.md and lessons.md files provide additional context for extracting end-state and success criteria.