syntaur 0.1.13 → 0.2.0

package/platforms/claude-code/skills/plan-assignment/SKILL.md

@@ -23,13 +23,13 @@ Optional notes from the user: $ARGUMENTS
 
 Read `.syntaur/context.json` from the current working directory.
 
-If the file does not exist, tell the user: "No active assignment found. Run `/grab-assignment <mission-slug>` first to claim an assignment."
+If the file does not exist, tell the user: "No active assignment found. Run `/grab-assignment <project-slug>` first to claim an assignment."
 
 Extract from the context file:
-- `missionSlug` -- the mission slug
+- `projectSlug` -- the project slug
 - `assignmentSlug` -- the assignment slug
 - `assignmentDir` -- absolute path to the assignment folder
-- `missionDir` -- absolute path to the mission folder
+- `projectDir` -- absolute path to the project folder
 - `workspaceRoot` -- absolute path to the workspace (may be null)
 
 ## Step 1.5: Load Playbooks
@@ -47,12 +47,12 @@ For each file found, read it and follow its directives. Playbooks may contain ru
 Read the following files to understand the assignment:
 
 1. Read `<assignmentDir>/assignment.md` -- extract the objective, acceptance criteria, context section, and any Q&A
-2. Read `<missionDir>/agent.md` -- extract conventions and boundaries
-3. Read `<missionDir>/claude.md` if it exists -- extract Claude-specific instructions
-4. Read `<missionDir>/mission.md` -- extract the mission goal for broader context
+2. Read `<projectDir>/agent.md` -- extract conventions and boundaries
+3. Read `<projectDir>/claude.md` if it exists -- extract Claude-specific instructions
+4. Read `<projectDir>/project.md` -- extract the project goal for broader context
 
 If the assignment has dependencies (`dependsOn` in frontmatter), read the handoff.md from each dependency's assignment folder for integration context:
-- `<missionDir>/assignments/<dep-slug>/handoff.md`
+- `<projectDir>/assignments/<dep-slug>/handoff.md`
 
 ## Step 3: Explore Workspace (if set)
 
@@ -72,9 +72,32 @@ If `workspaceRoot` is null, skip this step and note in the plan that no workspac
 
 ## Step 4: Write the Plan
 
-Read the existing `<assignmentDir>/plan.md` to see its current frontmatter structure. Preserve the YAML frontmatter fields (`assignment`, `status`, `created`, `updated`) and update the `updated` timestamp. Change the `status` field from `draft` to `in_progress` if it is still `draft`.
+Plans are versioned. The first plan for an assignment is `plan.md`; subsequent plans are `plan-v2.md`, `plan-v3.md`, etc. Each plan gets a linked entry in the `## Todos` section of `assignment.md`, and any prior active plan todo is marked superseded (never deleted).
 
-Replace the markdown body with a detailed implementation plan. The plan should include:
+### 4a. Determine the next plan filename
+
+Use Glob to list `<assignmentDir>/plan*.md`. Then:
+
+- If no plan files exist, the target is `plan.md` and the version label is "plan".
+- If `plan.md` exists but no `plan-v<N>.md`, the target is `plan-v2.md` and the version label is "plan v2".
+- Otherwise, pick the smallest `N >= 2` such that `plan-v<N>.md` does not exist. The version label is `plan v<N>`.
+
+Remember this `planFilename` and `versionLabel` for the remaining substeps.
+
+### 4b. Write the plan file
+
+Write `<assignmentDir>/<planFilename>` with standard plan frontmatter:
+
+```yaml
+---
+assignment: <assignmentSlug>
+status: draft
+created: "<nowTimestamp>"
+updated: "<nowTimestamp>"
+---
+```
+
+Then the markdown body should include:
 
 1. **Overview** -- one paragraph summarizing the approach
 2. **Tasks** -- numbered list of implementation tasks, each with:
@@ -86,7 +109,31 @@ Replace the markdown body with a detailed implementation plan. The plan should i
 4. **Risks and Open Questions** -- anything that might block or complicate implementation
 5. **Testing Strategy** -- how to verify the implementation works
 
