kiro-verify-completion

Validates task, fix, test, and feature completion claims against fresh command evidence.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-verify-completion-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-verify-completion
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-verify-completion
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-verify-completion-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents false completion claims by requiring fresh, scoped evidence before any task, fix, test run, or feature is declared done, stopping premature GO decisions in autonomous workflows. ## Core Features & Use Cases - Claim-Type Gating: Classifies claims as TASK, FIX, TEST_OR_BUILD, or FEATURE_GO and applies claim-specific evidence requirements. - Fresh Evidence Enforcement: Requires current command output, exit codes, and coverage checks, rejecting stale or partial evidence. - Structured Verdicts: Returns VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED with documented gaps and next actions. - Use Case: Before reporting a feature as ready for release, run this gate to confirm the full test suite passed, the built artifact boots to a usable state, and requirements coverage and design alignment are complete. ## Quick Start Verify whether the claim that the login fix works is supported by fresh test output before marking the task complete.

Frequently Asked Questions about kiro-verify-completion

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

FAQPage Schema
Why do tests passing and build succeeding not prove a feature works?

Type erasure, module loading, native ABI issues, and boot-time configuration problems can still cause runtime failure. A runtime smoke boot of the built artifact is required to confirm it reaches its first usable state.