Mission control review burst

Skill MN755/Codex-Mission_Control/.codex/skills/mission-control-review-burst

Use when Mission Control should recommend a bounded read-only review burst across correctness, security, testing, maintainability, and docs.From its SKILL.md

Install

npx -y skills add MN755/Codex-Mission_Control --skill mission-control-review-burst

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.

SKILL.md

1.8 KB, 351 tokens by cl100k_base, 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 review burst 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/recommend
GET /api/subagents/batches/{batch_id}
POST /api/subagents/batches/{batch_id}/results

Resources:

mission-control://projects/{project_id}/decision-ledger
mission-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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most review quality skills give in 351 tokens

Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-07

Ask questions one at a timein 81 of 1048, across 64 files
Provide a recommended answer for each questionin 73 of 1048, across 50 files
Explore the codebase instead of asking answerable questionsin 66 of 1048, across 42 files
Resolve dependencies between decisions one-by-onein 42 of 1048, across 17 files
Interview the user relentlessly about the planin 38 of 1048, across 13 files
Order findings by severityin 31 of 1048
Resolve each branch of the decision treein 27 of 1048, across 5 files
Run a grilling sessionin 26 of 1048, across 5 files
Update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 11 files
Propose precise canonical terms for vague languagein 25 of 1048, across 7 files
Create documentation files lazilyin 24 of 1048, across 5 files
Assign severity to every findingin 24 of 1048

Said here and by no other author read

check current status and scope
ask Mission Control for a review burst recommendation
surface any approval requirement
show proposed reviewers and expected outputs if approved
ingest burst results for manager follow-up
show review focus areas, burst size, risk, and approval posture

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.