Mission Control Brand And Communications
Purpose
Use Mission Control to produce communication drafts that respect audience, tone, claims, and evidence boundaries.
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 release notes, announcements, stakeholder updates, or internal comms.
- Brand tone or style constraints matter.
- Technical work needs an audience-specific summary.
Workflow
- Ask Mission Control to identify audience, tone, facts, claims, and source evidence.
- Draft the communication through the Manager workflow.
- Check for unsupported claims, secrets, or overpromising.
- Return the draft plus evidence notes and open questions.
Mission Control calls
Tools:
mission_control_start_taskmission_control_get_handoff_summary
Resources:
mission-control://projects/{project_id}/handoffmission-control://projects/{project_id}/decision-ledgermission-control://projects/{project_id}/status
User-facing output
- Provide the message draft, audience, tone assumptions, evidence sources, and unresolved claims.
Approval behavior
Ask before posting, emailing, publishing, or committing communications.
Never do
- Do not invent metrics, customer claims, or release guarantees.
- Do not leak internal paths, secrets, or private incident details.
- Do not turn uncertainty into marketing fog.
Failure and fallback
If evidence is thin, produce a draft marked as unverified and ask for source material.
Example invocation
Use Mission Control to draft a release announcement from the latest handoff.
1---2name: mission-control-brand-comms3description: Coordinate brand-guideline, internal-communications, announcement, and stakeholder-message work through Mission Control with tone, audience, and evidence constraints.4---56# Mission Control Brand And Communications78## Purpose910Use Mission Control to produce communication drafts that respect audience, tone, claims, and evidence boundaries.1112The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.1314## Use when1516- The user wants release notes, announcements, stakeholder updates, or internal comms.17- Brand tone or style constraints matter.18- Technical work needs an audience-specific summary.1920## Workflow21221. Ask Mission Control to identify audience, tone, facts, claims, and source evidence.232. Draft the communication through the Manager workflow.243. Check for unsupported claims, secrets, or overpromising.254. Return the draft plus evidence notes and open questions.2627## Mission Control calls2829Tools:30- `mission_control_start_task`31- `mission_control_get_handoff_summary`3233Resources:34- `mission-control://projects/{project_id}/handoff`35- `mission-control://projects/{project_id}/decision-ledger`36- `mission-control://projects/{project_id}/status`3738## User-facing output3940- Provide the message draft, audience, tone assumptions, evidence sources, and unresolved claims.4142## Approval behavior4344Ask before posting, emailing, publishing, or committing communications.4546## Never do4748- Do not invent metrics, customer claims, or release guarantees.49- Do not leak internal paths, secrets, or private incident details.50- Do not turn uncertainty into marketing fog.5152## Failure and fallback5354If evidence is thin, produce a draft marked as unverified and ask for source material.5556## Example invocation5758`Use Mission Control to draft a release announcement from the latest handoff.`
MN755