openspec-verify-change

To verify implementation matches change specs before archiving, you need to parse delta specs, map requirements to code changes, and run status checks to ensure task completion and spec coverage. This process generates a structured verification report with actionable recommendations.

Delta spec parsing is the process of reading change artifacts to map defined requirements directly to code changes. It validates code changes by checking task completion, spec coverage, and design coherence against the generated openspec workflow artifacts.

You can check task completion and spec coverage for openspec artifacts by loading the generated artifacts from the workflow and running a verification process. This guides you through status checks to ensure design coherence before archiving the changes.

Yes, openspec verification works without external dependencies, but it requires a delta specs directory and artifacts generated by the openspec workflow. It applies specifically to changes where these prerequisite artifacts exist to ensure completeness before archiving.

The best way to ensure design coherence before archiving code changes is to run a structured verification process that validates the implementation against change artifacts. This confirms that task and spec coverage requirements are fully satisfied and produces a coherent report.

Spec verification fails when artifacts are missing because the process requires a delta specs directory and artifacts generated by the openspec workflow to function. Without these inputs, it cannot parse delta specs or map requirements to validate implementation completeness.