kiro-verify-completion

Validate task completion claims using evidence from the current code state.

8|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/gaebalai/k-sdd --skill kiro-verify-completion-gaebalai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-verify-completion
Source: https://github.com/gaebalai/k-sdd/tree/main/tools/k-sdd/templates/agents/claude-code-skills/skills/kiro-verify-completion
Command: npx skills add https://github.com/gaebalai/k-sdd --skill kiro-verify-completion-gaebalai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill verifies that tasks, fixes, tests, or features are actually complete or successfully implemented by providing fresh evidence.

Core Features & Use Cases

  • Claim Verification: Validate completion and success claims with specific evidence.
  • Prevent False Claims: Identify false completions before reporting, saving time and resources.
  • Task-specific Evidence: Gather and verify evidence tailored to different task types.

Quick Start

Verify a task claim by using the 'kiro-verify-completion' skill with the claim type and exact claim.

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 claims with evidence from the current code state?

To verify task completion, you validate claims by gathering fresh evidence directly from the current code state. This ensures that no broader claims of fixes or feature readiness are accepted without supporting evidence.

What is the best way to prevent false completion claims in multi-step development tasks?

Preventing false completion claims requires applying claim-specific rules during evidence gathering. This validates that complex multi-step tasks are actually complete by checking the code state before reporting success.

How do you validate feature readiness using automated checks?

Validating feature readiness involves applying automated validation rules against the current code state. If automated checks fail, the system escalates the task for manual verification to ensure evidence supports the claim.

Can I use task-specific evidence gathering for different types of code fixes?

Yes, you can gather and verify task-specific evidence tailored to different claim types. This ensures that each fix or feature is validated against rules specific to its requirements before completion is confirmed.

When should I not use automated validation for task verification?

Automated validation should not be used alone when complex multi-step tasks require nuanced verification. In these cases, the system escalates to manual verification to ensure evidence accurately supports the completion claims.