The four modes

Muster exposes four entry points as slash commands under the muster: namespace.

Mode	Command	Shape
Run	/muster:run <outcome>	Plan and show, then stop for approval
Autopilot	/muster:autopilot <outcome>	Hands-off full lifecycle
Diagnose	/muster:diagnose <symptom>	Failure-first single-bug fix
Audit	/muster:audit [path]	Breadth-first whole-codebase review and fix

Run

The interactive router. Its front half is an assess-then-interview step: muster assess does a deterministic gap-check on the outcome (too short, no success criteria, vague), and if the outcome is not clear, the interview skill runs an interactive requirements interview, one question at a time, behind an approval gate.

Then it detects, routes, and shows the glass-box crew manifest plus the plan, and stops. Run plans and shows; it does not execute.

/muster:run Add rate limiting to the public API with tests

Run and Autopilot both accept a GitHub issue reference (a bare number, #123, or an issues URL) as the outcome.

Autopilot

Runs the whole lifecycle hands-off: branch, detect, route, run waves (parallel fan-out, tournaments, an adversarial review gate), commit per wave, then present the merge decision. It only stops for that merge decision or for an escalation.

/muster:autopilot Resolve all open issues and update the README

It triggers the interview only on an actual information gap. In unattended (Routine) mode it records the gap to the run report instead of blocking, and stops at a reviewable artifact (a pull request) rather than auto-merging.

Diagnose

Failure-first. Reproduce, find the root cause via systematic debugging on the best available debug provider, fix, add a regression test, verify. No symptom-patching.

/muster:diagnose Paste a failing test or stack trace here

Audit

The review-and-fix counterpart to diagnose. Where diagnose is one bug, audit sweeps the whole codebase. It fans out six read-only dimension reviews in parallel (architecture, tech-debt, coverage, simplification, readability, security), each on the best provider for its role, consolidates the findings into one ranked ledger, then fixes everything with TDD and verifies through the review gate before presenting the merge.

/muster:audit
/muster:audit src/payments

Next: the CLI commands that power these modes.