openspec-verify-change

To verify implementation matches change artifacts, you need a tool that checks completeness, correctness, and coherence against your specs, tasks, and design files. This ensures your software change aligns with specified requirements before archiving.

Spec adherence verification checks requirement implementation, scenario coverage, task completion, and design pattern consistency. It assesses whether your implementation is complete, correct, and coherent with the defined change artifacts and design specifications.

Yes, you need the openspec CLI installed to run change verification reports. The verification process parses JSON outputs generated by the openspec CLI to produce a structured and detailed verification report.

You generate a verification report for completed tasks by running the verification process with an optional change name. It parses JSON outputs to assess task completion, spec coverage, and requirement implementation, creating a detailed structured report.

Yes, you can check design adherence and pattern consistency automatically by verifying coherence within your implementation. The process assesses whether your code follows the design artifacts and maintains consistent architectural patterns.

You should run a change verification check before archiving your software change. It ensures the implementation is complete, correct, and coherent with the specified change artifacts, preventing incomplete or inconsistent tasks from being archived.