agentsclimarketplace

Mission control plan

Skill MN755/Codex-Mission_Control/plugins/mission-control/skills/mission-control-plan

An Open Source Platform For Building Projects With OpenAI's Codex, Claude CLI, And Other Coding LLMs Using Multi-Agent Swarms And Customizable Workflows. Runs On Windows, MacOS, And Linux.

Install
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Ask Mission Control Manager to create or revise a plan. Use when the user asks for a plan, scope changes, imported codebases need planning, or the next milestone and validation strategy need clarification before execution.

SKILL.md

2.1 KB, 385 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Plan

Purpose

Request a Mission Control plan or plan revision without taking over planning directly.

The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.

Use when

  • The user asks for a plan.
  • Scope changes require replanning.
  • A codebase was imported and needs structured milestones before execution.

Workflow

  1. Check current status and swarm plan resources first.
  2. Ask Mission Control Manager to create or revise the plan through mission_control_start_task or plan-specific workflow prompts.
  3. Return the plan summary with milestones, validation strategy, swarm strategy, and needed user decisions.
  4. If the plan implies approvals, surface them instead of auto-applying them.

Mission Control calls

Tools:

  • mission_control_get_status
  • mission_control_start_task

Resources:

  • mission-control://projects/{project_id}/status
  • mission-control://projects/{project_id}/swarm-plan
  • mission-control://projects/{project_id}/pending-decisions

User-facing output

  • Show goal, assumptions, milestones, validation strategy, swarm strategy, risks, and user decisions needed.
  • Call out whether the plan is new, revised, approved, or waiting on feedback.

Approval behavior

If the plan changes scope, cost, model policy, or swarm scale, get user approval before asking Mission Control to execute it.

Never do

  • Do not silently replace the Manager's plan with your own.
  • Do not claim approval status that Mission Control did not report.
  • Do not skip surfaced assumptions.

Failure and fallback

If plan-specific tooling is thin, use status and swarm resources to summarize current planning state and route the actual plan request through the Manager-led task flow.

Example invocation

Ask Mission Control Manager for a plan for this imported repo.

Gives 0 of the 12 instructions most roadmap strategy skills give in 385 tokens

Counted across 591 of the 672 authors here whose files we hold, read 2026-08-06

  • read product marketing context before asking questionsin 21 of 591, across 10 files
  • base price on perceived value, not costin 15 of 591, across 4 files
  • compact after finalizing a planin 14 of 591, across 9 files
  • differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
  • use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
  • use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
  • map topics to buyer journey stagesin 12 of 591, across 6 files
  • Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
  • Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
  • Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
  • Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
  • Open the strategic design template if neededin 11 of 591, across 1 file

Said here and by no other author read

  • check current status and swarm plan first
  • ask manager to create or revise the plan
  • return plan summary with milestones and validation
  • surface approvals instead of auto-applying them
  • get user approval for scope or cost changes
  • show plan goal assumptions milestones and risks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.