@koda-sl/baker-cli 0.91.0 → 0.92.0

package/README.md

@@ -2361,6 +2361,37 @@ Permissions enforced server-side:
 
 ---
 
+### Missions (`baker missions`)
+
+A **Mission** groups an ordered set of actions (its "steps") under one goal, with a markdown **overview** (the human-readable plan). Use a mission whenever a request decomposes into 2+ ordered actions — audits, campaigns, multi-step plans. A single one-off capture stays a loose action.
+
+Mission write ops stage on the **same chat draft as actions** and apply atomically on the existing publish — there is no separate apply. `BAKER_CHAT_ID` must be set for every command except `list`/`get`.
+
+```bash
+# Open a mission (returns { ok, data: { missionTempId }, hints })
+baker missions create --title "Audit Google Ads" --overview "## Phase 1 — Pull data\n..."
+
+# Create the action steps in order, then attach each by 0-based --order.
+# Both --mission and --action accept a real id or a temp_* ref from the same draft.
+baker missions add-action --mission <id-or-missionTempId> --action <id-or-tempId> --order 0
+
+baker missions update <mission-id> --title "..." --overview "..."   # real id only
+baker missions set-status <mission-id> --status accomplished        # active | accomplished | aborted
+
+baker missions list [--include-aborted]   # per-mission progress (done/total) + ordered steps
+baker missions get <mission-id>
+```
+
+Rules:
+
+- **The overview is forward planning** — write it as numbered Phases (goal / what it produces / what unlocks next), with **no calendar framing** (dates, deadlines, ETAs) and **no effort framing** (quick-win, MVP, t-shirt sizes).
+- **Publishing the chat = the user approving the plan.** The mission and its ordered steps apply atomically; the dashboard then shows the mission grouped, ticking off as steps complete.
+- **Mark `accomplished` only when the goal is genuinely met**, `aborted` if abandoned — never auto-conclude from step status.
+- Hard dependencies between steps still go through `baker actions link`; missions (ordering) and dependencies (blocking) are orthogonal.
+- All staged mission ops revert automatically if the chat is discarded.
+
+---
+
 ### `baker schema [command]`
 
 Inspect command argument schemas for AI agent introspection.