orchestratelisted

# Skill: Orchestrate **CRITICAL**: Run `HARNESS_DIR=$(epic-harness path)` first. NEVER use `.harness/` in the project directory. ## Mode: auto (default) Triggered automatically when an active multi-agent orchestration is detected. ### Step 1: Check orchestration state 1. Run `HARNESS_DIR=$(epic-harness path)` 2. Read `$HARNESS_DIR/orchestrator/run.json` 3. If no active run, this skill does not apply — return ### Step 2: Read agent inbox 1. Read `$HARNESS_DIR/orchestrator/agents/{my_id}/inbox.jsonl` 2. Process any pending messages from other agents or user interventions 3. Messages from other agents: integrate into current task context 4. Messages from user (via intervene redirect): adjust task accordingly ### Step 3: Check control directives 1. Read `$HARNESS_DIR/orchestrator/control.json` 2. If a directive targets this agent (or "all"), act on it: - **pause**: halt work after current tool call, wait for resume - **cancel**: stop immediately, set status to "cancelled" - **redirect**: adopt the new instruction, discard current task - **resume**: resume from paused state 3. After acting on a directive, increment `generation` in control.json to acknowledge ### Step 4: Check dependencies 1. Read `$HARNESS_DIR/orchestrator/run.json` dependency graph 2. Identify which agents this agent depends on 3. Read their `status.json` — if any dependency is not DONE, wait 4. If all dependencies are DONE, proceed with task ### Step 5: Execute with progress reporting While w