kiro-verify-completion

Name: kiro-verify-completion
Availability: InStock
Author: taku-o

Verify task completion claims against fresh validation evidence and exit codes.

1|Updated Apr 15, 2026

Search Tags:#automation #build #evidence #quality-assurance #verify #claims #tests

Ready to run

npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-verify-completion-taku-o

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-verify-completion
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-verify-completion
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-verify-completion-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents false completion claims by requiring fresh evidence that matches the scope of the claim.

Core Features & Use Cases

Enforces evidence-backed verification before declaring a task, fix, test pass, or feature go.
Works across TASK, FIX, TEST_OR_BUILD, and FEATURE_GO claims to ensure alignment with scope.

Quick Start

Submit a precise claim and attach fresh validation evidence to obtain a VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED result.

Frequently Asked Questions about kiro-verify-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify task completion with fresh evidence in software projects?▼

Task completion verification requires submitting a precise claim alongside fresh validation outputs and exit codes. The process aligns evidence with scope to produce a VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED result.

What problem does evidence-backed verification solve for build and test claims?▼

Evidence-backed verification prevents false completion claims by requiring fresh outputs that match the scope of the claim. This ensures tasks, fixes, and feature go decisions are backed by actual validation results.

Can I use automation to verify fix and feature go claims across different scenarios?▼

Yes, automation can verify fix and feature go claims across TASK, FIX, TEST_OR_BUILD, and FEATURE_GO scenarios. You submit a precise claim with canonical validation commands to obtain a verification result.

What's the best way to prevent premature completion claims in quality assurance?▼

The best way to prevent premature completion is enforcing evidence-backed verification before declaring a task or test pass. This requires fresh outputs and exit codes aligned with the original scope.

When do I need manual verification instead of an automated verified result?▼

Manual verification is needed when submitted evidence is insufficient or scope alignment is ambiguous, yielding a MANUAL_VERIFY_REQUIRED result. This occurs when canonical validation commands cannot fully confirm the claim.