openspec-verify-change

Verifying code changes against artifacts involves mapping implementation evidence to requirements and design decisions. This process ensures completeness, correctness, and coherence by checking task completion and spec coverage before archiving.

Change verification validates that an implementation matches corresponding change artifacts. It ensures completeness, correctness, and coherence by reviewing task completion, spec coverage, and code pattern consistency within software development workflows.

Yes, you need the openspec CLI for artifact retrieval and analysis. It provides the necessary change artifacts to validate that your implementation follows design decisions and maintains code pattern consistency.

To check spec coverage and task completion, select a specific change or infer it from context. The verification process maps requirements to implementation evidence, ensuring all tasks and specifications are fully covered.

Yes, during change verification you can review new code for consistency with project patterns. This ensures the implementation follows established design decisions and maintains coherence with existing software quality standards.

Automated artifact alignment relies on the openspec CLI for retrieval and analysis, meaning it requires properly structured change artifacts. It verifies coherence and design adherence but depends on accurate context inference for specific changes.