openspec-verify-change

To verify implementation against delta specs, the Skill parses change artifacts like tasks.md and design.md, searches the codebase for evidence, and outputs a structured verification report with prioritized issues and recommendations.

Change artifact validation detects incomplete tasks, missing requirements, and design or implementation divergences by comparing codebase evidence against managed change specs and task lists before release or archiving.

You generate a structured verification report by selecting an openspec change interactively, loading its context files, and parsing artifacts to produce a completeness, correctness, and coherence scorecard with actionable recommendations.

Yes, you need the openspec CLI to list and load change context files, parse artifacts, and search the codebase for implementation evidence during the verification process.

You can automate code review by applying this verification to feature branches, which validates that delta specs and task checklists are fully implemented before archiving or release.

Automated spec validation requires managed change artifacts like delta specs and task lists to exist, and it relies on the openspec CLI to load context files, meaning unmanaged or undocumented changes cannot be validated.