proof-verify

# Proof Verify Plan-based verification: freeze acceptance criteria BEFORE building, verify AFTER with independent agents. ## When to Use - After completing a feature/fix that was built from a plan - When you need independent confirmation that work meets spec - When the builder should NOT verify their own work - Trigger phrases: "verify against plan", "check the implementation", "proof check", "independent review" ## The Pattern ``` PHASE 1: PLAN (before any code) Create .proof/PLAN.md with numbered acceptance criteria Each AC: testable, specific, has a verification command or check Plan is FROZEN - no changes during build PHASE 2: BUILD (normal work) Implement against the plan Mark progress in .proof/PROGRESS.md Builder does NOT self-verify PHASE 3: VERIFY (after build, independent agent) Fresh agent reads PLAN.md (never saw the build process) Walks through each AC, runs verification commands Writes .proof/VERDICT.md with PASS/FAIL per criterion If any FAIL → .proof/PROBLEMS.md with specific fixes PHASE 4: FIX (if needed) Builder reads PROBLEMS.md, makes minimal fixes Back to PHASE 3 (re-verify) Loop until all PASS ``` ## Phase 1: Create Plan Create `.proof/PLAN.md` in the project root: ```markdown # Verification Plan **Created:** YYYY-MM-DD HH:MM **Task:** [one-line description] **Builder:** [session ID or "current"] **Status:** FROZEN ## Acceptance Criteria ### AC1: [short name] **Description:** [what must be true] **Verify:** [exact ...