openspec-verify-change

To verify changes match delta specifications, you can run an automated spec coverage check that compares codebase implementations against openspec requirements and outputs a structured report with critical issues and actionable recommendations.

Yes, you can automate task completion checks by comparing tasks.md entries and delta contexts against the actual codebase implementations to identify incomplete or missing task-level requirements before archiving.

Spec mapping for code review is the process of comparing delta requirements directly to code implementations, validating that every requirement is fully covered and generating a structured report highlighting critical warnings and suggestions.

Spec coverage verification supports optional design coherence and scenario coverage checks, automatically validating alignment when design documents and scenario artifacts exist within the openspec change context.

The best way to identify unimplemented delta requirements is to run an automated verification workflow that maps openspec delta specifications to code, outputting a structured report with critical, warning, and suggestion issues.

You need to verify change specifications before archiving to ensure that delta specs are fully implemented in the codebase and that artifacts such as tasks, specs, and design documents align correctly to prevent incomplete changes.