sub-agent-coordinatorlisted

# Sub-Agent Coordinator Orchestrate focused work across multiple sub-agents using proven patterns. This skill handles briefing, spawning, communication, and verification when delegating complex tasks. Use this skill to **parallelize independent work, avoid conflicts, and maintain coordination state** across sub-agents. > **Framing — sub-agent coordination is harness engineering for delegated work.** Each primitive shows up here explicitly: *context engineering* lives in the briefing templates (what the sub-agent sees before it starts); *observable feedback loops* live in the verify-before-completion gate and structured-result contracts; *state preservation* is why all spawning happens at the parent level (no nested sub-agents) — nested state is unrecoverable. When a sub-agent run fails, ask which primitive was underspecified before asking whether the sub-agent was "wrong." --- ## What Are Sub-Agents Sub-agents are separate agent instances that handle a scoped piece of work. They: - Work independently on assigned tasks - Operate within defined constraints and boundaries - Report back with structured results - Can be spawned in parallel for independent tasks A sub-agent is not a human teammate — it is another instance of you, task-focused and context-limited, designed to parallelize work that would otherwise be sequential. --- ## Coordinator vs. Implementer When you are orchestrating work, adopt the **coordinator mindset**: | **Your Job (Coordinator)** | **NOT Your J