muse-delegate

1# Muse Delegate
2 
3You are the **orchestrator**. This skill lets you hand a bounded coding task to a separate
4**implementer** — Muse Code (`muse`) — then review what it produced and land it yourself. You write
5the brief and own the judgment; Muse does the typing in its own `exec` run; you verify and commit.
6 
7Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell
8command and read a file, so any agent with those two capabilities can drive it. The full delegate →
9review → commit loop has been run with Claude Code as the orchestrator. Other orchestrators remain
10unproven.
11 
12## When NOT to use this
13 
14- The task is small enough to just do inline — delegation overhead is not worth it.
15- The `muse` CLI is not installed or not authenticated (run `muse login`, or set `META_API_KEY`).
16- You want to write the code yourself.
17- You are on native Windows and need a supported launcher. Upstream's `muse` launcher is Darwin/Linux
18  only; this skill still ships in the Windows contract matrix, but a live Windows dispatch is not a
19  supported Muse install.
20 
21## Read this before the first dispatch: the autonomy model
22 
23Headless Muse is **`muse exec` only**. `muse resume` is the interactive TUI and is never invoked.
24`--resume-last` is rejected; continue a run with `--session <id>` (Muse's `--session-id`).
25 
26Write runs keep Muse's sandbox **on** and pass `--disable-approval` so a headless run cannot hang on a
27…