Mission control review burst
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-review-burstAssembled 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
Use when Mission Control should recommend a bounded read-only review burst across correctness, security, testing, maintainability, and docs.
SKILL.md
1.8 KB, as published. Nobody here has run it
Mission Control Review Burst
Purpose
Ask Mission Control to split review work into bounded read-only Codex subagents.
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 a multi-angle review.
- The work is read-heavy and does not require coordinated edits.
- A single reviewer would be slower or less complete.
Workflow
- Check status and current scope.
- Ask Mission Control for a
reviewburst recommendation. - Surface any approval requirement.
- If approved, show the proposed reviewers and expected outputs.
- Ingest results for Manager follow-up.
Mission Control calls
Daemon/API:
POST /api/projects/{project_id}/subagent-bursts/recommendGET /api/subagents/batches/{batch_id}POST /api/subagents/batches/{batch_id}/results
Resources:
mission-control://projects/{project_id}/decision-ledgermission-control://projects/{project_id}/validation-summary
User-facing output
- Show review focus areas, burst size, risk, and approval posture.
- Return findings as summaries, not raw transcripts.
Approval behavior
Do not push a larger review burst through without answering the pending decision first.
Never do
- Do not let review bursts mutate code by default.
- Do not bypass approvals.
- Do not invent findings without cited evidence.
Failure and fallback
If burst planning is unavailable, fall back to a normal Mission Control review flow and say the burst path is unavailable.
Example invocation
Ask Mission Control whether a review burst makes sense for this change.