advisor-orchestrator-worker

Orchestrate parallel model workers with advisor review for large multi-step tasks.

135k|19.9k|Updated Apr 29, 2024
One-click install
npx skills add https://github.com/Shubhamsaboo/awesome-llm-apps --skill advisor-orchestrator-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advisor-orchestrator-worker
Source: https://github.com/Shubhamsaboo/awesome-llm-apps/tree/main/agent_skills/advisor-orchestrator-worker
Command: npx skills add https://github.com/Shubhamsaboo/awesome-llm-apps --skill advisor-orchestrator-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Large tasks that exceed a single model's context window or require parallel research across many subtasks often fail due to context leaks, silent partial failures, or judgment applied too late. This Skill enforces a disciplined three-tier loop that splits work into stateless briefs, verifies every result, and consults a stronger advisor model only at commitment boundaries.

Core Features & Use Cases

  • Three-tier model team: Orchestrator plans and verifies, cheap parallel workers execute subtasks, and a stronger advisor reviews the plan and final deliverable.
  • Stateless worker briefs: Every dispatch carries full inputs and acceptance criteria inline, written to temp files to prevent shell injection and context leakage.
  • Mandatory verification: Each result is judged PASS, FIX (redispatched with named failure), or ESCALATE against its own acceptance criteria.
  • Advisor as critic: Two mandatory consults (plan review and taste pass) plus mid-loop escalation, with every note applied or explicitly rebutted.
  • Use Case: Research twelve competitors in parallel, synthesize findings into a report, and have a stronger model review both the research plan and the final draft before delivery.

Quick Start

Ask your coding agent to orchestrate this task across a model team using the advisor-worker loop.

Frequently Asked Questions about advisor-orchestrator-worker

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

FAQPage Schema
How do I run multiple AI models in parallel on one task?

Decompose the task into self-contained subtasks with inline inputs and acceptance criteria, then dispatch each as a background shell process. Use temp files for briefs to avoid shell injection, reap each worker with its own wait, and verify results against acceptance criteria before merging.

What is the advisor-worker pattern for multi-model orchestration?

A three-tier loop where an orchestrator plans and verifies, cheap parallel workers execute stateless subtasks, and a stronger advisor model reviews the plan before dispatch and the deliverable before shipping. The advisor never executes, only judges.

Can I use Gemini and Claude together in one workflow?

Yes. Workers default to Gemini via the agy CLI with a Gemini API fallback, while the advisor uses Claude via the claude CLI with an Anthropic API fallback. Each role resolves CLI first, then API key, and announces every fallback up front.

Why do multi-model loops fail with context leaks or partial passes?

Failures come from shared context between workers, silent acceptance of partial results, and judgment applied too late. The fix is stateless briefs with full inline inputs, mandatory verification per subtask, and advisor consults only at commitment boundaries.

When should I not use a multi-model orchestrator?

Skip it for single-file edits or tasks one model handles in one pass. The overhead of planning, dispatching, verifying, and advisor review only pays off when the task is too large for one model or benefits from parallel generation.