domains / families / agent-tooling / muse-delegate

muse-delegate

separate

Delegate a coding task to Muse Code (`muse`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Muse — phrasings like "have Muse do X", "delegate this to Muse", "run it through Muse", or "use Muse to implement/fix/refactor" — or wants to run a queue of coding tasks through Muse while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. It applies only when the user wants that separate `muse exec` implementer run: if you are Muse yourself and the user simply asks you to write the code, do it directly. DO NOT USE for tasks small enough to do inline.

When to use

• delegating coding tasks to Muse
• running a queue of coding tasks through Muse
• having Muse implement, fix, or refactor code
• reviewing Muse's diff and committing it

When not to use

• The task is small enough to just do inline — delegation overhead is not worth it.
• The `muse` CLI is not installed or not authenticated (run `muse login`, or set `META_API_KEY`).
• You want to write the code yourself.
• You are on native Windows and need a supported launcher. Upstream's `muse` launcher is Darwin/Linux

Skill page

Source