team-verify

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.

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.

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.

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.

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.

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.