agentsclimarketplace

Mission control decision ledger

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-decision-ledger

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-decision-ledger

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

Show important Mission Control decisions and assumptions. Use when the user wants to review user decisions, Manager assumptions, auto-decisions, rejected options, or approval history without searching raw events.

SKILL.md

1.8 KB, as published. Nobody here has run it

Mission Control Decision Ledger

Purpose

Summarize the project decision ledger and assumption trail.

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 why a choice was made.
  • A plan or handoff should surface assumptions.
  • Approval history matters for auditability.

Workflow

  1. Read the decision-ledger resource and current status.
  2. Summarize user decisions, Manager assumptions, auto-decisions, rejected options, and approval history.
  3. If clarification is needed, point to the pending-decision or plan revision flow.

Mission Control calls

Tools:

  • mission_control_get_status

Resources:

  • mission-control://projects/{project_id}/decision-ledger
  • mission-control://projects/{project_id}/pending-decisions
  • mission-control://projects/{project_id}/status

User-facing output

  • List key decisions with impact and current status.
  • Highlight assumptions that are still provisional or unconfirmed.

Approval behavior

If the ledger shows unresolved decisions, route the user to the approval skill instead of guessing.

Never do

  • Do not rewrite history.
  • Do not flatten rejected options into accepted ones.
  • Do not hide assumptions that affect outcome quality.

Failure and fallback

If the resource returns no decision records, say that explicitly and avoid reconstructing history from pending decisions, plan state, or handoff notes alone.

Example invocation

Show the Mission Control decision ledger and assumptions.

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.