clavix-verify

Spec-driven code verification compares source code against defined requirements in tasks.md and full-prd.md to identify discrepancies. This auditing process checks implementation accuracy, completeness, and architectural adherence to prevent specification drift.

Spec-driven code auditing is a technical verification process that compares source code against defined requirements and architectural plans. You need this process after implementing a new feature to ensure all specified requirements are met before merging.

Perform a gap analysis against your specification documents to identify missing features and compliance issues. This audit compares actual source code implementation against tasks.md and full-prd.md, enforcing a mandatory fix-and-reverify loop for any identified architectural or behavioral discrepancies.

Yes, spec-driven verification works by comparing source code directly against existing specification documents rather than executing test suites. It performs a static technical audit of implementation completeness and architectural adherence without requiring you to author new automated tests.

Enforce a fix-and-reverify loop by running automated spec-driven audits that compare code against tasks.md and full-prd.md. The audit identifies compliance gaps and quality issues, requiring developers to resolve all discrepancies and re-run the verification until the implementation fully matches the specifications.

The limitation of this spec-driven auditing approach is its strict dependency on accurate, up-to-date specification documents. If your tasks.md or full-prd.md files are incomplete or outdated, the verification process cannot accurately identify implementation gaps or verify behavioral compliance.