spec-verify

Dispatch an independent agent to verify code changes for completeness, correctness, and coherence.

9|Updated May 27, 2026
One-click install
npx skills add https://github.com/kamioj/spec-workflow --skill spec-verify-kamioj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-verify
Source: https://github.com/kamioj/spec-workflow/tree/main/codex/skills/spec-verify
Command: npx skills add https://github.com/kamioj/spec-workflow --skill spec-verify-kamioj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the quality of code changes by dispatching an independent agent to verify them across three dimensions plus a charter audit, updating a verification ledger for traceable findings.

Core Features & Use Cases

  • Independent Verification: Spawns an agent with a fresh context to avoid biases and ensure objectivity.
  • Three-Dimensional Framework: Checks Completeness, Correctness, and Coherence.
  • Charter Audit: Ensures changes adhere to explicit proposal decisions.
  • Verification Ledger: Records findings with stable IDs for traceability.

Quick Start

Run the spec-verify command to verify the current change.

Frequently Asked Questions about spec-verify

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

FAQPage Schema
How do I independently verify code changes for completeness and correctness?

Independent code verification dispatches a fresh-context agent to check changes across completeness, correctness, and coherence, ensuring alignment with design proposals while recording traceable findings in a verification ledger.

What is a charter audit in software review?

A charter audit ensures code changes adhere to explicit proposal decisions, verifying that implemented modifications align with agreed-upon specifications and design constraints for traceable software quality assurance.

How do I maintain a verification ledger for traceable code review findings?

A verification ledger records code review findings with stable IDs during independent spec verification, enabling traceability across completeness, correctness, and coherence checks for auditable change quality management.

Does independent spec verification eliminate reviewer bias?

Independent spec verification spawns an agent with a fresh context to avoid biases, ensuring objectivity when checking code changes for completeness, correctness, and coherence against proposal and design specifications.

When do I need independent specification checking for code changes?

Independent specification checking is needed when ensuring code change quality through objective completeness, correctness, and coherence validation, plus a charter audit to confirm alignment with explicit proposal decisions.

What's the best way to audit code changes against design specifications?

Auditing code changes against design specifications is best handled by dispatching an independent agent to verify completeness, correctness, and coherence while maintaining a verification ledger for traceable charter audit findings.