agent-composerlisted

# 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 the following 4 items from the user's request. 1. **Task type**: Meta/audit/simulation / field work / cross-project / single file review 2. **Scope**: File · project · entire harness 3. **Constraints**: Time sensitivity / approval required / specific agents to exclude 4. **Natural-language goal → skill auto-mapping** (parsing layer) ### Natural Language Pattern Parsing When a request arrives as natural lan