kiro-verify-completion

To verify task completion, you must enforce fresh, scope-aligned evidence by running exact validation commands and checking exit codes. This prevents premature progression by returning a VERIFIED status only when fresh outputs match the claim scope.

Evidence-based validation for bug fixes requires capturing fresh command outputs and exit codes to prove the fix works. It enforces mandatory validation steps, ensuring feature-go readiness is backed by fresh evidence directly matching the claimed scope.

Completion verification for autonomous agents intercepts done claims and mandates fresh evidence generation. It validates exact commands and coverage, returning NOT_VERIFIED or MANUAL_VERIFY_REQUIRED if the evidence is stale or misaligned with the claim scope.

Yes, you can use automated validation to check test and build readiness by enforcing exact validation commands and capturing fresh outputs. It assesses evidence against the claim scope, returning VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED.

Your task validation returns MANUAL_VERIFY_REQUIRED when the mandated validation steps yield ambiguous fresh evidence. This status occurs during completion verification when scope-aligned evidence is insufficient to definitively return VERIFIED or NOT_VERIFIED.

The best way to enforce quality assurance for feature-go readiness is to mandate fresh evidence collection through exact validation commands. This verification process checks exit codes and coverage to ensure claims are backed by scope-aligned proof.