kiro-verify-completion

You prevent false completion claims by requiring fresh evidence that matches the claimed outcome before declaring a task, fix, or feature complete. This validation enforces a canonical command and checks fresh output and exit codes for alignment with the claim scope.

To verify task completion with fresh evidence, you provide a fresh verification command and capture its output and exit codes. The evidence must align with the scope of the completion claim to confirm the outcome is actually achieved.

Feature GO verification is the process of validating a feature release by enforcing evidence-backed checks before a GO decision. You need it across autonomous workflows to prevent premature success claims and ensure the claimed outcome is supported by fresh command output.

Yes, evidence-backed verification works for bug fixes and tests by requiring a canonical validation command and fresh output that matches the claim scope. It prevents unverified success claims across task completion, fixes, and tests in autonomous execution.

To verify a completion claim, you need a canonical validation command, the fresh command output, and the exit codes. These inputs are evaluated to ensure the evidence aligns with the specific scope of the claim before completion is declared.

Your autonomous workflow reports premature success because it lacks evidence-backed verification requiring fresh command output and exit codes. Without matching fresh evidence to the claimed outcome scope, false completion claims go unchecked and unverified.