Prompt file imported from fmflurry/settings-opencode (.claude/commands/orchestrate.md). Fill in {{arguments}} before use. Copyright stays with the author.

Orchestrate Command

CC: delegate this to the planner subagent via the Agent tool (subagent_type: planner). The subagent inspects the repo and runs the steps below.

Orchestrate multiple specialized agents for this complex task: {{arguments}}

Your Task

1. Analyze task complexity and break into subtasks
2. Identify optimal agents for each subtask
3. Create execution plan with dependencies
4. Coordinate execution - parallel where possible
5. Synthesize results into unified output

Available Agents

Orchestration Patterns

Sequential Execution

planner → tdd-guide → code-reviewer → security-reviewer

Use when: Later tasks depend on earlier results

Parallel Execution

           ┌→ security-reviewer
planner → ├→ code-reviewer
           └→ architect

Use when: Tasks are independent

Fan-Out/Fan-In

           ┌→ agent-1 ─┐
planner → ├→ agent-2 ─┼→ synthesizer
           └→ agent-3 ─┘

Use when: Multiple perspectives needed

Execution Plan Format

Phase 1: [Name]

• Agent: [agent-name]
• Task: [specific task]
• Depends on: [none or previous phase]

Phase 2: [Name] (parallel)

• Agent A: [agent-name]
  • Task: [specific task]
• Agent B: [agent-name]
  • Task: [specific task]
• Depends on: Phase 1

Phase 3: Synthesis

• Combine results from Phase 2
• Generate unified output

Coordination Rules

1. Plan before execute - Create full execution plan first
2. Minimize handoffs - Reduce context switching
3. Parallelize when possible - Independent tasks in parallel
4. Clear boundaries - Each agent has specific scope
5. Single source of truth - One agent owns each artifact

NOTE: Complex tasks benefit from multi-agent orchestration. Simple tasks should use single agents directly.