openspec-verify-change

You validate change implementations by automating the comparison of completed work against specs, tasks, and design documents to ensure completeness, correctness, and consistency before archiving.

Automated change validation is the process of checking task completion, spec coverage, design decisions, and pattern consistency to verify that change outputs align with requirements before archiving.

You can check task completion automatically by reading tasks.md and tallying checked boxes to verify that all required implementation tasks have been finished before archiving.

Yes, change management validation works without external dependencies by applying its internal validation workflow to read your existing specs, tasks, and design artifacts to produce a structured report.

The best way to verify design decisions match implemented changes is to automate a comparison workflow that checks design artifacts against actual outputs and generates a structured validation report identifying gaps.

You need to run a change validation report when preparing software changes for archiving, ensuring that task completion, spec coverage, and design consistency have all been verified.