kiro-verify-completion

Solid

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.

AI & Automation 3,416 stars 254 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 `GO` from 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: - `TASK` - `FIX` - `TEST_OR_BUILD` - `FEATURE_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: - `VERIFIED` - `NOT_VERIFIED` - `MANUAL_VERIFY_REQUIRED` Also return: - Claim reviewed - Evidence used - Scope/evidence mismatch, if any Use the language specified in `spec.json`. ## Gate Function 1. Identify the exact claim. 2. Identify the exact command or checklist that proves that claim. 3. Require fresh evidence from the current code state. 4. Check exit code, failure count, skipped scope, and missing coverage. 5. Reject claims that are broader tha...

Details

Author
gotalab
Repository
gotalab/cc-sdd
Created
10 months ago
Last Updated
1 weeks ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

verify

Enforce evidence-based completion claims — require fresh command output before reporting success. Use when completing any task, fixing a bug, finishing a phase, running tests, building, deploying, or making any "it works" claim.

1,222 Updated today
codeaholicguy
AI & Automation Listed

verification-before-completion

Use when about to claim work is complete, before committing or creating PRs - requires fresh verification evidence before any completion claim. Triggers on phrases like "done", "finished", "ready to commit", "all tests pass", "looks good", "should work", "I think that's it".

15 Updated 5 days ago
backspace-shmackspace
Code & Development Listed

verification-before-completion

Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.

4 Updated today
izyanrajwani
Code & Development Solid

verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

233 Updated today
jamditis
AI & Automation Featured

verification-before-completion

Claiming work is complete without verification is dishonesty, not efficiency. Use when ANY variation of success/completion claims, ANY expression of satisfaction, or ANY positive statement about work state.

39,227 Updated today
sickn33