Skip to content

a5c-ai/babysitter / library/methodologies/cc10x/skills/verification-before-completion

verification-before-completion

Verified

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

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)
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 319kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 319kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 319kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall