openspec-verify-change

To verify code implementation against change specifications, you can audit the codebase by mapping implementations to defined tasks, specs, and design documents to flag missing requirements or deviations. This ensures code accurately reflects intended changes before archiving or merging work.

A code compliance audit checks for completeness by verifying task completion, correctness by mapping implementation to requirements, and coherence by evaluating design adherence and code pattern consistency. It generates a report with critical, warning, and suggestion issues.

Yes, you need openspec-cli installed to verify change artifacts. The verification process operates by invoking the openspec CLI to list, status, and apply change instructions before analyzing context files and the codebase for discrepancies.

You can check if code meets defined tasks and requirements by performing a completeness check that verifies all tasks are completed and all requirements from specs are addressed, alongside a correctness validation that assesses scenario coverage and requirement intent alignment.

The best way to assess design adherence and code pattern consistency is through a coherence assessment that evaluates the codebase against established design decisions. This identifies discrepancies and generates a detailed report flagging deviations.

Implementation verification reports show critical issues when the codebase analysis detects significant discrepancies between the actual code and the change artifacts. These critical issues indicate missing implementations or severe deviations from the defined specifications and tasks.