Subagent orchestrator

Subagent Orchestrator

Subagent Orchestrator splits complex work into bounded specialist tasks while keeping one main agent responsible for integration and final correctness.

Trigger Conditions

Use this skill when:

• The user asks for subagents, custom agents, delegation, parallel work, or multi-agent execution.
• $project-commander identifies independent work streams that can run in parallel.
• Research, implementation, tests, and review can be separated without overlapping write sets.

Do Not Trigger

Do not use this skill when:

• The runtime has no subagent tool and simulated roles add no value.
• The next critical-path step is blocked on the delegated work.
• Tasks would duplicate each other or write to the same files without a merge plan.
• Current tool policy requires explicit user permission and the user has not provided it.

Role Catalog

• explorer: answer a specific codebase question; read-only.
• architect: assess design options and risks; usually read-only.
• worker: implement a bounded change with explicit file/module ownership.
• tester: run focused verification and report failures.
• reviewer: inspect diffs for bugs, regressions, and missing tests.
• docs-researcher: check external or local docs when current information may have changed.

Orchestration Workflow

1. State the local critical path: what the main agent will do immediately.
2. Split only independent sidecar tasks.
3. For each subagent task, specify:
   • role
   • objective
   • allowed files/modules
   • forbidden files/modules
   • expected output
   • whether edits are allowed
4. Spawn real subagents only if available and permitted. Otherwise, run the role sequence locally.
5. Keep working locally while subagents run.
6. Wait only when the result is needed for the next step.
7. Integrate outputs. Review any subagent code before trusting it.
8. Update .agent/ memory with assignments, results, and integration status.

Required .agent/ Updates

Always update:

• .agent/TASKS.md: add each delegated task and owner/role.
• .agent/LOG.md: record spawned or simulated agents, prompts, results, and integration notes.
• .agent/HANDOFF.md: list active/completed subagent streams and unresolved dependencies.

Update when relevant:

• .agent/DECISIONS.md: delegation strategy, accepted design choice, or merge decision.
• .agent/PLAN.md: phase changes caused by findings.

Other Skills

• Use $deep-planner before orchestration if the task is not yet decomposed.
• Use $verification-loop after integrating any edits.
• Use $self-reviewer after integration.
• Use $handoff-writer before ending.

Verification

Subagents do not replace verification. After integration, the main agent must run or follow $verification-loop.

Output Format

ORCHESTRATION PLAN
Main-agent critical path:
Delegated streams:
- Role:
  Objective:
  Scope:
  Output:
  Status:
Integration plan:
Verification plan: