Free — no credit card
EZYE OS · AI Workflows
Claude says "done" way too early
Here's the 5-point check that catches what it missed
A five-minute verification habit that stops broken features from slipping into production every time Claude claims a task is finished.
What's inside
- The exact 5 proof points before you trust "done"
- A copy-paste prompt that forces Claude to verify itself
- Why "done" and "actually works" are different
- How to stop re-checking every output by hand
EZYE OS · AI Workflows Cheat Sheet
The Claude "Done" Verification Checklist
by Divjot Sahni · EZYE Consulting · ezye.com.au
The 5 Things Claude Must Prove
1
Point 1: It ran the task, not just described it
2
Point 2: The output matches what you actually asked for
3
Point 3: Edge cases and errors were handled, not skipped
4
Points 4 and 5 unlock the rest once you have the full list
The Verification Prompt
1
Paste this after Claude claims a task is complete
2
It forces Claude to walk back through each of the 5 points
3
Full prompt text revealed inside the guide
Free access — enter your email below