spectra-verify

To automate code verification against design specifications, you can use a spec-driven development workflow that checks if your implementation matches change artifacts like specs and tasks. This ensures code integrity by validating alignment with intended designs automatically.

Spec-driven implementation review is the process of validating code changes against predefined change artifacts to ensure alignment with design specifications. You need it when managing complex code changes to verify that implementation matches the intended design and tasks.

Yes, you need the spectra CLI to verify implementation against change artifacts. The CLI is required for artifact retrieval and processing, enabling the automated verification of code changes against design and specification documents.

To verify a specific code change against its specifications, run the verification command with the target change name. This automatically checks if the implementation matches the change artifacts, ensuring code alignment with the intended design.

Yes, you can infer the change name from conversation context during implementation verification. The change management process supports checking for a specific change name or automatically inferring the target change from the surrounding context.

A key limitation of automated implementation verification is its strict dependency on the spectra CLI for artifact retrieval. Without the CLI installed and available, the verification process cannot execute or validate code against the design specifications.