openspec-verify-change

To verify code changes match design specs before archiving, you validate delta spec requirements, code references, and design decisions to assess completeness, correctness, and coherence. This ensures your implementation aligns with its artifacts for release readiness.

A structured verification report for software change packages highlights critical, warning, and suggestion issues with actionable recommendations. It assesses task completion, spec coverage, and scenario handling to ensure implementation correctness before archival.

Yes, you need the openspec CLI and repository context to validate change implementations. The tool requires access to delta specs, code references, and design decisions to generate a structured verification report.

You check delta spec requirements by running a verification workflow that assesses task completion, spec coverage, and scenario handling. It evaluates whether the codebase aligns with intended design decisions and produces a structured report.

Yes, you can use this verification tool to assess task completion and spec coverage. It applies to delta specs with requirements and scenarios to evaluate implementation completeness, producing a structured report with critical issues and actionable recommendations.

The best way to prepare change packages for archival is to run a verification workflow that identifies and confirms implementation matches with specs, tasks, and design artifacts. This validates completeness and produces a structured verification report.