agent-composer

# agent-composer — Agent Composition Layer A coordinator skill that reads the work context and decides "which agents to dispatch, when, and in what order." Selects the optimal combination from the FH skill pool and either outputs a fan-out plan or executes it directly. ## Triggers - `/agent-composer` - "Which agent should I use?", "Pick one automatically", "Compose the agents" - "Set up the agents", "Decide which agents to use" - "Split the work and run in parallel", "Process with multiple agents" - "Build the dispatch plan", "Run in parallel splits" - When the task is complex or spans multiple projects ## Core Principles - **Compose only**: Does not perform work directly. Outputs the dispatch plan and executes after user approval. - **Parallel first**: When 2+ tasks are independent, propose parallel fan-out instead of sequential. - **Minimal composition**: Only the agents needed. Over-provisioning agents creates inefficiency. - **Coordinator ≠ executor**: Only collects results (fan-in) and presents an integrated report. --- ## Step 0. Context Collection Identify 4 items from the request: task type · scope · constraints · natural-language goal → skill mapping. Check `LOCAL_SKILL_REGISTRY.md` for project-local skills; check `.mcp.json` or `CLAUDE.md` for external plugins. > **Detail**: See `SKILL_detail.md §Step-0` — NL pattern mapping table, cross-install detection, registry lookup format — read when auto-mapping an ambiguous request. --- ## Step 0.2 — Capability F...