sdd-verify

Spec compliance verification compares implementation behavior against SDD artifacts, requirements, and design decisions. It executes tests, analyzes coverage, and produces evidence-based quality gate reports with clear PASS or FAIL outcomes to prevent incomplete implementations.

Validate AI-assisted changes by auditing completed tasks, running relevant runtime tests, and checking design compliance. This produces a verification report documenting any compliance gaps or risks, ensuring the implementation matches the original specifications before acceptance.

Spec compliance checks require access to SDD artifacts, test runners, and project context. Providing these inputs allows the verification process to produce evidence-based quality gate decisions and accurately document any compliance gaps found during the audit.

Runtime quality gates execute tests and analyze coverage to produce verification reports. These reports yield evidence-based PASS or FAIL decisions by directly comparing runtime test evidence against the defined specifications, tasks, and design decisions.

An implementation fails spec compliance verification when its behavior does not match SDD artifacts, requirements, or design decisions. Runtime test execution only checks code execution, while compliance checks audit completed tasks and document gaps against the full specification.

Yes, you can document compliance gaps in spec-driven development workflows by comparing implementation behavior against specifications and runtime evidence. The process produces verification reports that highlight any incomplete tasks, compliance risks, or deviations from the design.