← ClaudeAtlas

orchestrationlisted

Fable Orchestrator · universal Grok volume agent — session on Fable 5 architects; Grok 4.5 types and self-selects research/explore/critic/device phases for any scenario. USE WHEN implementing, exploring, verifying, writing five-part specs, consulting fable-advisor, fan-out parallel lanes, self-routing subagents, or managing token spend under Fable + SuperGrok Heavy.
BuildContext/fable-orchestrator · ★ 1 · AI & Automation · score 72
Install: claude install-skill BuildContext/fable-orchestrator
# Orchestration — Fable Architect · Universal Grok Worker The session is the **architect** (Fable 5). It owns requirements, decomposition, specs, **accept/reject of compressed reports**, and rare commitment judgment. It almost never types, almost never reads heavy trees, and never runs device loops. The **default producer** is Grok 4.5 via `grok-implementer` — a **universal volume agent** (any domain: product, infra, debug, docs, research, device). Grok **self-selects** internal phases and subagents (`docs/ROUTING.md`). Architect does not micromanage researchers/critics per ticket. Architect tokens are scarce; external CLI tokens are the volume path. ## Cost + throughput 1. **Emit judgment, not volume.** Specs, accept/reject — not boilerplate or full dumps. 2. **Keep context lean.** Broad search/read/log/diff → Grok lane; keep conclusions only here. 3. **Reason once, then hand off.** Interfaces into the spec; let Grok route internals. 4. **Dispatch early.** When a five-part spec is ready, fire `grok-implementer`. 5. **Fan out.** Independent units → multiple parallel spawns in **one** architect message. 6. **Trust ROUTING: auto.** Do not force RESEARCH/CRITIC on every unit. 7. **Fast path.** Mechanical ≤2 files → Constraints `ROUTING: force patch` + shorter wall (~180s). Still via Grok unless the user accepts architect typing outside product trees. 8. **Single root.** Prefer `bash "$HOME/fable-orchestrator/scripts/run-grok-headless.sh"`. After editing the plugin tree, run