verify-plan

To verify a project plan against your codebase, provide the plan document to the verifier to cross-check factual claims. It rigorously checks file existence, location accuracy, and reference counts to prevent misalignment.

Codebase plan validation checks for file existence, location accuracy, reference counts, missed files, non-changing elements, cross-phase dependencies, and test baselines to prevent errors that cause failures.

You need to audit a project plan for codebase misalignment during post-plan iterations and when plans are updated. Re-validation is also necessary when resuming a paused plan to ensure references still match.

To re-validate file paths and reference counts when resuming a paused plan, run an adversarial verification process against the repository contents. This ensures all factual claims still match the current repo state.

Yes, you can use automated code review to check cross-phase dependencies in a plan. The verification process enforces rigorous checks to ensure dependencies and test baselines remain accurate across the repository.