skills.rest
shimaMatz
shimaMatzCOMMUNITY
Explore all skills by this author →
GitHub

kiro-verify-completion

Verify completion claims against fresh command outputs and exit codes.

Updated Apr 5, 2026
Search Tags:#validation#qa#evidence#verify#claims#tests#go-decision
One-click install
npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-verify-completion-shimamatz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-verify-completion
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-verify-completion
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-verify-completion-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that claims about task completion, bug fixes, tests passing, or feature readiness are supported by fresh evidence, preventing premature GO decisions.

Core Features & Use Cases

  • Enforces evidence-backed verification for TASK, FIX, TEST_OR_BUILD, and FEATURE_GO claims.
  • Provides deterministic outputs VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED along with reviewed claims and supporting evidence.
  • Supports integration in autonomous execution workflows, enabling safe handoffs and auditability.

Quick Start

To begin, provide the exact claim you want to verify and initiate a fresh-evidence verification against the current code state.

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 before a GO decision?▼

You can verify completion claims by running commands that produce fresh outputs and exit codes against the current code state. The process checks accuracy and scope alignment, reporting VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED with supporting evidence.

What is evidence-backed verification for autonomous execution workflows?▼

Evidence-backed validation prevents premature GO decisions by requiring fresh command outputs to support claims about task completion, bug fixes, tests, or feature readiness. It ensures safe handoffs and auditability in autonomous execution workflows.

How do I validate bug fix readiness before reporting success in an autonomous workflow?▼

To validate a bug fix, provide the exact claim and run fresh-evidence verification against the current code state. The system checks for accuracy and scope alignment, returning a deterministic status of VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED.

Can I use this validation approach for feature readiness and test passing claims?▼

Yes, this validation enforces evidence-backed verification for TASK, FIX, TEST_OR_BUILD, and FEATURE_GO claims. It requires commands that produce fresh outputs and exit codes to confirm feature readiness or test results.

Does the verification process require any specific dependencies or components to run?▼

No specific dependencies or components are required. The verification process needs only the exact claim you want to verify and commands that produce fresh outputs and exit codes against the current code state.

When should I not use fresh-evidence verification for completion claims?▼

Fresh-evidence verification is not suitable when you lack commands that produce fresh outputs and exit codes. If a claim cannot be tested against the current code state for accuracy and scope alignment, manual verification is required.

Related Skills

Explore More Software Engineering Skills→
AlabamaMikeAlabamaMike

verification-before-completion

Run verification commands and confirm fresh outputs before declaring completion.

Community
Basic
BarryYinBarryYin

kiro-verify-completion

Verify completion claims using fresh command outputs and exit codes.

Community
Advanced
djwmobleydjwmobley

verification

Run verification commands and attach output evidence before declaring completion.

Community
Advanced
acho1833acho1833

requesting-code-review

Prepare code review requests with commit ranges and implementation summaries.

Community
Basic