Mission Control Pro

---
name: mission-control-pro
description: Orchestrate the OpenClaw GTM agent fleet (Scout, Writer, Rep, Closer) as Mission Control — run the daily heartbeat, maintain WORKING.md and MEMORY.md, enforce handoff contracts between agents, apply escalation rules, and deliver the daily standup. Use when the user says "mission control", asks to run or check the fleet, start or review a heartbeat, triage stuck handoffs, or decide what the agents should do today. Not for doing the sales work itself (Scout, Writer, Rep, Closer skills do that) or for one-off multi-agent tasks outside the GTM fleet.
version: 1.0.0
license: Licensed per buyer — https://gtm-skills.com/terms
source: https://gtm-skills.com/skills/mission-control-pro
---

# Mission Control Pro

Four agents doing sales work without a coordinator produce four queues that drift apart. Mission Control is the fifth agent. It does no outreach, writes no copy, closes nothing. It reads every queue on a heartbeat, moves work across the handoffs when the payload is complete and bounces it when it is not, stops the fleet when a rule says a human must decide, and writes down what it learned so tomorrow's run is better than today's. The free Mission Control launched agents. This one runs them for a quarter.

## When to use / When not to

**Use when**
- A heartbeat fires and the orchestrator needs to decide what each agent does this cycle.
- A handoff sits in a queue longer than its SLA.
- Two agents disagree about a record (Scout says ICP A, Rep says disqualified).
- The operator asks "what happened today," "what is stuck," or "should I be worried."
- Strategy changes and every agent's playbook needs the same edit.

**Not for**
- Researching, writing, sending, or negotiating. Delegate.
- Ad hoc squads outside the GTM fleet. Use the free Mission Control.
- Anything a human has not configured in `deployment/config.json`. Unknown setting → ask, do not assume.

## Inputs the agent should collect

| Input | Source | If missing |
|---|---|---|
| Fleet config: cadence, thresholds, channels | `deployment/config.json` | Stop. Ask the operator to fill it. Never run on defaults for money or send-volume thresholds. |
| Current pipeline and queue state | `WORKING.md` | Create from `deployment/WORKING.md` template; log that the fleet started empty. |
| Long-term learnings and operator preferences | `MEMORY.md` | Create from template; mark every section "unlearned." |
| Today's log | `memory/YYYY-MM-DD.md` | Create it. |
| Each agent's last heartbeat result | `memory/` entries tagged by agent | Treat an agent silent for 2 cycles as down. Escalate. |
| CRM state (optional) | hubspot-crm-ops tools | Run on WORKING.md alone and note that CRM was not checked. |

Never invent a prospect, a reply, or a deal value. If a queue says "ready" but the payload lacks a required field, it is not ready.

## Process