verification-before-completion
Verify work actually meets its brief BEFORE declaring it done — a structured self-review pass that catches the gaps, unmet requirements, and untested claims that 'looks finished' hides. Use before handing over any deliverable (document, code, analysis, plan), when past work kept coming back with 'you missed…', or as the standing final step of any multi-step task. Produces the verified deliverable plus a short verification record: what was checked, what was found and fixed, what remains open.
npx skills add mohitagw15856/pm-claude-skills --skill verification-before-completion --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Verification Before Completion Skill "Done" is a claim, and most agents (and humans) declare it by *feeling* — the output looks complete, reads well, compiles. This skill replaces the feeling with a check: re-derive what was actually asked, audit the work against it, try to break it, and only then hand it over. The gap between looks-done and is-done is where rework lives. ## What This Skill Produces - The deliverable, **after** fixes the verification pass surfaced - A **verification record** (3-8 lines): checked against what, found and fixed what, still open what - Honest **residuals**: anything not verified, stated rather than implied ## The Verification Pass 1. **Re-read the ORIGINAL ask — not your memory of it.** Requirements decay in working memory over a long task; the third instruction in the user's message is the classic casualty. List every explicit requirement and every implicit one (format, tone, length, audience) as a checklist. *Then* audit the work against the list, item by item. 2. **Check the claims, not just the presence.** A section existing isn't the section being right. For each substantive claim/number/behaviour in the deliverable: is it grounded (traceable to
- What This Skill Produces
- The Verification Pass
- Output Format
- Quality Checks
- Anti-Patterns
What does the verification-before-completion skill do?
Verify work actually meets its brief BEFORE declaring it done — a structured self-review pass that catches the gaps, unmet requirements, and untested claims that 'looks finished' hides. Use before handing over any deliverable (document, code, analysis, plan), when past work kept coming back with 'you missed…', or as the standing final step of any multi-step task. Produces the verified deliverable plus a short verification record: what was checked, what was found and fixed, what remains open.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill verification-before-completion --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.