verification

Automate task completion verification by collecting fresh evidence after each TODO.

4|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill verification-agmo-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/verification
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill verification-agmo-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification is often overlooked or rushed, leading to unverified completions. This skill ensures every completion is backed by fresh evidence before claims are made, reducing rework and mistrust.

Core Features & Use Cases

  • Enforces a formal verification sequence (IDENTIFY, RUN, READ, VERIFY, CLAIM) after each TODO.
  • Dispatches verification tasks to the architect agent and optional Codex cross-check when available.
  • Records and curates evidence to support each completion, enabling traceability across sessions.

Quick Start

Provide fresh verification evidence for each completed TODO by running the prescribed checks and recording the results.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I verify task completions with fresh evidence before making claims?

To verify task completions with fresh evidence, run prescribed checks after each TODO and record the results. This enforces a structured IDENTIFY, RUN, READ, VERIFY, CLAIM sequence to ensure every claim is backed by verifiable results.

What is the formal sequence for collecting verification evidence during a build?

The formal verification sequence for collecting evidence is IDENTIFY, RUN, READ, VERIFY, and CLAIM. It applies after each TODO in the execute workflow to automate the verification of task completions and reduce rework.

How do I automate claim verification and traceability across build sessions?

Automate claim verification and traceability by dispatching verification tasks to the architect agent and recording curated evidence. This supports each completion with verifiable results across multiple sessions.

Can I use an architect agent for cross-checking TODO verifications?

Yes, you can use an architect agent for cross-checking TODO verifications. The system dispatches verification tasks to the architect agent and applies an optional Codex cross-check when available.

Why does my verification workflow lead to unverified completions and rework?

Verification workflows lead to unverified completions when the process is rushed or overlooked. Enforcing a structured evidence collection sequence after each TODO ensures every completion is backed by fresh results, reducing mistrust.

What's the best way to structure tests and evidence collection for TODO verification?

The best way to structure tests and evidence for TODO verification is applying the IDENTIFY, RUN, READ, VERIFY, CLAIM sequence. This delegates tasks to specialized agents and records curated evidence to support each completion.