Agent Orchestrator

Orchestrate complex tasks by decomposing them into subtasks, spawning autonomous sub-agents, and consolidating their work.

Core Workflow

Phase 1: Task Decomposition

Analyze the macro task and break it into independent, parallelizable subtasks:

CODEBLOCK0

Decomposition Principles:

• - Each subtask should be completable in isolation
• Minimize inter-agent dependencies
• Prefer broader, autonomous tasks over narrow, interdependent ones
• Include clear success criteria for each subtask

Phase 2: Agent Generation

For each subtask, create a sub-agent workspace:

CODEBLOCK1

This creates:
CODEBLOCK2

Generate SKILL.md dynamically with:

• - Agent's specific role and objective
• Tools and capabilities needed
• Input/output specifications
• Success criteria
• Communication protocol

See references/sub-agent-templates.md for pre-built templates.

Phase 3: Agent Dispatch

Initialize each agent by:

1. 1. Writing task instructions to INLINECODE0
2. Copying required input files to INLINECODE1
3. Setting status.json to INLINECODE3
4. Spawning the agent using the Task tool:

CODEBLOCK3

Phase 4: Monitoring (Checkpoint-based)

For fully autonomous agents, minimal monitoring is needed:

CODEBLOCK4

Periodically check status.json for each agent. Agents update this file upon completion.

Phase 5: Consolidation

Once all agents complete:

1. 1. Collect outputs from each agent's INLINECODE5
2. Validate deliverables against success criteria
3. Merge/integrate outputs as needed
4. Resolve conflicts if multiple agents touched shared concerns
5. Generate summary of all work completed

CODEBLOCK5

Phase 6: Dissolution & Summary

After consolidation:

1. 1. Archive agent workspaces (optional)
2. Clean up temporary files
3. Generate final summary:

CODEBLOCK6

File-Based Communication Protocol

See references/communication-protocol.md for detailed specs.

Quick Reference:

• - inbox/ - Read-only for agent, written by orchestrator
• INLINECODE7 - Write-only for agent, read by orchestrator
• INLINECODE8 - Agent updates state: pending → running → completed | INLINECODE12

Example: Research Report Task

CODEBLOCK7

Sub-Agent Templates

Pre-built templates for common agent types in references/sub-agent-templates.md:

• - Research Agent - Web search, data gathering
• Code Agent - Implementation, testing
• Analysis Agent - Data processing, pattern finding
• Writer Agent - Content creation, documentation
• Review Agent - Quality assurance, editing
• Integration Agent - Merging outputs, conflict resolution

Best Practices

1. 1. Start small - Begin with 2-3 agents, scale as patterns emerge
2. Clear boundaries - Each agent owns specific deliverables
3. Explicit handoffs - Use structured files for agent communication
4. Fail gracefully - Agents report failures; orchestrator handles recovery
5. Log everything - Status files track progress for debugging