kiro-verify-completion

To verify task completion claims, you validate the exact claim against current code state and fresh command outputs, including exit codes. This prevents false success reports by ensuring scope alignment before progression.

Automated claim validation checks whether a bug is fixed or tests pass by enforcing strict verification against fresh outputs. It provides audit-ready evidence to prevent premature GO decisions during autonomous execution.

You prevent false success reports by requiring exact claim matching, validating commands, and fresh outputs before confirming completion. This strict verification stops premature progression on tasks, fixes, or feature GO claims.

Yes, you can validate a FEATURE_GO claim by running exact validation commands and checking fresh outputs with exit codes. This confirms scope alignment and provides audit-ready evidence before allowing progression.

You need the exact completion claim, the specific validating command, and fresh outputs including exit codes. Providing these inputs allows the verification process to confirm scope alignment and generate audit-ready evidence.

Completion verification fails when the exact claim lacks scope alignment with fresh command outputs. Without validating current code state and proper exit codes, strict verification prevents premature confirmation to avoid false success reports.