kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- kiro-verify-completion
- description
- Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
02 资源文件 1
- 参考文档agents/openai.yaml159 B
03 SKILL.md 正文
kiro-verify-completion
<background_information> This skill prevents false completion claims. A task, fix, or feature is only complete when supported by fresh evidence that matches the scope of the claim. </background_information>
<instructions>
When to Use
- Before saying a task is complete
- Before saying a bug is fixed
- Before saying tests pass
- Before moving to the next task in autonomous execution
- Before reporting
GOfrom feature-level validation - Before trusting another subagent's success report
Do not use this skill for early planning or speculative status updates.
Inputs
Provide:
- The exact claim to verify
- Claim type:
TASKFIXTEST_OR_BUILDFEATURE_GO
- Validation commands discovered by the controller
- Fresh command output and exit codes
- Relevant task IDs, requirement IDs, and design refs where applicable
- For feature-level claims:
- requirements coverage status
- design alignment status
- integration status
- blocked task status
Outputs
Return one of:
VERIFIEDNOT_VERIFIEDMANUAL_VERIFY_REQUIRED
Also return:
- Claim reviewed
- Evidence used
- Scope/evidence mismatch, if any
Use the language specified in spec.json.
Gate Function
- Identify the exact claim.
- Identify the exact command or checklist that proves that claim.
- Require fresh evidence from the current code state.
- Check exit code, failure count, skipped scope, and missing coverage.
- Reject claims that are broader than the evidence.
- If mandatory validation cannot be completed, return
MANUAL_VERIFY_REQUIRED. - Only then allow the claim.
Claim-Specific Rules
TASK
Require:
- task-local verification evidence
- no unresolved blocking findings from review
- evidence aligned with the task boundary
FIX
Require:
- evidence that the original symptom is resolved
- no broader regressions in the relevant verification scope
TEST_OR_BUILD
Require:
- actual command output
- exit code
- no inference from unrelated checks
FEATURE_GO
Require:
- full test suite result
- runtime smoke boot result showing the built artifact reaches its first usable state
- requirements coverage assessment
- cross-task integration assessment
- design end-to-end alignment assessment
- blocked tasks assessment
A passing test suite alone is not enough for FEATURE_GO.
Stop / Escalate
Return MANUAL_VERIFY_REQUIRED when:
- No canonical validation command is known
- The required environment is unavailable
- A mandatory manual verification step cannot be executed
Return NOT_VERIFIED when:
- The command failed
- Evidence is stale
- Evidence is partial
- The claim exceeds the evidence
- The feature still has unresolved blocked tasks or uncovered requirements
Common Rationalizations
| Rationalization | Reality |
|---|---|
| “The subagent said it succeeded” | Reported success is not verification evidence. |
| “Tests passed earlier” | Fresh evidence only. |
| “Build should be fine because lint passed” | Lint does not prove build success. |
| “Tests passed and build succeeded, so it must run” | Type erasure, module loading, native ABI, and boot-time config issues can still fail at runtime. |
| “The feature is done because all tasks are checked off” | FEATURE_GO also requires coverage, integration, and design alignment. |
Output Format
## Verification Result
- STATUS: VERIFIED | NOT_VERIFIED | MANUAL_VERIFY_REQUIRED
- CLAIM_TYPE: TASK | FIX | TEST_OR_BUILD | FEATURE_GO
- CLAIM: <exact claim>
- EVIDENCE: <command/checklist and result>
- GAPS: <scope/evidence mismatch or missing validation>
- NOTES: <next action if not verified>
</instructions>
04 同仓库更多 Skills
kiro-spec-init
暂无简介
kiro-spec-init
暂无简介
sb-verify-completion
Consequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.
sb-validate-implementation
Validate completed Tasks against active Requirement IDs and record completion on GO under an explicit lifecycle-validation request or ordinary Drive authority. Also owns completion withdrawal under an evidenced Drive replan recovery handoff. For a consequence-free claim check, use sb-verify-completion.
sb-validate-design
Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.
sb-steering
Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.