verify

Automate acceptance criteria verification with fresh evidence and PASS/FAIL reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/o3-ozono/atdd-kit --skill verify-o3-ozono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/o3-ozono/atdd-kit/tree/main/skills/verify
Command: npx skills add https://github.com/o3-ozono/atdd-kit --skill verify-o3-ozono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifications in software workflows often rely on memory or vague assurances. This skill ensures that every acceptance criterion is backed by fresh, verifiable evidence before a claim of completion is made.

Core Features & Use Cases

  • Guarded verification: Enforces gating rules (in-progress label checks, branch validation) before proceeding to verification.
  • Spec vs Issue divergence handling: Resolves authoritative sources between specification documents and issue comments, with clear rules for tiebreaks.
  • Autopilot-driven flow: Coordinates verification steps and reports a final status ready for shipping when all ACs pass.
  • Evidence-driven reporting: Produces explicit PASS/FAIL results with command output as evidence for each acceptance criterion.

Quick Start

Run the verify skill in autopilot mode on an issue that has in-progress work to begin the verification flow.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate acceptance criteria verification with fresh evidence before claiming completion?

Acceptance criteria verification is automated by collecting fresh command output evidence before marking an issue complete. This ensures every criterion is backed by verifiable data, producing explicit PASS or FAIL results for shipping readiness.

What is spec versus issue divergence handling in issue-driven development?

Spec versus issue divergence handling resolves authoritative source conflicts between specification documents and issue comments. It applies clear tiebreaker rules to determine which source governs acceptance criteria verification before proceeding with tests.

How do I enforce in-progress label checks and branch validation for release gating?

Release gating is enforced through session guards that check in-progress labels and validate branches before verification begins. This prevents premature completion claims by blocking the autopilot flow until gating rules pass.

Can I run E2E and unit verification in autopilot mode for issue-driven workflows?

E2E and unit verification can run in autopilot mode within issue-driven workflows. The autopilot flow coordinates verification steps across both test scopes and reports a final skill-status ready for shipping when all acceptance criteria pass.

What are the limitations when specification documents and issue comments conflict during verification?

When specification documents and issue comments conflict during verification, the limitation is relying on manual interpretation. The skill mitigates this by applying explicit divergence handling rules with structured tiebreakers to resolve the authoritative source automatically.