Vd done is executed
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-done-is-executedAssembled 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
The always-on governor against over-claimed completion. Never call work done, fixed, passing, working, wired, or complete unless you RAN the actual Done criterion end-to-end and observed the result with your own eyes. Code that would work, a traced code path, a passing adjacent layer, or "looks right" are NOT done. Applies silently to every completion, success, or "it works" claim; dispatches the sibling vd-* skills.
SKILL.md
2.4 KB, as published. Nobody here has run it
Done Means Executed — Not Inspected
The failure this prevents: asserting something is finished based on reading the code that would run, or on a related path that does run, instead of running the real thing. The tell is a sentence like "skills-wired and persona-wired are both code-path claims I didn't execute."
The rule
A completion word — done, fixed, passing, working, wired, complete, verified — is a claim that you ran the actual Done criterion and saw the expected result. If you didn't run it, you may not use the word. Say what you actually did instead.
These are NOT done:
- Code-path verified — you read the code and it should do X. (You traced it; you didn't run it.)
- Adjacent-path verified — a lower layer or a different entry point works, so the real one "must." (See [[vd-plumbing-vs-behavior]].)
- Compiles / types pass / builds — it's runnable, not proven correct.
- Looks right — the strongest signal that you should run it. (See [[vd-run-the-real-path]].)
The loop (run on every completion claim)
- Name the real Done criterion. What exact observable behavior counts as done? Quote it if it's written down.
- Did I execute that? Not a proxy, not the plumbing — the actual user-facing path. If no → run it ([[vd-run-the-real-path]]) or downgrade the claim.
- Build the ledger. Tag each sub-claim ✅ executed / ◐ code-path / ○ assumed, and state what each does NOT establish ([[vd-claim-ledger]]).
- Report honestly. Only ✅ across every criterion earns "done." Anything else: report the gap plainly, first, before you're pushed ([[vd-report-the-gap]]).
Silent discipline
Run this in your head on every "it works." Don't narrate the framework — change what you verify and how confident you sound. Surface the reasoning only when a claim is load-bearing or you're shipping the gap.