advisor-orchestrator-worker

Orchestrates parallel worker models with advisor review to execute large multi-subtask projects.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Protremix/EvolvixOS --skill advisor-orchestrator-worker-protremix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: advisor-orchestrator-worker
Source: https://github.com/Protremix/EvolvixOS/tree/main/knowledge/skills/advisor-orchestrator-worker
Command: npx skills add https://github.com/Protremix/EvolvixOS --skill advisor-orchestrator-worker-protremix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-model passes break down on tasks too large for one context window or one generation call, and naive multi-model loops fail from context leaks, silent partial failures, and judgment applied too late. This Skill turns your coding agent into the orchestrator of a three-tier model team that splits big tasks into self-contained briefs, runs them across cheap parallel workers, verifies every result, and consults a stronger advisor model exactly twice: before work starts and before delivery. ## Core Features & Use Cases - Three-tier model team: an orchestrator plans and verifies, stateless workers (default Gemini 3.7 Flash via the agy CLI) execute one subtask each in parallel, and an advisor (default Claude Fable 5) reviews the plan and the final draft without ever executing. - Stateless worker briefs with verification: every dispatch carries full inline inputs and acceptance criteria, and each result is judged PASS, FIX (redispatched naming the failure), or ESCALATE, with no silent partial passes. - Budgets and fallbacks: every run states a budget up front, and missing CLIs fall back to the Gemini or Anthropic APIs, with a clearly labeled degraded mode when a role has no working path. - Use Case: Ask the agent to research 12 competitors in parallel: it frames success criteria, gets the plan reviewed by the advisor, fans out 12 worker briefs in batches, verifies each report, and delivers a synthesized comparison with a verification ledger. ## Quick Start Ask your agent to orchestrate this task across a model team because it is too big for one pass, fanning the subtasks out to parallel workers with advisor review.

Frequently Asked Questions about advisor-orchestrator-worker

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

FAQPage Schema
How do I split a large task across multiple AI models?▼

Frame the deliverable with 3 to 5 checkable success criteria, decompose it into self-contained subtasks with inline inputs and acceptance criteria, then dispatch each subtask to a stateless worker model in parallel. Verify every result against its own criteria before synthesizing the final deliverable.

How to run parallel LLM workers with the agy CLI?▼

Write each worker brief to a temp file and dispatch agy from an empty temp directory in a background subshell, chunking waves into batches of 3 due to shared Antigravity quota. Reap each worker with its own wait call and read each output file in dispatch order.

What happens if the agy or claude CLI is not installed?▼

Each role falls back to its API key: workers use the Gemini API via GEMINI_API_KEY or GOOGLE_API_KEY, and the advisor uses the Anthropic API via ANTHROPIC_API_KEY. If a role has neither CLI nor key, the skill offers a labeled degraded mode where the orchestrator plays that role.

When should I not use a multi-model orchestration loop?▼

Skip it for single-file edits or any task one model handles in a single pass, since the advisor consults and verification ledger add overhead. It is designed for tasks too large for one pass or requiring parallel generation across many subtasks.

Why do multi-model agent loops fail and how is it prevented?▼

They typically fail from context leaks, silent partial failures, and judgment applied too late. This loop prevents them with stateless briefs carrying full inline inputs, per-result PASS/FIX/ESCALATE verification, and mandatory advisor review before dispatch and before delivery.

How does the advisor model differ from worker models?▼

The advisor is the strongest available reasoning model used only for plan review, conflict resolution, and final taste passes, never for execution. Workers are the cheapest models that pass verification, each handling one stateless subtask with no memory or follow-ups.