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
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-release-prepAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things 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.
- fetches URLsInstructs the agent to fetch 4 URLs, including mission-control://projects/{project_id}/handoff and 3 more.
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_taskmission_control_get_handoff_summarymission_control_get_status
Resources:
mission-control://projects/{project_id}/handoffmission-control://projects/{project_id}/validation-summarymission-control://projects/{project_id}/risk-registermission-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