-Write the plan using the Edit tool to update `<assignmentDir>/plan.md`. Preserve the existing frontmatter and replace only the body content.
+**Decision capture:** While planning, note any meaningful choices you make (library picks, schema design, architectural calls, rejected alternatives). Record each as a numbered entry in `<assignmentDir>/decision-record.md` with the format `## Decision N: <short title>` — fields: Status (proposed/accepted), Context, Decision, Consequences. Downstream assignments that depend on this one auto-load these decisions during `/grab-assignment`, so they pay off over time.
+
+If the target file already exists (only possible for `plan.md` on first re-run against a scaffolded-but-empty plan), preserve the frontmatter and replace only the body, flipping `status` from `draft` to `in_progress` and updating `updated`.
+
+### 4c. Update assignment.md Todos
+
+Read `<assignmentDir>/assignment.md` and locate the `## Todos` section.
+
+1. **Supersede prior plan todos.** Scan unchecked todo lines for any that match the pattern `- [ ] Execute [<label>](./plan.md)` or `- [ ] Execute [<label>](./plan-v<N>.md)`. For each match, rewrite the line as:
+
+   ```
+   - [x] ~~Execute [<label>](./<old-plan-filename>)~~ (superseded by <versionLabel>)
+   ```
+
+   Never delete the old line — preserve history.
+
+2. **Append the new plan todo.** Append a new line to the end of the `## Todos` section:
+
+   ```
+   - [ ] Execute [<versionLabel>](./<planFilename>)
+   ```
+
+3. **Missing section fallback.** If the `## Todos` section does not exist (legacy assignment predating this convention), insert it immediately after `## Acceptance Criteria` with a short guidance HTML comment followed by the new todo line. Match the template used by `/create-assignment`.
+
+Also update the assignment frontmatter `updated` timestamp.
 
 ## Step 5: Report to User
 

package/platforms/claude-code/skills/syntaur-protocol/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: syntaur-protocol
-description: This skill should be used when the user mentions "syntaur", "assignment", "mission", works with files under ~/.syntaur/, references assignment.md, plan.md, handoff.md, or discusses the Syntaur protocol, lifecycle states, or write boundaries.
+description: This skill should be used when the user mentions "syntaur", "assignment", "project", works with files under ~/.syntaur/, references assignment.md, plan.md, handoff.md, or discusses the Syntaur protocol, lifecycle states, or write boundaries.
 version: 0.1.0
 ---
 
@@ -14,16 +14,16 @@ You MUST respect file ownership boundaries. Violations will be blocked by the Pr
 
 ### Files you may WRITE:
 1. **Your assignment folder** -- only the assignment you are currently working on:
-   - `assignment.md`, `plan.md`, `scratchpad.md`, `handoff.md`, `decision-record.md`
-   - Path: `~/.syntaur/missions/<mission>/assignments/<your-assignment>/`
-2. **Shared resources and memories** at the mission level:
-   - `~/.syntaur/missions/<mission>/resources/<slug>.md`
-   - `~/.syntaur/missions/<mission>/memories/<slug>.md`
+   - `assignment.md`, `plan*.md` (0 or more versioned plan files), `scratchpad.md`, `handoff.md`, `decision-record.md`
+   - Path: `~/.syntaur/projects/<project>/assignments/<your-assignment>/`
+2. **Shared resources and memories** at the project level:
+   - `~/.syntaur/projects/<project>/resources/<slug>.md`
+   - `~/.syntaur/projects/<project>/memories/<slug>.md`
 3. **Your workspace** -- source code files within the workspace defined in your assignment's frontmatter (`workspace.worktreePath` or `workspace.repository`)
 4. **Context file** -- `.syntaur/context.json` in the current working directory
 
 ### Files you must NEVER write:
-1. `mission.md`, `agent.md`, `claude.md` -- human-authored, read-only
+1. `project.md`, `agent.md`, `claude.md` -- human-authored, read-only
 2. `manifest.md` -- derived, rebuilt by tooling
 3. Any file prefixed with `_` (`_index-*.md`, `_status.md`) -- derived
 4. Other agents' assignment folders
@@ -32,9 +32,9 @@ You MUST respect file ownership boundaries. Violations will be blocked by the Pr
 ## Current Assignment Context
 
 If `.syntaur/context.json` exists in the current working directory, read it to determine:
-- `missionSlug` -- which mission you are working on
+- `projectSlug` -- which project you are working on
 - `assignmentSlug` -- which assignment is yours
