verifier

To verify code implementation against acceptance criteria, you need to collect demonstrable evidence such as test results and logs. This process enforces a hard stop before merge by ensuring every criterion has proof of satisfaction.

Spec compliance verification in CI/CD pipelines is a gatekeeping mechanism that prevents regressions by matching code implementations precisely against defined criteria. It integrates with the Spec Graph to mark components as Done only after successful verification.

To enforce a hard stop for test failures and coverage gaps during code review, you implement verification checks that block merges. This ensures sensitive data handling and coverage requirements are met before deployment proceeds.

Yes, the verifier skill operates without external dependencies. It uses internal references to guide evidence collection and updates the Spec Graph directly to mark components as Done based on verifiable proof.

To collect evidence for quality assurance and spec compliance, you gather test results, logs, and metrics as proof. This collected evidence demonstrates that the implementation satisfies all defined acceptance criteria before merge.