cverify

Audits spec-to-code conformance and generates a formal verification report with drift debt.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill cverify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cverify
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cverify
Command: npx skills add https://github.com/joshft/correctless --skill cverify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that implementations conform to the specification by auditing rule coverage, detecting undocumented dependencies, and assessing architecture compliance.

Core Features & Use Cases

  • Verifies spec-to-code conformance by cross-checking rules, dependencies, and architecture against the implemented artifact.
  • Generates a formal verification report and drift debt entries to document gaps and remediation priorities.
  • Integrates with existing QA artifacts and workflow state to guide TDD, verification, and release decisions.

Quick Start

Run /cverify after /ctdd completes to generate the verification report and drift debt for the current skill.

Frequently Asked Questions about cverify

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

FAQPage Schema
How do I verify spec-to-code conformance for my software architecture?

Spec-to-code conformance checks cross-reference implementation rules, dependencies, and architecture against the artifact. This produces a formal verification report and drift debt entries documenting gaps and remediation priorities.

What is drift debt in quality assurance and how is it tracked?

Drift debt entries document gaps between implementation and specification, capturing remediation priorities. They are generated by auditing rule coverage, dependency usage, and architecture compliance against the implemented artifact.

How do I audit dependency usage and rule coverage against a specification?

Apply a verification workflow across the full lifecycle to audit dependency usage and rule coverage. This enforces deterministic checks, collects artifacts, and generates calibration data to confirm implementation conformance.

Does architecture compliance verification integrate with existing QA artifacts?

Yes, verification integrates with existing QA artifacts and workflow state to guide TDD, verification, and release decisions. It produces a formal verification report and drift debt entries documenting gaps.

How do I generate calibration data for downstream release decisions?

Generate calibration data by enforcing deterministic checks and collecting artifacts during the verification lifecycle. This calibration data supports downstream decision making for release readiness and architecture compliance.

When do I need formal verification reporting for test-driven development?

You need formal verification reporting after the TDD cycle completes to confirm spec-to-code conformance. The report captures drift debt and integrates with QA artifacts to guide release decisions.