ZES-verification-before-completion

Validate task completion via multi-agent tests, linting, and requirement checks.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-verification-before-completion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ZES-verification-before-completion
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/ZES-verification-before-completion
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-verification-before-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the premature claiming of task completion by enforcing a rigorous, multi-agent verification process that validates code, requirements, and system health before any work is finalized.

Core Features & Use Cases

  • Multi-Agent Validation: Simultaneously runs tests, linting, and requirement checks using specialized AI agents (Groq, OpenRouter, LLM7).
  • Browser Smoke Testing: Automates UI verification to ensure frontend projects are functional and free of console errors.
  • Use Case: Before pushing a new feature to production, use this skill to verify that all unit tests pass, type-checking is clean, and the implementation strictly adheres to the original project plan.

Quick Start

Run the zes verify command in your terminal to perform a full verification of the current project directory.

Frequently Asked Questions about ZES-verification-before-completion

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

FAQPage Schema
How do I prevent premature task completion claims in automated testing pipelines?

Prevent premature completion by running a multi-agent verification pipeline that executes local testing tools and AI-driven requirement analysis. This validates code quality, plan compliance, and functional integrity before any work is finalized.

Can I automate browser smoke testing to check for frontend console errors?

Yes, you can automate browser smoke testing to verify frontend projects are functional and free of console errors. This is achieved by integrating browser automation tools within the multi-agent validation pipeline.

How do I validate code compliance against the original project plan?

Validate code compliance by using AI-driven requirement analysis across the software development lifecycle. Specialized AI agents check the implementation to ensure it strictly adheres to the original project plan.

Do I need local test runners and linters to use multi-agent verification?

Yes, multi-agent verification requires integration with local test runners, linters, and browser automation tools. These provide objective evidence for status claims and execute the local testing tools.

What is the best way to run unit tests and type-checking before pushing a feature?

The best way to run unit tests and type-checking before pushing is using a multi-agent validation command. It simultaneously runs tests, linting, and requirement checks to verify system health.