evidence-verificationlisted

# Evidence-Based Verification Skill ## Overview This skill teaches agents how to collect and verify evidence before marking tasks complete. Inspired by production-grade development practices, it ensures all claims are backed by executable proof: test results, coverage metrics, build success, and deployment verification. **Key Principle:** Show, don't tell. No task is complete without verifiable evidence. --- ## Core Concepts ### 1. Evidence Types **Test Evidence** - Exit code (must be 0 for success) - Test suite results (passed/failed/skipped) - Coverage percentage (if available) - Test duration **Build Evidence** - Build exit code (0 = success) - Compilation errors/warnings - Build artifacts created - Build duration **Deployment Evidence** - Deployment status (success/failed) - Environment deployed to - Health check results - Rollback capability verified **Code Quality Evidence** - Linter results (errors/warnings) - Type checker results - Security scan results - Accessibility audit results ### 2. Evidence Collection Protocol ```markdown ## Evidence Collection Steps 1. **Identify Verification Points** - What needs to be proven? - What could go wrong? - What does "complete" mean? 2. **Execute Verification** - Run tests - Run build - Run linters - Check deployments 3. **Capture Results** - Record exit codes - Save output snippets - Note timestamps - Document environment 4. **Store Evidence** - Add to shared context - Refere