clavix-verify

Audit code implementations against tasks.md and full-prd.md specifications.

Updated Feb 5, 2026

Search Tags:#testing #quality assurance #code review #verification #compliance #auditing

Ready to run

npx skills add https://github.com/mbed92/phd --skill clavix-verify-mbed92

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clavix-verify
Source: https://github.com/mbed92/phd/tree/main/.skills/clavix-verify
Command: npx skills add https://github.com/mbed92/phd --skill clavix-verify-mbed92

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code implementations precisely match their intended requirements and architectural plans, preventing drift and ensuring quality.

Core Features & Use Cases

Spec-Driven Auditing: Compares code against tasks.md (architecture) and full-prd.md (behavior).
Gap Analysis: Identifies discrepancies in implementation, missing features, and quality issues.
Use Case: After a developer implements a new feature, use this Skill to verify that all specified requirements are met and that the code adheres to the planned architecture before merging.

Quick Start

Use the clavix-verify skill to audit the implementation in the current project directory.

Frequently Asked Questions about clavix-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify code implementation against product requirements and architectural plans?▼

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.

What is spec-driven code auditing and when do I need it?▼

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.

How do I audit source code for missing features and compliance gaps before a merge?▼

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.

Does spec-driven code verification work without writing additional test cases?▼

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.

What is the best way to enforce a fix-and-reverify loop for identified code compliance issues?▼

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.

What are the limitations of auditing code against tasks.md and full-prd.md 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.