Files
ai-agent-harness/skills/verification-before-completion/SKILL.md

2.2 KiB

name, description
name description
verification-before-completion Require fresh, claim-specific evidence before reporting work complete, fixed, passing, ready, or safe to commit or publish.

Verification Before Completion

No completion claim without fresh evidence. This workflow verifies status; it does not authorize a commit, push, deployment, database operation, or other protected action.

Verification Gate

Before making a success claim:

  1. State the exact claim internally and identify which observable check can prove or disprove it.
  2. Run the relevant command or inspection fresh after the final change. Use repository-defined commands; do not invent a substitute that proves a different property.
  3. Read the complete result needed for the claim, including the exit code, failure count, skipped checks, and generated changes.
  4. Compare the evidence with the claim and the approved acceptance criteria.
  5. Report only the status supported by that evidence.

Evidence Rules

  • A passing lint does not prove compilation, a passing build does not prove runtime behavior, and a passing narrow test does not prove unrelated requirements.
  • For a regression test, establish that it is capable of detecting the defect when practical; do not treat an always-passing test as proof.
  • Recheck the worktree or final diff after generators, formatters, tests, or builds that may create or alter files.
  • Separate verified results, failures, checks not run, and pre-existing failures. Never quietly merge them into a success statement.
  • For delegated work, inspect the returned changes and run the relevant verification yourself before accepting the completion claim.
  • For absence or universal claims such as “no occurrences” or “all projects,” use a check whose scope actually covers the claim.

Reporting

  • Cite the commands or inspections actually run and summarize their observed results.
  • If a required check cannot run, state the actual incomplete or blocked status and the exact reason.
  • Do not use “should work,” “probably passes,” “seems correct,” or similar language as a substitute for verification.
  • Do not claim completion while a required check is failing or while known correctness, encoding, security, or generated-output drift remains unresolved.