kiro-verify-completion

To verify completion claims, run canonical validation commands for your task, capture fresh outputs, and report the results to enforce a gate that prevents premature feature go decisions.

Evidence-driven verification links validation results to specific task IDs, requirements, and design references to avoid scope drift. It requires fresh outputs matching the claim scope before approving task, fix, test, or build completions.

Prevent false completion claims by enforcing a verification gate that demands canonical validation commands and fresh outputs. This ensures completion proof matches the actual task scope before any go decision is made.

Yes, verification supports both automated checks and manual review. When automation is insufficient for validating completion claims, manual review processes can enforce the gate using fresh evidence and scoped outputs.

You need fresh outputs for build quality verification whenever declaring task, fix, test, or feature completion. Requiring fresh evidence ensures the validation results directly match the claim scope and prevent premature approvals.