Adversarial Verify — attack your own "done" — refactor-chain · verify

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: verify — runs inside every lane step immediately BEFORE orchestrate.mjs advance --delta legal, and again inside the final review gate · Prerequisite: the step's edits are complete and refactor-verify has a baseline result in hand · Next: claim survives → advance --delta legal; claim falls → fix or roll back, then re-attack. Adaptivity / conditional: repo-agnostic; the attack angles adapt to what the step claims.

Purpose

The person who just made a change is the least qualified person to certify it — they share every assumption the change was built on. This skill forces a role switch: state the completion claim precisely, then spend a round genuinely trying to destroy it from three fixed angles — wrong-assumption (what did I take on faith?), edge-case (which input/state/timing did I not consider?), and does-it-actually-run (was this executed, or does it merely read correctly?). Only a claim that survives all three earns advance --delta legal. A claim that falls was a bug caught minutes before it would have been compounded by the next step.