proof-verify

Spec-driven verification is enforced by isolating the builder from the review process through a frozen plan file and a fresh-context agent that independently evaluates the implementation against testable acceptance criteria.

Independent agent code review prevents confirmation bias by verifying implementations in an isolated context without access to the builder's progress notes, ensuring validation strictly against frozen specifications rather than builder assumptions.

Start plan-based verification by creating a .proof/PLAN.md file containing testable acceptance criteria in your project root, then spawn an independent agent to validate the implementation against that frozen specification.

Yes, structured plan files with testable acceptance criteria are required before code implementation to maintain high-integrity development cycles and enable independent quality assurance verification.

Independent verification requires builder isolation to prevent the builder's own assumptions from influencing the validation, ensuring code is strictly validated against frozen acceptance criteria for high-integrity development.

Use plan-based verification when implementing complex features or security-sensitive logic where you need to guarantee the final output strictly adheres to a pre-defined specification without confirmation bias.