Orchestrate

/hub:orchestrate is for changes that cross ≥3 domains and need explicit staging. It runs in two phases: planner produces a plan, you approve it, then agents execute with clear hand-offs.

When to use it

• Multi-domain work (API + frontend + mobile + infra, etc.).
• Risky or irreversible changes that deserve a review step.
• When you want the execution split across agents, not done by one.

When NOT to use it

• Single-agent work. Use create or enhance.
• No existing plan and no clear scope. Use brainstorm first.

Invocation

/hub:orchestrate migrate auth from sessions to JWT across API + frontend + mobile

@hub orchestrate migrate auth from sessions to JWT across API + frontend + mobile

The two phases

Phase 1 — plan

hub:orchestrator explores the repo, produces a plan that names every agent and every step with hand-offs, and shows you a HEAVY gate including the full dependency graph. You approve, tweak, or cancel.

Phase 2 — implement

The approved plan executes. Each agent runs in order, passes context to the next, and you see a clean transcript block per agent.

Example session

Pro tips

• Use orchestrate when the risk is “one agent forgot the other domain.” The plan phase makes hand-offs explicit.
• Tweak the plan, not the prompt. The HEAVY gate accepts tweak — use it to reorder steps or drop an agent.
• Ledger afterwards. /hub:ledger by-agent reveals which specialist ate the most tokens. Next time, you can warn them to be conservative.

Next steps

• Create — lighter, single-chain scaffolding for greenfield.
• Approval gate — how the HEAVY frame is built.
• Security auditor — the agent that caught HS256 here.