openspec-verify-change

Verifying code changes against OpenSpec specifications involves loading change artifacts and evaluating their completeness and correctness. The process generates a structured verification report with clear issue taxonomy and actionable recommendations to close gaps before archiving.

Validating delta specifications requires a verification workflow that discovers artifacts, checks their status, and confirms they map to code changes. This structured process surfaces any missing mappings and provides clear recommendations for remediation.

Generating a structured verification report for OpenSpec change workflows requires providing a change name to the verification process. It evaluates implementation completeness and correctness, outputting a report with a clear issue taxonomy and remediation recommendations.

Yes, the OpenSpec verification process checks design artifacts and task statuses by loading all associated change artifacts. It enforces a disciplined process including artifact discovery and status checks to ensure the implementation matches the design.

When implementation does not match specs or tasks, the verification report provides actionable recommendations to close gaps. You can use this issue taxonomy to identify missing delta specifications and remediate the discrepancies before archiving.