verification

Verify task completion against acceptance criteria with observable evidence.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Wilder1222/superomni --skill verification-wilder1222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/Wilder1222/superomni/tree/main/skills/verification
Command: npx skills add https://github.com/Wilder1222/superomni --skill verification-wilder1222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify task completion by enforcing acceptance criteria and providing verifiable evidence.

Core Features & Use Cases

  • Enforces a formal DONE gate before reporting task completion, requiring evidence and acceptance criteria to be satisfied.
  • Automates generation and organization of session artifacts for auditability and traceability.
  • Supports a structured session lifecycle with statuses (DONE, DONE_WITH_CONCERNS, BLOCKED, NEEDS_CONTEXT) and auto-advancement rules.

Quick Start

Use this skill at the end of a task to verify completion against acceptance criteria and generate observable evidence.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I verify task completion against acceptance criteria with verifiable evidence?

To verify task completion, you enforce a formal DONE gate requiring observable artifacts and logs. This ensures task completion is justified by verifiable evidence before reporting success in software delivery workflows.

What is a DONE gate in software delivery and when do I need verifiable evidence?

A DONE gate is a formal checkpoint ensuring task completion meets acceptance criteria. You need verifiable evidence like observable artifacts and logs to audit and justify task completion in software delivery workflows.

How do I generate session artifacts for quality assurance and traceability?

You generate session artifacts for quality assurance by automating their organization during the verification process. This requires a structured session and artifact storage to document verification outcomes and gate progress.

Can I use automated verification to track blocked tasks or tasks needing context?

Yes, automated verification supports a structured session lifecycle with statuses including BLOCKED and NEEDS_CONTEXT. It applies auto-advancement rules to manage task progress when acceptance criteria cannot be fully verified.

What is the best way to enforce quality assurance gates before reporting a task as done?

The best way to enforce quality assurance gates is by applying a formal verification process. This requires checking observable artifacts against acceptance criteria to ensure DONE is fully justified before reporting task completion.

Does verification work without structured session storage for documenting outcomes?

No, verification requires a structured session and artifact storage to function correctly. This environment is necessary to document verification outcomes, manage lifecycle statuses, and gate progress effectively.