orchestrated-execution

Coordinate complex work units through a 4-phase implement, validate, adversarial review, and commit loop.

Updated Feb 19, 2026

Search Tags:#multi-agent #governance #quality-gates #plan-review #adversarial-review #orchestrated-execution #4-phase

Ready to run

npx skills add https://github.com/Prekzursil/quality-zero-platform --skill orchestrated-execution-prekzursil

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrated-execution
Source: https://github.com/Prekzursil/quality-zero-platform/tree/main/.claude/plugins/metaswarm/skills/orchestrated-execution
Command: npx skills add https://github.com/Prekzursil/quality-zero-platform --skill orchestrated-execution-prekzursil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a rigorous 4-phase execution loop to coordinate complex work units, reducing miscommunication and drift by enforcing defined stages: IMPLEMENT, VALIDATE, ADVERSARIAL REVIEW, and COMMIT.

Core Features & Use Cases

Mode-agnostic orchestration across Task and Team modes with a consistent 4-phase flow.
Independent verification via adversarial review to ensure spec and DoD adherence before committing.
Context-aware commits that update a central project context and service inventory for traceability.

Quick Start

Spawn and run a work unit through the 4-phase loop to observe phase transitions and validation gates in action.

Frequently Asked Questions about orchestrated-execution

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

FAQPage Schema

How do I coordinate multi-agent workflows with validation gates?▼

Multi-agent workflows with validation gates are coordinated through a 4-phase loop: implement, validate, adversarial review, and commit. This enforces rigorous quality checks and reduces drift across complex tasks.

What is adversarial review in multi-agent orchestration?▼

Adversarial review in multi-agent orchestration is an independent verification phase that ensures spec and definition-of-done adherence before committing. It catches issues missed during implementation and validation phases.

How do I enforce a definition-of-done before committing code changes?▼

Enforce a definition-of-done before committing by passing work units through a 4-phase loop with explicit validation and adversarial review gates. These gates verify spec adherence and block commits until requirements are met.

Does multi-agent orchestration work for both task and team modes?▼

Multi-agent orchestration works mode-agnostically across both task and team modes. The 4-phase execution loop maintains a consistent flow for implementing, validating, reviewing, and committing regardless of the operational mode.

How do I maintain project context traceability during multi-agent execution?▼

Maintain project context traceability during multi-agent execution by using context-aware commits. These commits update a central project context and service inventory, ensuring full traceability across all orchestrated work units.

When should I use a 4-phase orchestrated execution loop?▼

Use a 4-phase orchestrated execution loop for complex work units requiring multi-agent coordination, plan validation, and rigorous quality gates. It is essential when independent adversarial reviews and strict definition-of-done adherence are mandatory.