soleri-subagent-driven-developmentlisted

# Subagent-Driven Development Decompose work into isolated units, dispatch subagents via the Agent tool, merge results back. You are the orchestrator — you make all decisions, subagents execute. **Announce at start:** "I'm using the subagent-driven-development skill to dispatch isolated agents." ## The Orchestrator Contract **You are the boss. Subagents are the crew.** 1. **All decisions stay with the orchestrator.** Research the task, consult the vault, decide the approach. Subagents receive exact specs — scope, file boundaries, acceptance criteria. They execute, they don't decide. 2. **Subagents MUST NOT create plans.** Only the orchestrator creates plans. Subagent prompts must explicitly state: "Do NOT create plans, do NOT call planning tools." 3. **If a subagent hits ambiguity, it returns — it doesn't guess.** The orchestrator resolves, then re-dispatches. 4. **The orchestrator reconciles all work.** After subagents return, the orchestrator reviews changes, merges, captures knowledge. ## Hybrid Agent Routing Not all subagents are equal. Route by complexity: | Signal | Agent Type | Why | | ------------------------------------- | ------------------------- | ----------------------------- | | Single file, clear spec, no decisions | **Claude Code worker** | Fast, low overhead | | Approach already in parent plan | **Claude Code worker** | Spec is decided | | 3+ f