orchestrator-modelisted

Sequential chain routing — decomposes a compound task into subtasks, routes each subtask to its optimal tier (via advisor-mode underneath), runs a quality-gate check after each step, and escalates to a higher tier on gate failure. Complements council-mode (parallel comparison). Orchestrator is the "route around failure" thesis applied sequentially: keep each subtask on the cheapest tier that passes, escalate only when the gate fails. Trigger on: "orchestrator mode", "chain this", "break this into subtasks", "route each step", "escalation pipeline", "run this as a chain", "decompose and route", "quality- gated routing", "sequential tier routing", "run the orchestrator".
cerebrocybersolutions/libro · ★ 0 · AI & Automation · score 78

Install: claude install-skill cerebrocybersolutions/libro

# Orchestrator Mode ### Sequential Chain Routing | Quality-Gated Escalation | Cost-Minimizing Orchestrator mode takes a compound task, decomposes it into subtasks, and routes each subtask to its optimal tier via advisor-mode. Between steps, a quality gate checks whether the output satisfies the subtask's acceptance criteria. If the gate fails, the subtask re-dispatches one tier up. If the gate passes, the chain continues. **Core principle:** > Route around failure, don't pick the "best" model. Orchestrator keeps every subtask > on the cheapest tier that passes, and only escalates when a specific gate trips. This is the complement to council-mode. Council compares models on the same task; orchestrator runs a chain where each step picks its own tier and earns its escalation. --- ## BRAIN CHECK — Run Before Every Orchestrator Call Brain root: resolved from `$CEREBRO_ROOT` env var or `~/.cerebro/profile.yaml`. 1. Verify advisor-mode is installed and provider-aware 2. **Local fleet (optional):** if `fleet_primary` is set, verify Ollama is reachable. Cloud-only deployments skip this check — all tiers route to cloud. 3. Verify the task decomposes into ≥2 discrete subtasks (otherwise use advisor-mode directly) --- ## WHEN TO USE ORCHESTRATOR MODE | Situation | Why Orchestrator | |-----------|-----------------| | Multi-step pipeline with different subtask types | Each step picks its own optimal tier | | Research → draft → review chain | Decompose by knowledge intensity |