openspec-verify-change

To verify implementation matches specifications, you map code changes against defined tasks, requirements, and design documents. This process assesses completeness by checking task status and correctness by validating that requirements and scenarios are fully covered.

Checking requirement coverage and task status ensures development completeness. You verify that all defined tasks are marked complete and that every specified requirement is addressed by the implementation before archiving the changes.

Validating code coherence involves evaluating design adherence and checking code pattern consistency. You assess whether the implementation follows established architectural guidelines and aligns with project-specific design decisions.

You can verify implementations with incomplete artifacts because the system gracefully degrades checks based on available specifications, tasks, and designs. It dynamically prompts for changes if not specified, ensuring partial validation.

Yes, you need the openspec-cli installed to execute change verification checks. This command-line dependency provides the foundational scripts and references required to parse artifacts and assess implementation correctness.

You should run implementation verification after developing a new feature based on a spec and before archiving. This prevents code drift by ensuring user stories are implemented, architectural guidelines are followed, and test scenarios are covered.