Mission control restore 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.
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-restore-planAssembled 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
Generate a rollback or restore plan from Mission Control state. Use when the user wants to know what would be reverted, what evidence would be preserved, and which destructive steps would still need approval before any restore action.
SKILL.md
1.9 KB, as published. Nobody here has run it
Mission Control Restore Plan
Purpose
Describe how rollback would work without executing it.
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 how to roll back safely.
- A risky change needs a restore plan.
- Recovery decisions need a concrete revert outline.
Workflow
- Review snapshot, handoff, and status state.
- Ask Mission Control for a restore or rollback plan if available.
- Summarize what would be reverted, what would remain, and which steps would need approval.
- Do not execute the restore in this skill.
Mission Control calls
Tools:
mission_control_request_snapshotmission_control_request_recovery_planmission_control_get_status
Resources:
mission-control://projects/{project_id}/handoffmission-control://projects/{project_id}/statusmission-control://projects/{project_id}/decision-ledger
User-facing output
- Explain the rollback target, affected files or milestones, evidence preservation, and approval gates for destructive steps.
- Keep it actionable enough for the user to decide.
Approval behavior
Any actual restore or revert remains behind explicit approval. This skill only prepares the plan.
Never do
- Do not execute restore steps.
- Do not understate destructive impact.
- Do not claim rollback coverage for unsnapshotted work.
Failure and fallback
If no restore-plan tool exists, build the plan from snapshot availability, handoff evidence, and current status, and mark the dedicated tool as expected or future.
Example invocation
Generate a restore plan in case the current change set goes bad.