-- `missionDir` -- absolute path to the mission folder
+- `projectDir` -- absolute path to the project folder
 - `assignmentDir` -- absolute path to your assignment folder
 - `workspaceRoot` -- absolute path to your code workspace (if set)
 
@@ -47,13 +47,17 @@ For detailed protocol information, read these files:
 ## Lifecycle Commands
 
 Use the `syntaur` CLI for state transitions. Available commands:
-- `syntaur assign <slug> --agent <name> --mission <mission>` -- set assignee
-- `syntaur start <slug> --mission <mission>` -- pending -> in_progress
-- `syntaur review <slug> --mission <mission>` -- in_progress -> review
-- `syntaur complete <slug> --mission <mission>` -- in_progress/review -> completed
-- `syntaur block <slug> --mission <mission> --reason <text>` -- block an assignment
-- `syntaur unblock <slug> --mission <mission>` -- unblock
-- `syntaur fail <slug> --mission <mission>` -- mark as failed
+- `syntaur assign <slug> --agent <name> --project <project>` -- set assignee
+- `syntaur start <slug> --project <project>` -- pending -> in_progress
+- `syntaur review <slug> --project <project>` -- in_progress -> review
+- `syntaur complete <slug> --project <project>` -- in_progress/review -> completed
+- `syntaur block <slug> --project <project> --reason <text>` -- block an assignment
+- `syntaur unblock <slug> --project <project>` -- unblock
+- `syntaur fail <slug> --project <project>` -- mark as failed
+
+## Troubleshooting
+
+If Syntaur state looks inconsistent (missing files, stale manifests, unexpected hook blocks), run `syntaur doctor` to diagnose. The `/doctor-syntaur` slash command wraps it and helps interpret results.
 
 ## Playbooks
 
