missionlisted

# /mission — autonomous mission runner Manage self-driving missions. Each mission is **two folders**: `~/missions/<name>` — the control plane, holding only the operational markdown files (mission, prompts, backlog, log, decisions, questions); `~/Desktop/missions` is a symlink to it for Finder — and `~/Projects/<name>` — the workspace where ALL work products land (code, specs, docs, reports). A mission need not be about code: it can span several existing repos, or be coordination, PR reviews, or communications — everything beyond the two folders happens only through explicit per-mission grants recorded in its CLAUDE.md "Scope & grants" section. A launchd job ticks every 5 minutes and runs headless Claude from the control plane: a **planning pass** (Fable 5.1) when there is human input to process, then an **implementation pass** (Opus 5) that completes exactly one backlog item — so an unblocked backlog iterates continuously, one item at a time, while a blocked or idle mission costs nothing (the runner's bash gates decide without spending tokens, and the lock makes ticks that land mid-run no-ops). All protocol details live in the mission's own `CLAUDE.md` (scaffolded from `templates/CLAUDE.md`), which every headless run auto-loads. ## Parse arguments `$ARGUMENTS`: - **No arguments, or the first token is one of `status` / `pause` / `resume` / `stop` / `control`** → an **aggregate command** across all missions (no args = `status`); see "Aggregate commands" below. - Otherwise t