verify-integration

Requirement verification traces acceptance criteria through implementation artifacts and integration points to ensure complete coverage. It classifies gaps, tracks remediation, and validates tests before generating a compliance report for pull request review.

Requirement traceability maps acceptance criteria to specific implementation artifacts to verify each requirement has a corresponding solution. It is needed between implementation and review stages to prevent incomplete feature delivery and ensure all integration paths are validated.

Integration verification checks that components are wired together and functioning across end-to-end flows. It validates that integrated code artifacts are substantive, coordinates remediation for identified gaps, and produces a compliance score before approval.

Compliance gating classifies requirement gaps and coordinates remediation attempts before pull request review. It produces verification reports and applies compliance scoring to ensure incomplete features are blocked from reaching the approval stage.

Tracing specification requirements involves extracting acceptance criteria, mapping them to implementation artifacts, classifying integration gaps, and verifying test coverage. This process validates integration paths and generates a compliance score to gate approval.

Integration completeness checks validate that components are wired together and substantive across end-to-end flows, not just isolated functionality. Gap classification identifies missing requirement mappings and integration paths that local tests do not cover.