openspec-verify-change

To verify implementation coherence against change specifications, you can use an automated validation process that checks tasks, specs, and design artifacts for completeness, correctness, and coherence before archiving. It evaluates requirement implementation, scenario coverage, and code pattern consistency.

The best way to validate code changes against design artifacts is by running an automated verification process that evaluates design adherence and spec coverage. It generates a summary scorecard and detailed issues by priority to ensure the implementation matches defined specifications.

Yes, you need the openspec CLI to check change management artifacts because the verification process requires openspec capabilities and JSON parsing to validate implementation completeness and interact with users to select changes.

Automated specification matching works by evaluating task completion, requirement implementation, and scenario coverage against provided change artifacts. It checks code pattern consistency and design adherence to report coherence issues categorized by CRITICAL, WARNING, or SUGGESTION priorities.

You need to run a coherence check on your system change implementation before archiving the changes for deployment. This ensures that the implementation aligns with the defined specifications, design, and tasks, preventing incomplete or incorrect updates from being archived.

Yes, you can select specific changes to verify if no name is provided because the verification process includes user interaction. It prompts you to select the specific change from the available options to begin the validation and reporting process.