Missions

A mission is a time-boxed focus for your whole workspace: what you and your agents are pushing toward for the next few weeks. It spans every area in the workspace, and the intents under it say what has to change to get there.

What a mission holds

  • A name that says what the mission is about, such as "Ship the public beta".
  • An outcome: what is true when the mission is over, such as "Beta live for 50 customers".
  • A description and dates, when a deadline helps, including an end date.
  • Intents: the outcomes you agree with your agent on the way. An intent belongs to a mission, and its tasks reach the mission through it.

A task, an issue or an idea can also sit directly under a mission when it does not need an intent of its own. An item belongs either to an intent or straight to a mission, never to both.

One active mission at a time

Only one mission is active at a time. That is the point of a mission: it tells your agent where the workspace is heading right now.

When your agent looks for work, it picks tasks of the active mission first, then tasks of open intents, and only then the rest of the backlog by priority. When you ask it "what should we do next?", the active mission is where it looks.

To start a new mission while another one is active, finish or cancel the active one first.

Mission statuses

Status Meaning
new Created and waiting. Every mission starts here.
active The current focus of the workspace. Only one mission can be active.
completed The mission reached its outcome.
cancelled The mission was abandoned, with the reason recorded.

Every status change is recorded on the mission with a reason, so you can later see why a mission was closed or dropped.

Opening a mission

You do not fill in a form. Tell your agent what you want to focus on, and it creates the mission, proposes the intents that belong to it, and asks before activating it.

terminal
~/acme

 Let's start a mission for the next two weeks:
  get the public beta out to our first 50 customers.

Your agent: Created mission MS-b3t4qp "Ship the public beta"
  Outcome: beta live for 50 customers
  End date: 2026-10-08

No other mission is active. Activate it now?

 Yes. What intents does it need?

Your agent: Mission MS-b3t4qp is active.
Three intents would get us there:
  1. Self-serve sign-up without a sales call
  2. Invite links for teammates
  3. Usage limits for the beta plan
I recommend starting with 1: the other two assume
accounts already exist. Shall we brainstorm it?

Other ways to ask:

  • "Create a mission for the October release and link the billing intents to it."
  • "Which mission is active, and how far along are its intents?"
  • "Move the invite-links intent to the next mission."

Closing a mission

When the outcome is reached, ask your agent to complete the mission. Unfinished work does not have to die with it: your agent can move open intents and tasks to the next mission as it closes this one.

terminal
 The beta is live. Close the mission and move
  whatever is left to the next one.

Your agent: Mission MS-b3t4qp "Ship the public beta"
  3 intents: 2 done, 1 in build
Completed. The open intent "Usage limits for the
beta plan" moved to MS-q9rt2k "Beta feedback round".

If a mission stops making sense, cancel it instead. Your agent asks for the reason and records it on the mission.

  • "Cancel the pricing mission, we're dropping paid plans for now."
  • "Complete the beta mission and move its open tasks to the feedback mission."

Next

  • Intents: what an intent is and how you agree its outcomes.
  • The intent flow: how an intent moves from brainstorm to review.