Mission control release prep

Skill MN755/Codex-Mission_Control/plugins/mission-control/skills/mission-control-release-prep

Prepare a project for release through Mission Control. Use when validation, docs, versioning, changelog, limitations, evidence, deployment readiness, and security concerns need one coordinated release-prep review.From its SKILL.md

Install

npx -y skills add MN755/Codex-Mission_Control --skill mission-control-release-prep

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

2.1 KB, 378 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Release Prep

Purpose

Coordinate release-prep review through Mission Control without skipping evidence or approvals.

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 if the project is ready to ship.
A release candidate needs a final checklist.
Docs, validation, and security all need coordinated review.

Workflow

Review handoff, validation, risk, and status resources.
Ask Mission Control for a release-prep pass if needed.
Summarize validation, docs, versioning, changelog, limitations, evidence, deployment readiness, and security concerns.
Surface any remaining approvals or blockers.

Mission Control calls

Tools:

mission_control_start_task
mission_control_get_handoff_summary
mission_control_get_status

Resources:

mission-control://projects/{project_id}/handoff
mission-control://projects/{project_id}/validation-summary
mission-control://projects/{project_id}/risk-register
mission-control://projects/{project_id}/status

User-facing output

Give a release-readiness summary and list unresolved blockers.
Be specific about whether versioning, changelog, docs, and security are complete or still thin.

Approval behavior

If release-prep implies deployments, publishing, or policy shifts, keep those actions behind explicit approvals.

Never do

Do not announce release readiness without evidence.
Do not skip limitations or unresolved risks.
Do not publish anything from chat directly.

Failure and fallback

If release-prep is not a dedicated workflow yet, synthesize the checklist from the available resources and clearly mark missing evidence.

Example invocation

Use Mission Control to do a release-prep review for this project.

What ships with it: 1 file

160 B alongside SKILL.md

agents/

openai.yaml160 B

Gives 0 of the 12 instructions most ship operate skills give in 378 tokens

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

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

Review handoff, validation, risk, and status resources
Ask Mission Control for a release-prep pass
Summarize validation, docs, versioning, and security
Surface any remaining approvals or blockers
Give a release-readiness summary
List unresolved blockers

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.