openspec-verify-change

To verify code implementation against change specifications, you can use this Skill to assess completeness, correctness, and coherence by analyzing task status, requirement coverage, scenario implementation, and design adherence. It requires the openspec CLI to run.

To check if all defined tasks in a specification are completed, this Skill performs a completeness check that verifies all defined tasks are finished and all requirements are addressed before archiving or merging changes.

No, openspec-verify-change does not work without the openspec CLI installed. The Skill requires the openspec CLI as a dependency to analyze change artifacts and validate implementation correctness.

The best way to validate feature implementation before merging is to verify implementation aligns with intent of requirements, covers defined scenarios, and adheres to design decisions. This Skill automates that coherence review against project coding patterns.

Yes, you can infer the change name automatically when verifying implementation. The Skill can infer the change name from conversation context or will prompt you to specify it if the target change is ambiguous.

Implementation drift occurs when code changes do not accurately reflect intended changes defined in specifications and design documents. It is prevented by validating implementation accuracy against change artifacts before archiving to ensure quality and consistency.