team-verify

Name: team-verify
Availability: InStock
Author: izmailovilya

Coordinate CI, browser, and spec verifiers against VERIFICATION_PLAN.md.

41|10|Updated Jan 21, 2026

Search Tags:#automation #verification #agents #orchestration #reporting #quality-assurance #ci

Ready to run

npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill team-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-verify
Source: https://github.com/izmailovilya/ilia-izmailov-plugins/tree/main/plugins/agent-teams/skills/team-verify
Command: npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill team-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end feature verification by coordinating CI, browser, and spec verifiers against a VERIFICATION_PLAN.md to ensure a feature meets acceptance criteria before release.

Core Features & Use Cases

Orchestrates CI-verifier, browser-verifier, and spec-verifier agents in parallel for fast, comprehensive checks against VERIFICATION_PLAN.md.
Generates a progressive verification report with clear status, evidence, and human-check gates.
Provides a structured workflow for teams to gate feature completion based on automated verification results.

Quick Start

Run the verification with a VERIFICATION_PLAN.md path, e.g., /team-verify path/to/VERIFICATION_PLAN.md

Frequently Asked Questions about team-verify

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

FAQPage Schema

How do I automate feature verification across CI, browser, and spec checks before release?▼

Automated feature verification coordinates CI, browser, and spec verifier agents in parallel against a VERIFICATION_PLAN.md to ensure features meet acceptance criteria before release. It generates evidence-rich reports and gates completion based on automated verification results.

What is a VERIFICATION_PLAN.md and how is it used for end-to-end feature validation?▼

A VERIFICATION_PLAN.md serves as the structured input for orchestrating end-to-end feature verification. It defines acceptance criteria that CI, browser, and spec verifier agents check against, producing a progressive verification report with clear status and evidence.

How do I run parallel verification agents against my feature verification plan?▼

Run parallel verification agents by executing the verification command with a path to your VERIFICATION_PLAN.md file. The orchestration coordinates CI, browser, and spec verifiers simultaneously to deliver fast, comprehensive checks and structured reports.

Can I gate feature completion based on automated verification results?▼

Yes, feature completion gating uses automated verification results from the coordinated CI, browser, and spec checks. The workflow provides a structured protocol with an integrity manifest and progressive disclosure to gate releases effectively.

Does automated feature verification handle human checks when automation cannot verify criteria?▼

Automated feature verification includes human-check gates within its progressive report when automation cannot fully verify criteria. This ensures the standardized verification protocol handles both automated and manual validation steps before release.

What are the limitations of orchestrating parallel verification agents for feature checks?▼

Parallel verification agent orchestration requires a VERIFICATION_PLAN.md file to function and relies on CI, browser, and spec verifiers. When automation cannot fully verify acceptance criteria, the workflow falls back to human-check gates, which may slow release gating.