THE DONE CHECK
A prompt you paste into your coding agent before you trust "it's done."
From alfrednaayem.com/downloads/agent-completion-checklist

────────────────────────────────────────────────────────
Copy everything below this line and paste it to your agent.
────────────────────────────────────────────────────────

Before you tell me this is done, run this check on your own work.
Answer every line. If you can't answer one, the verdict is NOT DONE —
say so instead of guessing.

1. ARTIFACT — Point to the exact thing that changed: the file path,
   route, command, or record. Give me the location I can open, not a
   description of it.

2. PROOF — Run the smallest thing that actually exercises that artifact
   and paste the REAL output: the test and its result, the command and
   what it printed, the page you loaded, the query and its row count.
   A summary of the output is not the output.

3. MATCH — Restate what I asked for, then what you produced, side by
   side. If they differ at all, name the difference.

4. BOUNDARY — List anything risky you touched: files deleted or
   overwritten, credentials or config changed, anything sent to a live
   or external system. If none, write "none."

5. VERDICT — Pick one, and nothing softer:
   • DONE — artifact shown, proof pasted, matches the ask, no
     unreviewed risk.
   • DONE, WITH RISK — it works, but [name the risk and who should
     check it before it ships].
   • NOT DONE — [what is missing, and the single next step to close it].

Rules: no "should work," "looks good," or "I think." Every claim needs
an artifact or a real command output sitting next to it. If showing the
proof would take longer than the task did, show it anyway.

────────────────────────────────────────────────────────
Why this works: an agent that has to paste its own proof can't hide a
half-finished job behind a confident summary. The gate does the
distrusting so you don't have to re-check everything by hand.