omk-verification

Execute verification commands and report success only when evidence passes.

103|15|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/KaimingWan/oh-my-kiro --skill omk-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omk-verification
Source: https://github.com/KaimingWan/oh-my-kiro/tree/main/skills/omk-verification
Command: npx skills add https://github.com/KaimingWan/oh-my-kiro --skill omk-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence before completion is frequently missing, leading to dishonest or unsafe claims. This Skill enforces fresh verification before any success statement to ensure integrity.

Core Features & Use Cases

  • Verifies claims by executing dedicated verification steps prior to marking work as done.
  • Applies to AI-assisted coding, PR reviews, and task state transitions to block premature completion.
  • Supports customizable verification commands and evidence collection to reduce hallucination and drift.

Quick Start

Run a fresh verification command before marking a task as complete.

Frequently Asked Questions about omk-verification

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

FAQPage Schema
How do I prevent AI-assisted coding from claiming task completion without verification?

To prevent unverified success statements in AI-assisted coding, you need evidence-first verification before completion. This gates the final task status by executing full verification commands and parsing outputs to ensure claims are backed by fresh evidence.

What is evidence-first verification in software engineering quality assurance?

Evidence-first verification in quality assurance is the process of executing dedicated verification steps prior to marking work as done. It gates completion claims by running commands and parsing outputs, ensuring AI systems only report success when verification passes.

How do I block premature task state transitions and PR reviews with guardrails?

To block premature task state transitions and PR reviews, implement guardrails that enforce fresh verification before completion. This automates evidence collection by executing verification commands and gating the final status until outputs pass validation.

Can I use customizable verification commands for AI system claims validation?

Yes, you can use customizable verification commands for AI system claims validation. This reduces hallucination and drift by executing your specified commands, parsing the outputs, and only reporting success when the fresh evidence passes verification.

What is the best way to automate quality assurance before marking a task board complete?

The best way to automate quality assurance before marking a task board complete is to gate the final status with automated verification. This approach executes full verification commands and parses outputs to block premature completion claims.

Why does my AI workflow report success before verification commands finish?

AI workflows report success prematurely because evidence before completion is frequently missing. To fix this, enforce fresh verification by automating dedicated verification steps that gate the final status until command outputs are parsed and validated.