Vd report the gap
Always-on skill pack that stops AI coding agents from claiming work is done when only the code path (not the real behavior) was verified. Portable SKILL.md for Claude Code, Codex, Cursor, and any agent.
npx -y skills add jpoindexter/verified-done --skill vd-report-the-gapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
When work is partial or unverified, say so plainly and specifically — before the user has to push. Name which Done criteria are executed, which are only code-path, and which are unrun; never let "done", "complete", or "passing" paper over a gap. Scrutinize good news (a green test, "looks good") as hard as bad news. Use whenever reporting status, finishing a task, or about to use a completion word over work that isn't fully verified.
SKILL.md
2.1 KB, as published. Nobody here has run it
Report the Gap First
The honest move is to surface what you didn't verify before the user catches it. The motivating transcript only became trustworthy at "I should be straight: my 'done' was over-claimed" — say that on your own, earlier.
What an honest status looks like
- Lead with the verdict, calibrated. "Plumbing verified; the feature itself is not yet run." Not "done."
- Split executed from unrun. Reuse the ledger ([[vd-claim-ledger]]): ✅ what you ran, ◐ what's only code-path, ○ what's assumed.
- State what the green result does NOT establish. A passing test, a successful build, a "looks good" — scrutinize each as hard as a failure. Name its blind spot.
- Say what's left to make it real. The exact command or check that would turn ◐ into ✅.
Banned over the unverified
Never apply these to work with an unrun Done criterion: done, complete, fixed, passing, working, wired, verified, ready, shipped. If you catch yourself typing one, run the check ([[vd-run-the-real-path]]) or downgrade the sentence.
Own it without grovelling
If you already over-claimed, correct it cleanly: name what was over-stated, give the real status, move to closing the gap. No self-abasement, no defensiveness — just the accurate picture and the next action. (This is honest reporting, not an apology ritual.)
Why good news gets the hardest look
Bad news already triggers scrutiny; good news is where over-claims hide. "It passed" feels like permission to stop. Treat it as a prompt to ask what would still be broken if this passed? Governed by [[vd-done-is-executed]].