verification

Verification aligns your implementation against a SPEC.md contract by running unit, integration, and end-to-end tests to catch deviations and edge cases before production. The skill enforces must-have checks and test coverage to ensure compliance with agreed requirements.

Specification-driven verification reduces bugs by treating SPEC.md as the authoritative contract and validating implementations against it systematically. Multi-level testing—unit, integration, and end-to-end—surfaces gaps between intent and code early.

Documentation and test alignment verification encourages clear test artifacts that support audits and future maintenance. Running verification against SPEC.md ensures tests document behavior and cover contractual requirements end to end.

Verification covers unit, integration, and end-to-end checks, so you can validate behavior across all levels. This multi-level approach catches edge cases and quality issues that single-layer testing might miss.

Before verification, ensure SPEC.md exists and clearly defines your contractual requirements. The verification workflow reads this specification as the source of truth, so alignment between your spec and codebase determines the quality of results.