kiro-verify-completion

Verify completion claims by running prescribed validation commands, attaching fresh command outputs and exit codes, and evaluating current code state to return VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED with documented gaps.

Prevent false fix claims by requiring fresh, scope-aligned evidence for FIX claims. Validate the latest reproduction command outputs and exit codes to ensure teams and agents do not trust stale or secondhand success reports.

Validate autonomous agent handoff reports by applying the FEATURE_GO claim-to-checklist mapping. Require fresh coverage and integration status evidence to determine whether the feature readiness claim is actually supported.

Yes, the verification process supports TEST_OR_BUILD claims. It validates exit codes and command outputs during development workflows, returning clear outcomes with documented gaps and next actions to prevent premature success reports.

Expect a MANUAL_VERIFY_REQUIRED outcome when submitted evidence contains documented gaps. The verification process returns this status when fresh command outputs, exit codes, or runtime state evidence are insufficient to fully support the claim.

To verify a development task claim, you need prescribed validation commands, fresh command outputs, current exit codes, and current code or runtime state evidence to evaluate whether the completion or success claim is fully supported.