kiro-verify-completion

Verify completion claims with fresh evidence across development workflows.

Updated Feb 25, 2024
One-click install
npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-verify-completion-ryowatanabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-verify-completion
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-verify-completion
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-verify-completion-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents premature completion signals by requiring fresh, evidence-backed verification before declaring a task, fix, test, or feature as complete.

Core Features & Use Cases

  • Enforces evidence-based verification for TASK, FIX, TEST_OR_BUILD, and FEATURE_GO claims.
  • Guides teams to collect exact validation commands and fresh outputs, ensuring claims match the scope.
  • Useful in autonomous workflows, code reviews, and product readiness checks to avoid false positives.

Quick Start

Provide the exact claim and the corresponding claim type to trigger fresh verification and evidence gathering.

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 fresh evidence in automated workflows?

Verify completion claims by triggering fresh evidence gathering based on the exact claim and claim type. This skill enforces mandatory validation steps across development and QA workflows to prevent premature completion signals and guard against false positives.

What is evidence-based verification for feature readiness checks?

Evidence-based verification for feature readiness requires fresh validation outputs before approving a GO decision. This process guards against untested features by enforcing mandatory validation steps and returning VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUESTED statuses with accompanying evidence.

How do I prevent premature completion signals in code review and QA workflows?

Prevent premature completion signals by enforcing evidence-based verification for TASK, FIX, TEST_OR_BUILD, and FEATURE_GO claims. This requires teams to collect exact validation commands and fresh outputs, ensuring claims match scope before any task is declared complete.

Does this verification skill support automated validation for fix claims and test builds?

Yes, this verification skill supports automated validation for fix claims and test builds through the TEST_OR_BUILD and FIX claim types. It requires fresh evidence-backed validation and returns VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUESTED statuses with accompanying evidence.

When should I request manual verification instead of automated completion validation?

Request manual verification when automated validation cannot fully confirm a completion claim, returning a MANUAL_VERIFY_REQUESTED status. This occurs when fresh evidence is insufficient or ambiguous, requiring human review before declaring a task, fix, or feature as complete.