@@ -67,6 +71,6 @@ ls ~/.syntaur/playbooks/*.md 2>/dev/null
 
 - Assignment frontmatter is the single source of truth for state
 - Slugs are lowercase, hyphen-separated
-- Always read `agent.md` and `claude.md` at the mission level before starting work
+- Always read `agent.md` and `claude.md` at the project level before starting work
 - Add unanswered questions to the Q&A section of assignment.md (do not set status to blocked for questions)
 - Commit frequently with messages referencing the assignment slug

package/platforms/codex/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "syntaur",
   "version": "0.1.7",
-  "description": "Run Syntaur mission and assignment workflows from Codex, including claiming work, planning, completing handoffs, session tracking, and write-boundary enforcement.",
+  "description": "Run Syntaur project and assignment workflows from Codex, including claiming work, planning, completing handoffs, session tracking, and write-boundary enforcement.",
   "author": {
     "name": "Brennen"
   },
@@ -9,8 +9,8 @@
   "hooks": "./hooks.json",
   "interface": {
     "displayName": "Syntaur",
-    "shortDescription": "Mission and assignment workflows for Codex",
-    "longDescription": "Use Syntaur to create missions and assignments, claim work, keep plan and handoff records current, track Codex sessions, and enforce Syntaur write boundaries.",
+    "shortDescription": "Project and assignment workflows for Codex",
+    "longDescription": "Use Syntaur to create projects and assignments, claim work, keep plan and handoff records current, track Codex sessions, and enforce Syntaur write boundaries.",
     "developerName": "Brennen",
     "category": "Coding",
     "capabilities": [

package/platforms/codex/README.md

@@ -4,7 +4,7 @@ Syntaur plugin for OpenAI Codex. Installed automatically during `syntaur setup`.
 
 ## What's included
 
-- **Skills:** syntaur-protocol, create-mission, create-assignment, grab-assignment, plan-assignment, complete-assignment, track-session
+- **Skills:** syntaur-protocol, create-project, create-assignment, grab-assignment, plan-assignment, complete-assignment, track-session
 - **Hooks:** write boundary enforcement, session cleanup
 - **Commands:** track-session
 - **Agents:** syntaur-protocol (background)

package/platforms/codex/adapters/AGENTS.md.template

@@ -4,7 +4,7 @@ This is a reference template for the Codex and OpenCode adapters.
 
 The `syntaur setup-adapter codex` or `syntaur setup-adapter opencode`
 command generates `AGENTS.md` dynamically in your workspace with
-mission and assignment context filled in.
+project and assignment context filled in.
 
 The generated file now does two things:
 
@@ -12,5 +12,5 @@ The generated file now does two things:
 2. points Codex at the reusable Syntaur Codex plugin workflows (`syntaur-protocol`, `grab-assignment`, `plan-assignment`, `complete-assignment`, and related helpers) when that plugin is installed globally
 
 See the rendered output by running:
-  syntaur setup-adapter codex --mission <slug> --assignment <slug>
-  syntaur setup-adapter opencode --mission <slug> --assignment <slug>
+  syntaur setup-adapter codex --project <slug> --assignment <slug>
+  syntaur setup-adapter opencode --project <slug> --assignment <slug>

package/platforms/codex/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
   display_name: "Syntaur"
-  short_description: "Mission and assignment workflows for Codex"
-  default_prompt: "Use Syntaur to create missions and assignments, claim work, plan an assignment, or complete a handoff in the current workspace."
+  short_description: "Project and assignment workflows for Codex"
+  default_prompt: "Use Syntaur to create projects and assignments, claim work, plan an assignment, or complete a handoff in the current workspace."
 
 policy:
   allow_implicit_invocation: true

package/platforms/codex/agents/syntaur-operator.md

@@ -1,6 +1,6 @@
 ---
 name: syntaur-operator
-description: Specializes in the Syntaur CLI and protocol: mission and assignment scaffolding, claiming work, maintaining assignment records, planning, handoffs, session tracking, adapter setup, lifecycle transitions, and write-boundary enforcement. Use when working with ~/.syntaur/, assignment.md, plan.md, handoff.md, .syntaur/context.json, or the syntaur CLI.
+description: Specializes in the Syntaur CLI and protocol: project and assignment scaffolding, claiming work, maintaining assignment records, planning (versioned plan files), handoffs, session tracking, adapter setup, lifecycle transitions, and write-boundary enforcement. Use when working with ~/.syntaur/, assignment.md, plan*.md, handoff.md, .syntaur/context.json, or the syntaur CLI.
 ---
 
 You are the Syntaur Operator for Codex.
@@ -9,9 +9,9 @@ Your job is to work fluently within the Syntaur protocol without breaking owners
 
 ## Primary Responsibilities
 
-- Create missions and assignments with the `syntaur` CLI
+- Create projects and assignments with the `syntaur` CLI
 - Claim assignments and establish local assignment context
-- Keep `assignment.md`, `plan.md`, and `handoff.md` accurate during execution
+- Keep `assignment.md`, active plan files (`plan.md`, `plan-v2.md`, ...), and `handoff.md` accurate during execution
 - Track Codex sessions for the Syntaur dashboard
 - Set up Codex adapter instructions in the active workspace
 - Enforce Syntaur write boundaries and lifecycle rules
@@ -20,15 +20,15 @@ Your job is to work fluently within the Syntaur protocol without breaking owners
 
 When a task involves Syntaur:
 
-1. Determine whether the user needs mission creation, assignment creation, assignment execution, completion/handoff, or session tracking.
+1. Determine whether the user needs project creation, assignment creation, assignment execution, completion/handoff, or session tracking.
 2. If `.syntaur/context.json` exists in the current working directory, read it first.
 3. If working on a specific assignment, read these in order:
-   - `<missionDir>/manifest.md`
-   - `<missionDir>/agent.md`
-   - `<missionDir>/mission.md`
-   - `<missionDir>/claude.md` if it exists
+   - `<projectDir>/manifest.md`
+   - `<projectDir>/agent.md`
+   - `<projectDir>/project.md`
+   - `<projectDir>/claude.md` if it exists
    - `<assignmentDir>/assignment.md`
-   - `<assignmentDir>/plan.md`
+   - any `<assignmentDir>/plan*.md` files linked from active todos in the `## Todos` section
    - `<assignmentDir>/handoff.md`
 4. Resolve the workspace boundary from `.syntaur/context.json` or `assignment.md` frontmatter before editing code.
 
@@ -36,7 +36,7 @@ When a task involves Syntaur:
 
 ### Never write
 
-- `mission.md`
+- `project.md`
 - `agent.md`
 - `claude.md`
 - `manifest.md`
@@ -47,12 +47,12 @@ When a task involves Syntaur:
 
 - the current assignment folder only:
   - `assignment.md`
-  - `plan.md`
+  - `plan*.md` (0 or more versioned plan files, e.g., `plan.md`, `plan-v2.md`)
   - `scratchpad.md`
   - `handoff.md`
   - `decision-record.md`
-- mission `resources/*.md`
-- mission `memories/*.md`
+- project `resources/*.md`
+- project `memories/*.md`
 - `.syntaur/context.json` in the current working directory
 - source files inside the assignment workspace boundary
 
@@ -61,7 +61,8 @@ When a task involves Syntaur:
 - Assignment frontmatter is the single source of truth for assignment state.
 - Slugs are lowercase and hyphen-separated.
 - `pending` with unmet `dependsOn` means structural waiting. `blocked` means a real runtime obstacle and requires a `blockedReason`.
-- Update acceptance criteria checkboxes as work lands.
+- Update acceptance criteria and `## Todos` checkboxes as work lands.
+- When requirements shift, supersede the prior plan todo instead of rewriting the old plan file.
 - Keep the `## Progress` section in `assignment.md` current after meaningful milestones.
 - Append handoffs instead of replacing previous handoff entries.
 
@@ -69,38 +70,40 @@ When a task involves Syntaur:
 
 Use these commands directly when needed:
 
-- `syntaur create-mission "<title>" [--slug <slug>] [--dir <path>]`
-- `syntaur create-assignment "<title>" --mission <slug> [--slug <slug>] [--priority <level>] [--depends-on <slugs>] [--dir <path>]`
+- `syntaur create-project "<title>" [--slug <slug>] [--dir <path>]`
+- `syntaur create-assignment "<title>" --project <slug> [--slug <slug>] [--priority <level>] [--depends-on <slugs>] [--dir <path>]`
 - `syntaur create-assignment "<title>" --one-off [--slug <slug>] [--priority <level>] [--dir <path>]`
 - `syntaur setup [--yes] [--claude] [--codex] [--claude-dir <path>] [--codex-dir <path>] [--codex-marketplace-path <path>] [--dashboard]`
-- `syntaur assign <assignment-slug> --agent codex --mission <mission-slug>`
-- `syntaur start <assignment-slug> --mission <mission-slug>`
-- `syntaur review <assignment-slug> --mission <mission-slug>`
-- `syntaur complete <assignment-slug> --mission <mission-slug>`
-- `syntaur block <assignment-slug> --mission <mission-slug> --reason <text>`
-- `syntaur unblock <assignment-slug> --mission <mission-slug>`
-- `syntaur fail <assignment-slug> --mission <mission-slug>`
+- `syntaur assign <assignment-slug> --agent codex --project <project-slug>`
+- `syntaur start <assignment-slug> --project <project-slug>`
+- `syntaur review <assignment-slug> --project <project-slug>`
+- `syntaur complete <assignment-slug> --project <project-slug>`
+- `syntaur block <assignment-slug> --project <project-slug> --reason <text>`
+- `syntaur unblock <assignment-slug> --project <project-slug>`
+- `syntaur fail <assignment-slug> --project <project-slug>`
 - `syntaur uninstall [--all] [--yes]`
-- `syntaur track-session --mission <mission-slug> --assignment <assignment-slug> --agent codex --session-id <id> --path <cwd>`
-- `syntaur setup-adapter codex --mission <mission-slug> --assignment <assignment-slug>`
+- `syntaur track-session --project <project-slug> --assignment <assignment-slug> --agent codex --session-id <id> --path <cwd>`
+- `syntaur setup-adapter codex --project <project-slug> --assignment <assignment-slug>`
 
 ## Standard Workflows
 
 ### Claim an assignment
 
-1. Discover the mission and pending assignments.
+1. Discover the project and pending assignments.
 2. Run `syntaur assign ... --agent codex`.
 3. Run `syntaur start ...`.
 4. Create `.syntaur/context.json` in the working directory.
 5. Register the session with `syntaur track-session`.
-6. If needed, run `syntaur setup-adapter codex --mission <slug> --assignment <slug>`.
+6. If needed, run `syntaur setup-adapter codex --project <slug> --assignment <slug>`.
 
 ### Plan an assignment
 
-1. Read the assignment, mission instructions, and any dependency handoffs.
+1. Read the assignment, project instructions, and any dependency handoffs.
 2. Explore the workspace.
-3. Replace the body of `plan.md` with a concrete implementation plan.
-4. Keep `assignment.md` in sync with what is now known.
+3. Determine the next plan filename: `plan.md` if no `plan*.md` exists, otherwise the smallest unused `plan-v<N>.md` (N >= 2).
+4. Write the plan file with standard frontmatter (`assignment`, `status: draft`, `created`, `updated`) and body.
+5. Update `assignment.md`'s `## Todos` section: supersede any prior active plan todo (`- [x] ~~...~~ (superseded by plan-v<N>)`), then append a new `- [ ] Execute [<label>](./<planFilename>)` todo.
+6. Keep `assignment.md` in sync with what is now known.
 
 ### Complete an assignment
 

package/platforms/codex/references/file-ownership.md

@@ -6,9 +6,9 @@ Agents must never modify these files:
 
 | File | Location |
 |------|----------|
-| `mission.md` | `<mission>/mission.md` |
-| `agent.md` | `<mission>/agent.md` |
-| `claude.md` | `<mission>/claude.md` |
+| `project.md` | `<project>/project.md` |
+| `agent.md` | `<project>/agent.md` |
+| `claude.md` | `<project>/claude.md` |
 
 ## Agent-Writable (Your Assignment Folder Only)
 
@@ -16,20 +16,20 @@ You may only write to files inside your assigned assignment folder:
 
 | File | Purpose |
 |------|---------|
-| `assignment.md` | Assignment record and source of truth for state |
-| `plan.md` | Your implementation plan |
+| `assignment.md` | Assignment record and source of truth for state (includes `## Todos` checklist) |
+| `plan*.md` | Versioned implementation plans (optional, 0 or more: `plan.md`, `plan-v2.md`, ...) — each linked from a todo in `assignment.md` |
 | `scratchpad.md` | Working notes |
 | `handoff.md` | Append-only handoff log |
 | `decision-record.md` | Append-only decision log |
 
-Path pattern: `~/.syntaur/missions/<mission>/assignments/<your-assignment>/`
+Path pattern: `~/.syntaur/projects/<project>/assignments/<your-assignment>/`
 
 ## Shared-Writable
 
 | Location | Purpose |
 |----------|---------|
-| `<mission>/resources/<slug>.md` | Reference material |
-| `<mission>/memories/<slug>.md` | Learnings and reusable patterns |
+| `<project>/resources/<slug>.md` | Reference material |
+| `<project>/memories/<slug>.md` | Learnings and reusable patterns |
 
 ## Derived (Never Edit)
 

package/platforms/codex/references/protocol-summary.md

@@ -5,10 +5,10 @@
 ```
 ~/.syntaur/
   config.md
-  missions/
-    <mission-slug>/
+  projects/
+    <project-slug>/
       manifest.md            # Derived: root navigation (read-only)
-      mission.md             # Human-authored: mission overview (read-only)
+      project.md             # Human-authored: project overview (read-only)
       _index-assignments.md  # Derived (read-only)
       _index-plans.md        # Derived (read-only)
       _index-decisions.md    # Derived (read-only)
@@ -17,8 +17,8 @@
       agent.md               # Human-authored: universal agent instructions (read-only)
       assignments/
         <assignment-slug>/
-          assignment.md      # Agent-writable: source of truth for state
-          plan.md            # Agent-writable: implementation plan
+          assignment.md      # Agent-writable: source of truth for state (includes ## Todos checklist)
+          plan*.md           # Agent-writable: versioned implementation plans (optional, 0 or more: plan.md, plan-v2.md, ...)
           scratchpad.md      # Agent-writable: working notes
           handoff.md         # Agent-writable: append-only handoff log
           decision-record.md # Agent-writable: append-only decision log
@@ -28,6 +28,9 @@
       memories/
         _index.md            # Derived (read-only)
         <memory-slug>.md     # Shared-writable
+  playbooks/
+    manifest.md              # Derived: playbook listing (read-only)
+    <slug>.md                # User-authored: behavioral rules for agents
 ```
 
 ## Assignment Lifecycle
@@ -59,8 +62,10 @@
 ## Key Rules
 
 1. Assignment frontmatter is the single source of truth for assignment state.
-2. One folder per mission and one subfolder per assignment.
+2. One folder per project and one subfolder per assignment.
 3. Derived files are never edited manually.
 4. Slugs are lowercase and hyphen-separated.
 5. Dependencies are declared via `dependsOn` in assignment frontmatter.
 6. An assignment cannot transition from `pending` to `in_progress` while any dependency is not `completed`.
+7. The `## Todos` section in `assignment.md` is an informal markdown checklist. Items may be simple tasks or link to plan files. When a plan is superseded, mark the old todo: `- [x] ~~Execute [plan](./plan.md)~~ (superseded by plan-v2)` — never delete it.
+8. Playbooks in `~/.syntaur/playbooks/` define behavioral rules agents must follow. Read `manifest.md` for a summary, then read each referenced playbook before starting work.

package/platforms/codex/scripts/enforce-boundaries.sh

@@ -51,7 +51,7 @@ if [ ! -f "$CONTEXT_FILE" ]; then
 fi
 
 ASSIGNMENT_DIR=$(jq -r '.assignmentDir // empty' "$CONTEXT_FILE" 2>/dev/null)
-MISSION_DIR=$(jq -r '.missionDir // empty' "$CONTEXT_FILE" 2>/dev/null)
+MISSION_DIR=$(jq -r '.projectDir // empty' "$CONTEXT_FILE" 2>/dev/null)
 WORKSPACE_ROOT=$(jq -r '.workspaceRoot // empty' "$CONTEXT_FILE" 2>/dev/null)
 
 if [ -z "$ASSIGNMENT_DIR" ] || [ -z "$MISSION_DIR" ]; then
@@ -93,7 +93,7 @@ if [ -n "$WORKSPACE_ROOT" ] && [[ "$FILE_PATH" == "$WORKSPACE_ROOT"/* ]]; then
   allow_and_exit
 fi
 
-REASON="Syntaur write boundary violation: Cannot write to '$FILE_PATH'. Allowed paths: assignment dir ($ASSIGNMENT_DIR), mission resources/memories, workspace ($WORKSPACE_ROOT)."
+REASON="Syntaur write boundary violation: Cannot write to '$FILE_PATH'. Allowed paths: assignment dir ($ASSIGNMENT_DIR), project resources/memories, workspace ($WORKSPACE_ROOT)."
 REASON_ESCAPED=$(echo "$REASON" | jq -Rs '.' 2>/dev/null)
 if [ -z "$REASON_ESCAPED" ]; then
   REASON_ESCAPED="\"Syntaur write boundary violation\""

package/platforms/codex/scripts/session-cleanup.sh

@@ -24,7 +24,7 @@ if [ ! -f "$CONTEXT_FILE" ]; then
 fi
 
 SESSION_ID=$(jq -r '.sessionId // empty' "$CONTEXT_FILE" 2>/dev/null)
-MISSION_SLUG=$(jq -r '.missionSlug // empty' "$CONTEXT_FILE" 2>/dev/null)
+MISSION_SLUG=$(jq -r '.projectSlug // empty' "$CONTEXT_FILE" 2>/dev/null)
 
 if [ -z "$SESSION_ID" ] || [ -z "$MISSION_SLUG" ]; then
   exit 0
@@ -33,7 +33,7 @@ fi
 PORT=$(cat "$HOME/.syntaur/dashboard-port" 2>/dev/null || echo "4800")
 curl -sf -X PATCH "http://localhost:${PORT}/api/agent-sessions/${SESSION_ID}/status" \
   -H "Content-Type: application/json" \
-  -d "{\"status\": \"stopped\", \"missionSlug\": \"${MISSION_SLUG}\"}" \
+  -d "{\"status\": \"stopped\", \"projectSlug\": \"${MISSION_SLUG}\"}" \
   -o /dev/null 2>/dev/null || true
 
 exit 0

package/platforms/codex/skills/complete-assignment/SKILL.md

@@ -11,12 +11,12 @@ Write a handoff for the current Syntaur assignment and transition it to `review`
 
 User arguments: `$ARGUMENTS`
 
-If the user passed `--complete`, transition directly to `completed` only when all acceptance criteria are met. Otherwise transition to `review`.
+If the user passed `--complete`, transition directly to `completed` only when all acceptance criteria are met AND all todos are either checked or marked superseded. Otherwise transition to `review`.
 
 ## Workflow
 
 1. Read `.syntaur/context.json`. If it does not exist, tell the user there is no active assignment.
-2. Read `<assignmentDir>/assignment.md` and evaluate every item in the `## Acceptance Criteria` section.
+2. Read `<assignmentDir>/assignment.md` and evaluate every item in the `## Acceptance Criteria` section AND every item in the `## Todos` section. Superseded todos (marked `- [x] ~~...~~ (superseded by ...)`) count as resolved. If any acceptance criterion is unmet OR any todo is still `- [ ]` and not superseded, warn the user before proceeding.
 3. Read `<assignmentDir>/handoff.md` and append a new handoff entry using the protocol format:
 
 ```markdown
@@ -44,18 +44,18 @@ If the user passed `--complete`, transition directly to `completed` only when al
 4. Update the handoff frontmatter:
    - set `updated` to the current timestamp
    - increment `handoffCount`
-5. Update acceptance criteria checkboxes in `assignment.md` to match reality.
+5. Update acceptance criteria and todo checkboxes in `assignment.md` to match reality. Do NOT modify superseded todo lines (those matching `- [x] ~~...~~ (superseded by ...)`).
 6. If `.syntaur/context.json` includes `sessionId`, mark that session as completed through the dashboard API:
 
 ```bash
 curl -s -X PATCH "http://localhost:$(cat ~/.syntaur/dashboard-port 2>/dev/null || echo 4800)/api/agent-sessions/<session-id>/status" \
   -H "Content-Type: application/json" \
-  -d '{"status":"completed","missionSlug":"<mission-slug>"}'
+  -d '{"status":"completed","projectSlug":"<project-slug>"}'
 ```
 
 7. Transition the assignment:
-   - `syntaur complete <assignment-slug> --mission <mission-slug>` when `--complete` is allowed
-   - otherwise `syntaur review <assignment-slug> --mission <mission-slug>`
+   - `syntaur complete <assignment-slug> --project <project-slug>` when `--complete` is allowed
+   - otherwise `syntaur review <assignment-slug> --project <project-slug>`
 8. Delete `.syntaur/context.json`.
 9. Summarize:
    - new status

package/platforms/codex/skills/create-assignment/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: create-assignment
-description: Use when the user wants to create a new Syntaur assignment inside a mission or as a one-off mission plus assignment.
+description: Use when the user wants to create a new Syntaur assignment inside a project or as a one-off project plus assignment.
 ---
 
 # Create Assignment
@@ -14,7 +14,7 @@ User arguments: `$ARGUMENTS`
 Parse:
 
 - First positional argument: assignment title
-- `--mission <slug>` required unless `--one-off`
+- `--project <slug>` required unless `--one-off`
 - `--one-off` optional
 - `--slug <slug>` optional
 - `--priority <level>` optional, default `medium`
@@ -23,21 +23,22 @@ Parse:
 
 If no title was provided, ask the user for it.
 
-If neither `--mission` nor `--one-off` was provided, look for `.syntaur/context.json` in the current working directory. If present, default the mission to that context's `missionSlug` and tell the user you are using it.
+If neither `--project` nor `--one-off` was provided, look for `.syntaur/context.json` in the current working directory. If present, default the project to that context's `projectSlug` and tell the user you are using it.
 
 ## Workflow
 
 1. Run one of:
-   - `syntaur create-assignment "<title>" --mission <slug> [--slug <slug>] [--priority <level>] [--depends-on <slugs>] [--dir <path>]`
+   - `syntaur create-assignment "<title>" --project <slug> [--slug <slug>] [--priority <level>] [--depends-on <slugs>] [--dir <path>]`
    - `syntaur create-assignment "<title>" --one-off [--slug <slug>] [--priority <level>] [--dir <path>]`
 2. If the command fails, report the error and stop.
 3. Read the generated `assignment.md`.
 4. Summarize:
    - assignment slug
-   - mission slug
+   - project slug
    - priority
    - location
-   - created files: `assignment.md`, `plan.md`, `scratchpad.md`, `handoff.md`, `decision-record.md`
+   - created files: `assignment.md`, `scratchpad.md`, `handoff.md`, `decision-record.md` (plan files are NOT scaffolded — they are created on demand by `plan-assignment`)
 5. Suggest next steps:
-   - fill in the objective, context, and acceptance criteria
+   - fill in the objective, context, acceptance criteria, and any initial todos in the `## Todos` section
+   - or run `plan-assignment` to create a plan file and auto-append a linked todo to `## Todos`
    - run `grab-assignment` to claim it if work should begin now