openspec-verify-change

You can verify implementation against change artifacts by parsing specifications, tasks, and design documents to assess completeness, correctness, and coherence. This maps requirements to code and scenarios to highlight critical issues and warnings before merging changes.

Spec compliance ensures code implementations accurately reflect defined specifications, tasks, and design documents. By checking task and spec coverage, it prevents drift and ensures quality before archiving changes.

Checking design adherence before merging involves evaluating code pattern consistency and coherence against project design documents. It generates a detailed report highlighting critical, warning, and suggestion-level issues based on evidence of implementation.

Automated code review checks task and spec coverage for new features by analyzing the codebase for evidence of implementation. It verifies that all requirements are met and all tasks are completed before archiving changes.

TDD quality assurance can map requirements to code scenarios by parsing openspec artifacts and analyzing the codebase. It assesses correctness by ensuring defined scenarios align with the actual code implementation.

Automated spec compliance verification operates by parsing openspec artifacts and analyzing code for implementation evidence. It is limited to evaluating completeness, correctness, and coherence based on the provided specifications, tasks, and design documents.