verify

Name: verify
Availability: InStock
Author: KOHLEX

Collect end-to-end acceptance evidence and write VERIFICATION.md with a merge verdict.

Updated Jun 4, 2026

Search Tags:#automation #qa #verification #evidence #end-to-end #archiving #acceptance-criteria

Ready to run

npx skills add https://github.com/Kohlex/autopilot-plugin --skill verify-kohlex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/verify
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill verify-kohlex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end acceptance criteria often live in SPEC.md and PLAN.md, but there is no single auditable artifact. This skill automates gathering public-surface evidence and writes VERIFICATION.md for archival at merge time.

Core Features & Use Cases

End-to-end verification orchestration: collects evidence from HTTP routes, CLI commands, Tauri invokes, library exports, event buses, workflows, and background jobs, consolidating it into VERIFICATION.md.
Architecture-aligned audit: enforces the VERIFICATION.md schema and supports inputs like ARCHITECTURE.md lock_hash, SPEC.md breadcrumbs, and integration breadcrumbs for traceability.
Audit-ready verdicts: computes per-AC evidence and a gate-rollup verdict, enabling READY-TO-MERGE, NEEDS-WORK, or BLOCKED statuses.

Quick Start

Run the verify skill in the capability worktree to generate VERIFICATION.md and attach evidence.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I automate end-to-end acceptance criteria evidence collection for merge readiness?▼

Automate end-to-end acceptance criteria evidence collection by orchestrating checks across HTTP routes, CLI commands, library exports, and event buses, consolidating results into a VERIFICATION.md file for governance. This process computes a gate rollup to produce a READY-TO-MERGE or BLOCKED verdict.

What is a VERIFICATION.md schema and how does it support architecture audit traceability?▼

A VERIFICATION.md schema is an auditable artifact format that aligns end-to-end verification evidence with ARCHITECTURE.md lock hashes and SPEC.md breadcrumbs. It ensures traceability by mapping acceptance criteria directly to verified public-surface interactions like Tauri invokes and background jobs.

Do I need SPEC.md breadcrumbs and an ARCHITECTURE.md lock to generate end-to-end verification evidence?▼

Yes, SPEC.md breadcrumbs, PLAN.md tasks, and an approved ARCHITECTURE.md lock are required prerequisites to generate end-to-end verification evidence. These inputs ensure collected HTTP route and CLI evidence accurately traces back to approved capability designs.

How do I compute a gate rollup verdict for capability acceptance criteria?▼

Compute a gate rollup verdict by aggregating in-fence verification gates from evidence gathered across public surfaces like HTTP routes and event buses. This cross-tool orchestration evaluates per-acceptance-criteria evidence to output a final READY-TO-MERGE, NEEDS-WORK, or BLOCKED status.

Can I collect verification evidence from Tauri invokes and background jobs for archival?▼

Yes, you can collect verification evidence from Tauri invokes, background jobs, event buses, and library exports for archival. The orchestration consolidates this multi-surface evidence into VERIFICATION.md to prove end-to-end capability readiness at merge time.