agents

agents

1. Decide: yourself unless several lanes or a long wait (§ 1); an irreversible step → § 2's question, then act.
2. Clarify: no target you could verify → read_skill grill, its interview until settled, no plan before; one decision to confirm → one grill-shaped question before the act; remember --decision as each settles.
3. Init: the message on stdin, init - --slug … --done-means … --goal … --repo …; --engine codex|claude when the user names the workers' engine.
4. Propose (only when § 1 says threads; else do it now): the threads as JSON → propose.
5. Open or ask: a plain split → go, arm the wake, tell the plan; else the texts to choose between, or § 2's question.
6. Each wake: context once; inbox, oldest first; propose ready threads; one name-first line per thread; wake armed; end the turn.
7. Done: verify, accept each thread, agents.py archive, say what closed and stayed.

Never a silent start: your first line on /agents <goal> is a status line ("Reading the repo for a split; plan in about a minute.") and each exploration round past a few reads ends with a short progress line until the plan. Run python3 <skill-dir>/scripts/agents.py <verb>; read its stdout alone (progress is stderr; never 2>&1 into a JSON parser); write nothing outside <project>/library/. host-manager calls carry the --tmux prefix MUSE_AGENTS_TMUX names; the wake script carries MUSE_AGENTS_TMUX=<value>. Per-turn verbs propose, tick, follow, stop, ack and every flag: references/verbs.md; context reads the inbox it returns.

1. Decide

Every child is an agents.py lane; never subagent_spawn. You are the coordinator, a thread a separate agent session, done means the evidence ending it, threads are proposed and opened — at once when the split is plain, on the user's yes when not — a follow thread lands PRs, BLOCKED(HUMAN) is their question; no slug, init or arm talk before it is needed. Pick the shape by judgement — you orchestrate: split by independent units of work whose results join in your hands (per proposed unit, not the goal's final artifact); alternatives judged in parallel by a thread or the settled measure; a worker plus a verifier — examples only; yourself when nothing is independent. agents://agents is multi-agent collaboration through host-manager (never in-process subagents): you do the work yourself unless it needs several lanes at once or a long wait — then threads, or one follow thread while you stay in the channel (several fixes in one PR included is one thread); the plan line names the choice. The plan line says why in one or two sentences: the shape, why that many lanes (or one), what runs in parallel, when the first report is expected. A solo fix asks § 2's one question first when a step is irreversible or out of repo: clear goal + irreversible step = one question, then act. "Pick up " is resume <slug> --takeover --confirm "<their words>", never init: run it before any git or test in their clone.