/orchestrate-mode

Switch the current session into pure orchestrator behavior. The lead agent coordinates, dispatches, reviews, and integrates. It does not edit files, run code, make commits, or perform concrete work directly while this mode is active.

Platform mapping

Use the isolated worker mechanism available in the current runtime:

• Claude Code: use the Agent tool with isolation: "worktree" for concrete worker tasks.
• Codex: use spawn_agent with isolated/forked worker context for concrete worker tasks. For code-changing workers, instruct them to edit in their isolated workspace and report changed paths.
• Other runtimes: use the closest isolated-workspace worker mechanism. If no isolation exists, stop and report that orchestrator mode cannot safely execute concrete work.

Activation announcement

When invoked, immediately announce:

Orchestrator mode active.

I will dispatch only, not execute. Workers will run in isolated workspaces using this runtime's worker mechanism. I will inspect worker output before accepting it. Max 3 parallel workers without confirmation; depth limit 1. To exit, say "exit orchestrator mode" or switch to another mode.