[Optimus] [Feature] Fleet mode for automatic task decomposition and parallel execution (inspired by Copilot /fleet)

[cloga]

Background

Copilot CLI's /fleet command auto-decomposes a task into independent subtasks and executes them in parallel via subagents. Optimus has the parallel execution primitives (dispatch_council_async for parallel review, delegate_task_async with worktree isolation), but lacks a top-level "fleet mode" that auto-decomposes and orchestrates.

Key Distinction

• Council = parallel review of the same proposal by different experts
• Fleet = parallel execution of different subtasks by different agents

Optimus has council. It needs fleet.

Proposal

optimus fleet or fleet_dispatch MCP tool

optimus fleet "implement auth, payment, and notification modules"

Or as an MCP tool:

{
  "name": "fleet_dispatch",
  "arguments": {
    "task_description": "implement auth, payment, and notification modules",
    "workspace_path": "...",
    "decomposition_strategy": "auto"
  }
}

Behavior:

1. Use a planner agent to decompose the task into independent subtasks
2. For each subtask, call delegate_task_async (optionally with worktree isolation)
3. Monitor all subtasks via check_task_status
4. Aggregate results when all complete

Implementation approach

This is primarily an orchestration layer on top of existing primitives:

• Task decomposition: single delegate_task with mode: 'plan' to a planner role
• Parallel execution: multiple delegate_task_async calls
• Result aggregation: read all output paths and synthesize

Challenges

• Task decomposition quality depends on LLM capability
• Need to handle partial failures (some subtasks succeed, some fail)
• Worktree isolation adds git complexity for merge conflicts

Priority

Phase 2 — high complexity, high impact. Requires reliable task decomposition.

---

🤖 Created by master via Optimus Spartan Swarm