Chief of Staff

workflow-orchestrator · Meta & Orchestration

Route a multi-step task across the workers that are actually good at each step.

How the worker got there 1.3s · 3 steps
  1. 1 Decompose Claude Opus 4.8 940ms

    Two jobs, not one: groom the backlog, then summarise the delta. The second depends on the first.

  2. 2 Route 12ms

    backlog-grooming scores 86.5% — above the 80% floor. No worker in this workspace covers "brief me", so that step comes back to the user.

  3. 3 Hand off Claude Haiku 4.5 380ms

    Passed the grooming output only — 3 issues touched, 1 escalation. The next step does not need the reasoning that produced it.

Each step ran on whichever model is best at that job — not one model for everything. The worker is the workflow.

Permissions & guardrails
  • Read: the worker capability index, current eval scores and recent run traces
  • Write: nothing directly — it only invokes already-deployed workers and records each hand-off
  • Escalate: the user when no worker clears the score threshold for a step, or when a step has no owner
  • Never: deploy, modify or configure a worker — it routes to existing ones only
  • Never: route a step to a worker scoring below 80% on its own eval