Verification Before Completion

Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed.

a5c-ai Updated 1.7k repo stars

File contents

Rules

  • Never claim "should work" without evidence
  • Never claim success without exit code 0
  • Never claim a bug is fixed without reproduction failure
  • Always capture and report exit codes
  • Always run the full test suite, not just targeted tests
  • Use timeout guards (timeout 60s) to prevent hanging

When to Use

  • Before completing any BUILD workflow step
  • Before claiming a DEBUG fix is verified
  • Before approving a REVIEW result
  • Before marking any task as done

Agents Used

  • integration-verifier (primary consumer)
  • component-builder (TDD evidence)
  • bug-investigator (fix evidence)

a5c-ai/babysitter/tree/main/library/methodologies/cc10x/skills/verification-before-completion commit 343749ac3a

Frequently asked questions

npx skillmds@latest add a5c-ai/verification-before-completion