verify-before-done

Enforces evidence-based verification before declaring tasks, stories, or QA verdicts complete.

3|3|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/joaoguirunas/team-os --skill verify-before-done-joaoguirunas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-before-done
Source: https://github.com/joaoguirunas/team-os/tree/main/.claude/skills/verify-before-done
Command: npx skills add https://github.com/joaoguirunas/team-os --skill verify-before-done-joaoguirunas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers frequently claim work is finished — tests pass, bugs are fixed, stories are done — without fresh evidence, leading to false success reports, broken builds, and premature commits. This Skill imposes a mandatory verification gate so no completion claim is made without running the actual check first. ## Core Features & Use Cases - The Gate (5 steps): Identify the proving command, Run it now, Read the full output and exit code, Verify it supports the claim, then Claim with cited evidence. - Claims-to-evidence table: Maps common claims (tests pass, lint clean, bug fixed, story done) to the minimum fresh evidence required, including red-green regression cycles and dry-run migration checks. - Red-flag language detection: Blocks premature phrases like "should work now" or "probably passes" and counters rationalizations such as "it was a trivial change" or "I ran it earlier." - Use Case: Before a developer marks a story as done or a QA agent issues a PASS verdict, the Skill requires a fresh test suite run with 0 failures and exit code 0, cited directly in the report. ## Quick Start Before marking this task complete, run the full test suite and report the actual output and exit code as evidence.

Frequently Asked Questions about verify-before-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify work is actually done before marking a task complete?▼

Follow the 5-step gate: identify the command that proves the claim, run it now, read the full output and exit code, confirm it supports the claim, then state the claim citing that evidence. Any edit after a check invalidates prior evidence.

What evidence is required before saying tests pass?▼

A fresh run of the full test suite showing 0 failures and exit code 0. Partial runs or results from before the last edit do not count, since any change invalidates earlier evidence.

How should a bug fix be verified before closing it?▼

Reproduce the original symptom, apply the fix, and confirm the symptom is gone. For regression coverage, document a red-green cycle: the test fails without the fix and passes with it.

Can I trust a subagent's report that work succeeded?▼

No. Subagents may report success with incomplete work, so verify the actual files and test results yourself before relaying or acting on their claims.

When should this verification gate be applied?▼

Always, before marking tasks or stories done, committing code, issuing QA verdicts like PASS or FAIL, reporting progress, or ending a session with deliverables claimed as ready.