agentsclimarketplace

Mission control continue handoff

Skill MN755/Codex-Mission_Control/.codex/skills/mission-control-continue-handoff

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-continue-handoff

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

Continue work after a Mission Control handoff without losing continuity. Use when the user wants another iteration, wants limitations preserved, or needs the next change request to build on the previous handoff and evidence.

SKILL.md

2.0 KB, 352 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Continue Handoff

Purpose

Continue from an existing handoff while preserving evidence and limitations.

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 wants to keep going after handoff.
  • A new milestone should build on the previous handoff.
  • Earlier evidence and limitations still matter.

Workflow

  1. Read the previous handoff first.
  2. Summarize preserved limitations, evidence, and unfinished work.
  3. Create a change request or next milestone through Mission Control.
  4. Track the new iteration without erasing the earlier handoff context.

Mission Control calls

Tools:

  • mission_control_get_handoff
  • mission_control_start_task
  • mission_control_get_status

Resources:

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

User-facing output

  • Show what carries over from the last handoff, what the new iteration changes, and what evidence must be refreshed.
  • Keep old and new scopes distinct.

Approval behavior

Any new change request that widens scope still requires normal approvals and user consent.

Never do

  • Do not lose the previous limitations.
  • Do not overwrite the narrative as if this is a fresh project.
  • Do not discard evidence history.

Failure and fallback

If no explicit continue-handoff workflow exists, use the prior handoff plus a change-request flow and make the continuity objective explicit in the task request.

Example invocation

Continue from the last Mission Control handoff and start the next iteration.

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.