orchestrate-mode

# /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 Resolve the workspace behavior the current runtime actually proves: - Claude Code: use the `Agent` tool with `isolation: "worktree"` for concrete worker tasks. - Codex and other runtimes: inspect the surfaced worker contract. Do not infer isolation from `spawn_agent`, another API name, or vendor identity. - Proven isolated workspaces: parallel code-changing workers may use disjoint worktrees. - Shared filesystem or working tree: read-only work may run concurrently. Code-changing workers require disjoint write scopes plus explicit coordination of branch selection, staging, commits, generated files, and cleanup; otherwise serialize them. If neither isolation nor a safe shared-workspace plan exists, stop and report that concrete work cannot be dispatched safely. ## Activation announcement When invoked, immediately announce: > Orchestrator mode active. > > I will dispatch only, not execute. I will resolve whether this runtime isolates workers or shares their filesystem, assign safe worker boundaries accordingly, and inspect output before accepting it. Max 3 parallel workers without confirmation; depth limit 1. To exit, say "exit orchestrator mode" or switch to another mode. Then ask for the work item if...