Orchestrate

Treat the current session as the control tower. Keep decomposition, worker routing, integration, user communication, and final review in this session. Use orchestrate.sh to control detached agent-CLI workers in tmux or cmux.

Resolve ORCH to the absolute orchestrate.sh adjacent to the SKILL.md that loaded this skill. Verify that it is executable before continuing. Use the output of "$ORCH" help as the authority for command syntax, supported profiles, and defaults; the current help command exits with status 1 after printing that output.

Control invariants

• Launch full-auto workers only in directories the user has entrusted to autonomous edits and commands.
• Record the active ORCH_HOME and choose a unique run prefix. Start every worker ID with that prefix so concurrent control towers sharing the state directory cannot collide.
• Record each worker's ID, directory, workstream, and latest state. Pass explicit ledger IDs to waitall and stop; reserve no-ID waitall, stop --all, and gc for recovery after confirming the entire ORCH_HOME is in scope.
• Route human decisions to the user. Treat --answer as an assertion that the user chose the supplied response, and pass it only after receiving that choice.
• Interpret DONE as a settled worker screen. Establish task completion separately by reading the logs, checking for trailing questions or unfinished plans, reviewing the result, and running verification.
• Interpret TIMEOUT as a live worker that needs inspection or more time. Inspect with poll or logs, then wait again.
• Run commands that may exceed the host's foreground limit (spawn, run, wait, waitall, and stop) through the host's non-blocking execution facility, retaining the handle until stdout is collected.

For two or more concurrent workers, read references/fan-out.md completely before creating any worker, then apply it alongside the loop below.

Dispatch loop