evidence-verification

Verification requires collecting evidence across tests, builds, and code quality checks. This skill standardizes that process by running all necessary checks, capturing results with exit codes and timestamps, and generating a combined evidence report that proves the task meets production-grade quality standards.

Evidence-based task completion requires test results, build status, code-quality metrics, and deployment health checks. This skill provides templates and a protocol to systematically identify verification points, execute checks, capture outcomes, and store evidence in shared context for compliance.

Yes. This skill enforces an evidence collection protocol that runs tests, executes builds, and lints code automatically, then combines all results into a single report. It stores findings with exit codes and timestamps to create undeniable proof of task completion.

Unverified claims lead to production issues because they lack backing evidence. This skill prevents that by requiring test results, build logs, and quality metrics before marking work complete, ensuring every deliverable is backed by documented proof aligned to production standards.

This skill defines tiered quality standards—minimum, production-grade, and gold-standard—so teams know what evidence is required at each level. Production-grade requires comprehensive test coverage, clean builds, and passing linters; the skill's templates clarify what each threshold demands.