verification

Verifies completion claims by executing and inspecting evidence before sign-off.

6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kok1eee/o-m-cc --skill verification-kok1eee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/kok1eee/o-m-cc/tree/main/skills/verification
Command: npx skills add https://github.com/kok1eee/o-m-cc --skill verification-kok1eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before declaring completion, it's essential to collect and verify concrete evidence to avoid false success claims.

Core Features & Use Cases

  • Adversarial verification posture: actively attempt to break changes, test edge cases, and validate robustness.
  • Iron Law enforcement: require executing verification commands and inspecting outputs before declaring completion.
  • Structured workflow: follow the IDENTIFY, RUN, READ, VERIFY, DECLARE steps to systematically confirm results and produce traceable evidence.
  • Use cases: applies to bug fixes, feature implementations, and refactors where validated results are required before sign-off.

Quick Start

Run the verification workflow to collect and confirm evidence before declaring completion.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I prove a bug fix is complete with verifiable evidence?

To prove a bug fix is complete with verifiable evidence, execute the IDENTIFY, RUN, READ, VERIFY, DECLARE workflow to collect concrete artifacts and prevent premature success claims.

What is adversarial testing in software verification?

Adversarial testing in software verification is the practice of actively attempting to break changes and test edge cases to validate robustness before declaring task completion.

How to prevent false success claims before declaring task completion?

Prevent false success claims by enforcing an Iron Law that requires executing verification commands, inspecting outputs, and validating artifacts before any sign-off declaration.

Does this verification process work for feature implementations and refactors?

Yes, this verification process works for feature implementations and refactors, applying structured evidence collection and artifact validation to ensure validated results before sign-off.

What are the limitations of declaring completion without explicit evidence collection?

Declaring completion without explicit evidence collection leads to false success claims and unverified assumptions, bypassing the required adversarial testing and artifact validation guardrails.