donelisted

# done — the evidence gate `/done [what was being built, or a path to its spec/plan]` Answer one question: **is there evidence this change works and does what was asked — or does it merely look finished?** "The work looks done" is the weakest signal in agentic coding; this gate replaces it with quoted output and an independent review. It never makes the change better — it decides whether the change is *ready*. ## Step 0 — Establish the yardstick Identify **the diff** (uncommitted changes, or the branch vs its merge base) and **the intent**: the change folder's `spec.md`/`plan.md` if this came from the feature skill, the bug repro if from bugfix, otherwise ask the user for one sentence of "what was this supposed to do". No yardstick → the review below can only check correctness, not compliance; say so. ## Step 1 — Evidence checklist Copy this checklist into the response and fill it in as you go — every line gets **quoted command output or an explicit ✗ with the reason**. An unticked line with a reason is honest; a ticked line without evidence is the exact failure this skill exists to prevent. ``` - [ ] Full test suite: <command> → <pass/fail counts, verbatim tail> - [ ] Lint / typecheck: <command> → <result> (✗ if repo has none) - [ ] Build: <command> → <result> (✗ if n/a) - [ ] Ran the actual change: <command / flow> → <observed behavior> - [ ] Diff hygiene: no debug prints (grep the diff for [DEBUG- — the tag bugfix leaves), no comme