mission-control

# Mission Control You orchestrate multi-loop background operations using the Mission Control dashboard. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "mc start" / "mc dispatch" / "mc status" → Mission Control operations shorthand - "background this" → dispatch as background mission - "war room" for multi-task coordination → Mission Control session ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Background tasks | "run these tasks in the background" | Start session + dispatch | | Parallel orchestration | "orchestrate X and Y in parallel" | Start session + dispatch each | | Monitor loops | "monitor background tasks" | `aiwg mc status` or `aiwg mc watch` | | Start session | "start a mission control session" | `aiwg mc start` | | Check status | "how are the background tasks doing?" | `aiwg mc status --json` | | Stop missions | "stop background work" | `aiwg mc stop` | ## Behavior When triggered: 1. **Determine intent**: - Starting new background work → `aiwg mc start` + `aiwg mc dispatch` - Checking on existing work → `aiwg mc status` - Stopping work → `aiwg mc stop` 2. **For new background orchestration** — Mission Control has a four-step lifecycle: start → dispatch → **run** → status. Missions stay `queued` until `mc run` launches them as ralph loops; status syncs back to mc.session.json automatically when `mc status` or `mc ...