mission-controllisted

# Mission Control Use this skill when the user wants Codex to work through Mission Control for planning, execution, approvals, status, or final handoff. ## Bridge boundary - Codex chat is the bridge between the user and Mission Control. - Codex chat is not the Manager AI. - Mission Control Manager owns planning, orchestration, worker routing, recovery actions, and completion state. ## Mission Control MCP tools to call - `mission_control_attach_workspace` - `mission_control_start_task` - `mission_control_get_status` - `mission_control_get_pending_decisions` - `mission_control_answer_decision` - `mission_control_get_handoff` - `mission_control_get_handoff_summary` - `mission_control_get_event_digest` ## Mission Control resources it may read - `mission-control://projects/current/summary` - `mission-control://projects/current/workspace` - `mission-control://projects/current/actions` - `mission-control://projects/current/manager/queue` ## Decisions that must be passed to the user - Which project or workspace Mission Control should operate on - Any manager clarification question that affects scope, risk, or priority - Any approval request before the decision tool is called - Whether to fall back to non-Mission-Control work if the bridge is unavailable ## Workflow 1. Prove the Mission Control bridge surface before guessing: - prefer the named `mission_control_*` tools when the session exposes them - if tool exposure is unclear, verify MCP registration or resource vi