---
title: Missions
generated: true
---

<!-- Generated from docs/glossary.yml by tools/build-public-docs.mjs. Do not edit; edit the term. -->

# Missions

4 words that belong together: Mission, Analysis Mission, Execution Mission, Creation Mission.

## Mission

<video controls preload="metadata" width="640" src="https://images.stellarview.net/rudiments/mission-96a42a11.mp4"></video>

*Mission, in 47 seconds of a running system.*

**Plain word:** An automated workflow.

An orchestrated run in named phases. It keeps a full record of what the AI was asked and what it answered.

Related: [Replicant](/concepts/fleet) · [Tool](/01-start/claude-code) · [Mission Coordinator](/glossary#mission-coordinator) · [Mission Commander](/glossary#mission-commander) · [Away Mission](/concepts/fleet) · [GitHub Companion](/concepts/companion).

Where it is used: [Use it from Claude Code](/01-start/claude-code) · [Install](/01-start/install).

[In the glossary](/glossary#mission).

## Analysis Mission

**Plain word:** Requirements → design → test plan.

The workflow that turns an issue into a root cause, a design and a test plan before any code is written.

[In the glossary](/glossary#analysis-mission).

## Execution Mission

**Plain word:** Code generation through to pull request.

The workflow that takes an approved design and produces a branch, the implementation and a pull request.

[In the glossary](/glossary#execution-mission).

## Creation Mission

**Plain word:** Turn a rough idea into a written issue.

The workflow that takes a sentence or a voice note and produces a properly specified GitHub issue.

[In the glossary](/glossary#creation-mission).

