verify-before-donelisted

# Verify Before Done Self-reported success is the most expensive lie in agentic coding: an agent that grades its own homework will, on a long enough timeline, tell you something works when it doesn't. This skill replaces "I believe this is done" with "here is the evidence this is done." ## When to use this - You're about to write "fixed", "done", "working", "tests pass", "should work now", or similar, at the end of a turn. - You implemented something and are tempted to report success based on reading the code rather than running it. - A user asks you to verify, double-check, or confirm that something works. ## Instructions 1. **Name the claim.** Before finishing, state precisely what you're claiming is true ("the login form now rejects invalid emails", "the flaky test no longer flakes"). A vague claim ("I fixed it") can't be verified — a specific one can. 2. **Get evidence, not confidence.** Climb this ladder as far as the task allows — don't stop at a lower rung when a higher one is available. See `references/evidence-ladder.md` for the full breakdown with examples. - Rung 0 — *Unverified assumption*: "this should work." Never report this as done. - Rung 1 — *Static read*: re-read the diff and reasoned it's correct. Weak on its own. - Rung 2 — *Automated check*: ran the test suite / linter / type-checker and it's green. - Rung 3 — *Reproduced the scenario*: reproduced the original failure, applied the fix, reproduced again, and it's now