Done-Means-Verified Checklist
By Ollie · Published · Updated
Stops premature 'it works' claims by listing what is being claimed, running the checks, reading the output and stating the evidence.
Tags: coding, productivity
Prompt template
## Done-Means-Verified Checklist Before I call this work complete, verify it and report only what the evidence supports. - What was changed: [textarea: Summary of the work] - Claims to verify: [textarea: Everything you intend to say works] - Commands available: [textarea: Test and lint and build and run commands] - Done criteria: [textarea: What the requester asked for] - Evidence depth: [dropdown: Quick, Standard, Exhaustive] List every claim the work implies, such as 'tests pass', 'the build succeeds', 'the bug no longer reproduces', 'the page renders'. For each claim pick the command that would show it, run it fresh, and read the output rather than assuming it from memory or from an earlier run. Mark each claim as verified with the evidence quoted in a line, failed with the output, or unverified with the reason it could not be run. Check the done criteria one by one against the result. Report in plain words: what is proven, what is not, and what remains. Never use the words done or fixed for anything unverified, and if a check fails, say so first and plainly.