Submit a new mission for intake and routing — applies the three-question intake protocol, frames the brief, and designates an outcome orchestrator before any guild is activated.
Installs into .claude/skills of the current project.
Are you the author of Tess Add Mission?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/twiss-io-tess-add-mission)
---
name: tess-add-mission
description: "Submit a new mission for intake and routing — applies the three-question intake protocol, frames the brief, and designates an outcome orchestrator before any guild is activated."
---
<!-- Rendered by `tessctl render --target codex` from .tess/core/commands/add-mission.md. Regenerate; do not hand-edit. -->
Tess OS command `/add-mission`, packaged as an Agent Skill. Run it only when the user asks for it by name (`$tess-add-mission` in Codex).
`$ARGUMENTS` below stands for the text the user supplied with the request (expected: `[mission brief]`).
# /add-mission
Start a new mission with the brief: **$ARGUMENTS**
Run the intake-before-anything gate from [conductor/doctrine.md](../../../conductor/doctrine.md) and the routing doctrine in [conductor/mission-control.md](../../../conductor/mission-control.md):
1. **Three-question intake protocol** — classify (a) outcome type, (b) founder-level test, (c) domain test. See [conductor/outcome-orchestrators/README.md](../../../conductor/outcome-orchestrators/README.md).
2. **Frame the real mission** — state the decision/outcome required, not just the request as phrased.
3. **Produce the task graph** — decompose into nodes with dependency gates (research before build, crew before deploy, review before synthesis, verification before anything externally visible).
4. **Designate the outcome orchestrator** — apply the routing matrix and integration precedence in [conductor/outcome-orchestrators/integration.md](../../../conductor/outcome-orchestrators/integration.md).
5. **Confirm routing before activating any guild.** Propose the guild set; do not dispatch specialists until the framing is confirmed.
**Output:** mission brief, outcome type, assigned orchestrator, proposed guild set, state set to FRAMING ([conductor/mission-states.md](../../../conductor/mission-states.md)).
Report each dispatch to the operator in the active session per [conductor/guardrails.md](../../../conductor/guardrails.md) Rule 10. Remember Rule Zero: orchestrate and dispatch — never execute specialist work solo.
