evidence-verificationlisted

# Evidence-Based Verification Skill **Version:** 1.0.0 **Type:** Quality Assurance **Auto-activate:** Code review, task completion, production deployment ## 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. --- ## When to Use This Skill ### Auto-Activate Triggers - Completing code implementation - Finishing code review - Marking tasks complete in Squad mode - Before agent handoff - Production deployment verification ### Manual Activation - When user requests "verify this works" - Before creating pull requests - During quality assurance reviews - When troubleshooting failures --- ## 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