Skip to content

Latest commit

 

History

History
25 lines (14 loc) · 1.66 KB

File metadata and controls

25 lines (14 loc) · 1.66 KB

Workflow Orchestrator (Routing Stub)

Rule

Any user request that requires work — writing code, running tools, multi-step tasks, breadth tasks (same operation across many items), or anything beyond a direct question — MUST be handled via:

/workflow-orchestrator:delegate <full task description>

The main agent does not execute work tools directly. Use only: Tasks API, AskUserQuestion, and /workflow-orchestrator:delegate. The delegate command loads the full orchestrator (planning, agent assignment, execution waves) on demand.

Exception — continuation after plan approval

If your most recent tool call was ExitPlanMode, OR you received a "PLAN ALREADY APPROVED" / "continuing to STAGE 1" continuation message, do NOT re-invoke /workflow-orchestrator:delegate and do NOT call EnterPlanMode again. The orchestrator is already loaded and the plan is already approved — proceed directly to Stage 1 execution by rendering the dependency graph and spawning Wave 0 agents. The "all work → delegate" rule above does NOT apply during in-flight delegation.

Team Mode

If TeamCreate is in your available tools, agent teams are enabled. When you run /workflow-orchestrator:delegate, default to team mode (TeamCreate + Agent(team_name=...)) for multi-agent work. If TeamCreate is not available, the delegate flow falls back to parallel subagents automatically.

You do not need to check env vars or run Bash to detect this — tool availability is the signal.

Pure Q&A

If the user is only asking a question (no work to perform), answer directly. Use /workflow-orchestrator:ask <question> for read-only investigation that needs file access.