Collect end-to-end acceptance evidence and write VERIFICATION.md with a merge verdict.
npx skills add https://github.com/Kohlex/autopilot-plugin --skill verify-kohlex
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
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.
Run the verify skill in the capability worktree to generate VERIFICATION.md and attach evidence.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
KohlexSpawn three parallel subagents to propose architecture extensions and append them to ARCHITECTURE.md.
s3nex-comCoordinate pull request lifecycle from review through merge with mandatory gates.
KohlexWire new capabilities into public surfaces after unit tests complete.
frydaiiiRun report-only QA tests on web applications and generate structured evidence reports.
