<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/context/ops-vs-missions/">
  <id>https://docs.spec-kitty.ai/context/ops-vs-missions/</id>
  <title>Ops vs. Missions</title>
  <updated>2026-11-13T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/context/ops-vs-missions/"/>
  <summary>What separates a lightweight, governed ad-hoc Op from a full spec-to-consolidate Mission, and a concrete rule for choosing between them.</summary>
  <content type="html">&lt;span id=&quot;ops-vs-missions&quot;&gt;&lt;/span&gt;
&lt;p&gt;Spec Kitty has two distinct units of governed work. Confusing them is the single
most common source of “why didn’t this get tracked/reviewed/landed” confusion for
users past their first mission.&lt;/p&gt;
&lt;h2 id=&quot;the-two-units-of-work&quot;&gt;The two units of work&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;An Op&lt;/strong&gt; is a lightweight, governed ad-hoc invocation started with
&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch &quot;&amp;#x3C;request&gt;&quot;&lt;/code&gt;. It does &lt;strong&gt;not&lt;/strong&gt; create a mission, a spec, a
plan, a work package, a branch, or a worktree. Concretely, &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/dispatch.py&lt;/code&gt;):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Routes the request text to an agent profile via &lt;code dir=&quot;auto&quot;&gt;ActionRouter&lt;/code&gt; (or uses the
profile you pass with &lt;code dir=&quot;auto&quot;&gt;--profile&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Loads governance/Charter context for that &lt;code dir=&quot;auto&quot;&gt;(profile, action)&lt;/code&gt; pair.&lt;/li&gt;
&lt;li&gt;Opens an &lt;strong&gt;Op record&lt;/strong&gt; — a single append-only JSONL file at
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;invocation_id&gt;.jsonl&lt;/code&gt; — and writes a &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event with a fresh
ULID invocation ID.&lt;/li&gt;
&lt;li&gt;Returns synchronously with that context. It never spawns an LLM call itself;
the calling agent does the actual work.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The Op stays &lt;strong&gt;open&lt;/strong&gt; until you close it explicitly:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;profile-invocation&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;complete&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--invocation-id&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;&amp;#x3C;id&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--outcome&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;&amp;#x3C;done&lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;|&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;failed&lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;|&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;abandoned&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;That command appends a &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event to the same JSONL file (see
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/executor.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ProfileInvocationExecutor.invoke()&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;complete_invocation()&lt;/code&gt;). The record belongs to the checkout the command ran in
(the repository root checkout or a linked worktree). Unclosed Ops in every checkout
of the repository are surfaced by &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops&lt;/code&gt; and eventually swept to
&lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt;, each closure on the spine of the checkout that owns the record. There is no lane, no &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; state, and no
consolidation step — an Op is a single governed unit of work with a start event and an
end event, nothing else.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A Mission&lt;/strong&gt; is the canonical product term for a full spec-to-consolidate workflow
unit: specify → plan → tasks → implement → review → consolidate (accept, for some
mission types). Starting one (&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt;, which runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create&lt;/code&gt;) creates a
persistent mission directory under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission-slug&gt;/&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;, work-package files, and a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; carrying a durable
&lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;. Work packages move through the 9-lane status state machine
(&lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;
→ &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, with &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt; as side states), each transition is an
append-only event in &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; prepares
the work package’s workspace: a lane worktree and branch per execution lane for a
lanes topology, or the write checkout for a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission. A Mission is designed to
survive across many sessions, multiple agents, and a review/consolidation gate; an Op is
designed to be opened and closed inside a single turn of work.&lt;/p&gt;
&lt;h2 id=&quot;decision-rule&quot;&gt;Decision rule&lt;/h2&gt;
&lt;p&gt;The binding rule is shipped doctrine, not this page:
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-open-packs/blob/main/packs/built-in/directives/053-choose-op-or-mission-before-starting.directive.yaml&quot;&gt;DIRECTIVE_053 — Choose Op or Mission Before Starting&lt;/a&gt;
requires the choice to be made before work starts and re-checked while it runs.
It also requires every Op to be closed. The step-by-step heuristic that applies
the rule is the
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-open-packs/blob/main/packs/built-in/tactics/op-or-mission-selection.tactic.yaml&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;op-or-mission-selection&lt;/code&gt; tactic&lt;/a&gt;.
Activate both in a project with:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;activate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;directive&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;053-choose-op-or-mission-before-starting&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;charter&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;activate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;tactic&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;op-or-mission-selection&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;The table and heuristic below explain that rule. If they ever disagree with
the artifacts, the artifacts win.&lt;/p&gt;
&lt;p&gt;Use this table to decide before you start:&lt;/p&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;If your situation is…&lt;/th&gt;&lt;th&gt;Use&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;A one-off question, review, or piece of advice with no lasting spec/plan/code artifact to track&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Op&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt;)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;A small fix or task that doesn’t need a spec, a review gate, or multi-session tracking&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Op&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt;)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;You want the governance context (Charter, doctrine) injected once, synchronously, without opening a multi-step workflow&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Op&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt;)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The work needs a written spec, an implementation plan, discrete reviewable work packages, or will span more than one sitting&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Mission&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty.specify&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The work needs to be resumable by name/slug across sessions or by a different agent&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Mission&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The work needs an explicit review/approval gate before it lands&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Mission&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;A useful heuristic: if you can describe the entire task in one sentence and
expect it done in one sitting, it’s an Op. If you’d naturally want to write a
spec for it, or if “let’s continue this tomorrow” makes sense, it’s a Mission.&lt;/p&gt;
&lt;p&gt;The choice can change while you work. If an Op turns up work that is too
large to finish cleanly now, or that needs its own design pass (a spec, an
ADR or an operator decision), stop extending the Op. Close it with the
outcome of what you actually did, then carry the rest into a Mission or a
tracked follow-up. Don’t let the Op grow until the work is done.&lt;/p&gt;
&lt;p&gt;Ops and Missions are not mutually exclusive: a governed mission action (e.g.
&lt;code dir=&quot;auto&quot;&gt;spec-kitty next --agent &amp;#x3C;name&gt; --mission &amp;#x3C;slug&gt;&lt;/code&gt;) uses the same governed-context
model as &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt;. Both may write under &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt;, but the record kind
differs. &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt; opens a standalone &lt;strong&gt;per-invocation Op record&lt;/strong&gt; — its own
file at &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;invocation_id&gt;.jsonl&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/writer.py&lt;/code&gt;
/ &lt;code dir=&quot;auto&quot;&gt;executor.py&lt;/code&gt;) — that stays open until you explicitly close it with
&lt;code dir=&quot;auto&quot;&gt;profile-invocation complete&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; never opens one of those. It
instead writes paired &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; &lt;strong&gt;lifecycle records&lt;/strong&gt; — a
different schema, &lt;code dir=&quot;auto&quot;&gt;ProfileInvocationRecord&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/lifecycle.py&lt;/code&gt;). Each record is its own file,
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ulid&gt;.json&lt;/code&gt;, so two branches never edit the same lifecycle
file. The older shared &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl&lt;/code&gt; log is still read, never
written. A lifecycle record closes when &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; reports a result for
it. A record left open by an agent that stopped mid-action is closed by
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops --close-stale&lt;/code&gt;, which writes an &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt; record for
every one older than &lt;code dir=&quot;auto&quot;&gt;--threshold&lt;/code&gt; and does not advance the Mission (#7346).&lt;/p&gt;
&lt;h2 id=&quot;examples&quot;&gt;Examples&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Op&lt;/strong&gt; — a quick governed question, no mission created:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;dispatch&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;Review this implementation approach for the retry logic&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--profile&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;implementer-ivan&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# ... agent does the review inline ...&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;profile-invocation&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;complete&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--invocation-id&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;01J...&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--outcome&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;done&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Mission&lt;/strong&gt; — a full lifecycle reference, spanning multiple commands and
sessions:&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;/spec-kitty.specify&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;   &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# -&gt; kitty-specs/&amp;#x3C;mission-slug&gt;/spec.md&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;/spec-kitty.plan&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;       &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# -&gt; plan.md&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;/spec-kitty.tasks&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;      &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# -&gt; tasks.md + tasks/WP*.md&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;agent&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;action&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;implement&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;WP01&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--agent&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;&amp;#x3C;name&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;   &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# prepares the workspace, work begins&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# ... review, approve, repeat per WP ...&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;consolidate&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;   &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# lane consolidation into the Mission branch, then branch integration into the local target branch&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;For the mechanism behind governed dispatch in more depth, see
&lt;a href=&quot;/api/profile-invocation/&quot;&gt;Profile Invocation Reference&lt;/a&gt; (CLI flags and
trail fields) and
&lt;a href=&quot;/architecture/governed-profile-invocation/&quot;&gt;Understanding Governed Profile Invocation&lt;/a&gt;
(the &lt;code dir=&quot;auto&quot;&gt;(profile, action, governance-context)&lt;/code&gt; model). To choose which Mission
type to start, see &lt;a href=&quot;/context/mission-types/&quot;&gt;Mission Types&lt;/a&gt;.&lt;/p&gt;</content>
</entry>
