@open-agent-toolkit/cli 0.3.18 → 0.3.20

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.3.18",
-  "docs-config": "0.3.18",
-  "docs-theme": "0.3.18",
-  "docs-transforms": "0.3.18"
+  "cli": "0.3.20",
+  "docs-config": "0.3.20",
+  "docs-theme": "0.3.20",
+  "docs-transforms": "0.3.20"
 }

package/assets/skills/oat-brainstorm/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: false
 user-invocable: true
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
 metadata:
-  version: 1.3.8
+  version: 1.3.10
 ---
 
 # Brainstorm
@@ -238,7 +238,7 @@ ACTIVE_PROJECT_PR_STATUS=""
 if [ -n "$ACTIVE_PROJECT" ] && [ -f "$ACTIVE_PROJECT/state.md" ]; then
   ACTIVE_PROJECT_VALID="true"
   # Read state.md frontmatter — extract:
-  #   oat_workflow_mode → ACTIVE_PROJECT_MODE        (e.g., "spec-driven", "quick", "lite")
+  #   oat_workflow_mode → ACTIVE_PROJECT_MODE        (e.g., "spec-driven", "quick", "import", "lite", "brief", "goal")
   #   oat_phase         → ACTIVE_PROJECT_PHASE       (e.g., "discovery", "design", "plan", "implement")
   #   oat_pr_status     → ACTIVE_PROJECT_PR_STATUS   (e.g., "none", "open", "closed")
 fi
@@ -401,8 +401,8 @@ The payload is staged in memory only — it is not persisted between conversatio
   - Capture as new idea → confirm slug.
   - Extend existing idea → confirm which idea (slug or path).
   - Doc-to-path → confirm path.
-  - Promote to new project → confirm slug + workflow mode (`lite`, `quick`, or `spec-driven`, with skill proposing a default based on the chosen direction and scope signals).
-  - Active-project fold-back → for lite confirm `plan.md`; otherwise confirm which artifact (`design.md` if exists, else `discovery.md`; user signal can override toward `discovery.md` for foundational changes).
+  - Promote to new project → confirm slug + workflow mode (`lite`, `brief`, `goal`, `quick`, or `spec-driven`, with skill proposing a default based on the chosen direction and scope signals; propose `goal` when the direction needs several deliveries over time).
+  - Active-project fold-back → for lite, brief, and goal confirm `plan.md`; for import confirm `design.md` or `discovery.md` when present, else `plan.md`; otherwise confirm which artifact (`design.md` if exists, else `discovery.md`; user signal can override toward `discovery.md` for foundational changes).
   - Active-project reference file → confirm filename (default `YYYY-MM-DD-<topic>.md`).
 
 - **`none`** (currently `Inline only` and `Summarize idea directly`): no per-field confirmation at this layer. For `Inline only`, write the closing summary directly. For `Summarize idea directly`, hand off — the downstream `oat-idea-summarize` surfaces its own summary for accept/refine review.
@@ -510,7 +510,7 @@ End mode assertion when the backlog-add hands control back.
 
 #### 9g — Promote to new OAT project
 
-The slug and workflow mode (`lite`, `quick`, or `spec-driven`) were confirmed at
+The slug and workflow mode (`lite`, `brief`, `goal`, `quick`, or `spec-driven`) were confirmed at
 step 8. Run:
 
 ```bash
@@ -552,6 +552,25 @@ fi
 # END LITE PROJECT PROMOTION CONTRACT
 ```
 
+**Brief branch:** When mode is `brief`, the scaffold holds `plan.md` (the
+`plan-brief` template), `implementation.md`, and `references/research/`, and
+no `discovery.md`. Write the synthesized payload (`summary`, `motivation`,
+`approachesConsidered`, `chosenDirection`, key decisions, `openQuestions`) to
+`<project>/references/research/brainstorm-YYYY-MM-DD.md` and leave `plan.md`
+as scaffolded: `oat-project-brief` authors the brief through its interview,
+reading that research first. Do not create `discovery.md` or `design.md`.
+Leave the project state at plan/in-progress, print the `oat-project-brief`
+handoff, and stop.
+
+**Goal branch:** When mode is `goal`, arrive exactly as the brief branch does:
+the goal scaffold holds the same files (its `plan.md` carries
+`oat_plan_source: goal` and the canonical Milestones table header). Write the
+synthesized payload to `<project>/references/research/brainstorm-YYYY-MM-DD.md`,
+leave `plan.md` as scaffolded for `oat-project-goal` to author through its
+interview (including the milestone split), do not create `discovery.md` or
+`design.md`, leave the project state at plan/in-progress, print the
+`oat-project-goal` handoff, and stop.
+
 **Quick/spec-driven branch:** Only for those two modes, continue with the
 discovery flow below.
 
@@ -598,11 +617,14 @@ The 3-way router fires once per session. After convergence resumes (e.g., the us
 
 #### 9i — Active project: fold-back to upstream artifact
 
-Uniform across spec-driven, quick, and lite modes. Differs only in which plan-authoring skill the handoff prompt addresses (resolved by `ACTIVE_PROJECT_MODE` and `ACTIVE_PROJECT_PR_STATUS`).
+Uniform across spec-driven, quick, import, lite, brief, and goal modes. Differs only in which plan-authoring skill the handoff prompt addresses (resolved by `ACTIVE_PROJECT_MODE` and `ACTIVE_PROJECT_PR_STATUS`).
 
 **Step 1 — Pick upstream artifact.** Prefer the most-specific existing one:
 
 - For lite, always select `<ACTIVE_PROJECT>/plan.md`. Append `## Brainstorming Update` immediately above `## Phase 1`; lite has no discovery or design artifact.
+- For brief, always select `<ACTIVE_PROJECT>/plan.md` (the Project Brief). Append `## Brainstorming Update` immediately above the first `## Phase` heading; brief has no discovery or design artifact, and the receiving skill folds the update into the brief's sections.
+- For goal, select `<ACTIVE_PROJECT>/plan.md` exactly as for brief; the update never edits the `## Milestones` table, which the receiving skill amends.
+- For import, use `design.md` or `discovery.md` when present (the rules below); otherwise `<ACTIVE_PROJECT>/plan.md`, because the import scaffold has neither.
 - `<ACTIVE_PROJECT>/design.md` if it exists (any mode — quick lightweight design counts).
 - Otherwise `<ACTIVE_PROJECT>/discovery.md`.
 - The user's signal during the conversation can override toward `discovery.md` even when `design.md` exists ("this is foundational" → discovery; "this is a design refinement" → design).
@@ -674,7 +696,7 @@ beside another dirty project file must take Step 4.
 
    For non-synced projects, use the explicit `--` filename form. **Never `git add -A`. Never directory globs.** Other working-tree paths are not touched by this commit. For synced projects, `FOLD_BACK_COMMIT_SHA` comes from the push JSON rather than the parent branch.
 
-3. `<artifact-basename>` is `plan.md` for lite, otherwise `design.md` or `discovery.md` depending on which was chosen. `<project-name>` is the active project's slug.
+3. `<artifact-basename>` is `plan.md` for lite, brief, and goal (and for import when it has no `design.md` or `discovery.md`), otherwise `design.md` or `discovery.md` depending on which was chosen. `<project-name>` is the active project's slug.
 
 4. If the guarded persistence succeeded → proceed to step 5 (handoff prompt).
 
@@ -749,8 +771,35 @@ Resolve the handoff target by `ACTIVE_PROJECT_MODE` and `ACTIVE_PROJECT_PR_STATU
 | spec-driven | none / closed                | `oat-project-plan`        |
 | quick       | none / closed                | `oat-project-quick-start` |
 | lite        | none / closed                | `oat-project-lite`        |
+| import      | none / closed                | `oat-project-import-plan` |
+| brief       | none / closed                | `oat-project-brief`       |
+| goal        | none / closed                | `oat-project-goal`        |
 | any mode    | open (`oat_pr_status: open`) | `oat-project-revise`      |
 
+For brief, `oat-project-brief` is the target while the brief is still in
+planning (`oat_phase: plan`); once implementation has started
+(`oat_phase: implement`), the target is `oat-project-implement`, which
+integrates the update as new or amended phases and stops for the brief's
+focused realignment when the update changes an Outcome, a Constraint, a
+Decision, the authority, the endpoint, or the agreed Approach. For brief, the
+prompt's last two sentences read "Integrate the new content into the brief as
+new or amended phases. Don't refresh the brief — preserve the review table and
+the journal." instead.
+
+For goal, `oat-project-goal` is the target: it folds the update into the
+brief as an amendment through its review ladder, during authoring or at the
+next re-alignment (`delivered`). While a milestone is active, an update that
+stays inside that milestone's approved Outcomes and Approach goes to
+`oat-project-implement` instead, which adds the new phases to the active
+milestone's `## Milestones` row; anything else waits for re-alignment. The
+prompt's last two sentences read as for brief.
+
+With an open PR in goal mode the open PR is a registered delivery, and
+`oat-project-revise` requires an explicit target. Name it in the prompt: add
+"Target: <mNN>/<dNN> (the open delivery)." after its first sentence, with the
+milestone and delivery IDs read from the `oat_deliveries` entry whose member
+URL is `oat_pr_url`.
+
 Print the handoff prompt template, substituting `<skill-name>`, `<artifact>`, `<hash>`, and `<subject>` from the actual branch commit or synced push receipt:
 
 ```
@@ -822,9 +871,9 @@ End mode assertion when the split handoff completes or reports its own blocker.
 - ✅ The terminal-state picker conditionally includes `Promote to N projects` only when `oat project split evaluate-signals` reports `triggered: true`; small-scope convergence keeps the option hidden.
 - ✅ Synthesis payload is built per the design Data Models `SynthesizedPayload` schema: `title`, `summary`, `motivation`, `vision`, `approachesConsidered[]`, `chosenDirection`, `openQuestions[]`, `nextSteps[]`, `transcriptSessionNote`.
 - ✅ Confirmation pattern matches `references/destinations.md`: `full` for scoped backlog item (field-by-field with example wording), `minimal` for slug/path/artifact destinations, `none` for inline-only and summarize-idea-directly.
-- ✅ Each handoff branch (9a-9k) reads the correct downstream `SKILL.md` path and enters at the documented step. Project promotion writes `discovery.md` only — never `design.md` — and does not auto-chain into the next phase.
+- ✅ Each handoff branch (9a-9k) reads the correct downstream `SKILL.md` path and enters at the documented step. Project promotion writes `discovery.md` for quick/spec-driven, `plan.md` for lite, and a `references/research/` note for brief and goal — never `design.md` — and does not auto-chain into the next phase.
 - ✅ Doc-to-path validation handles all four cases: path-is-directory, parent-missing (with explicit out-of-repo confirmation), file-already-exists (overwrite or rename), unwritable (surface OS error).
 - ✅ Fold-back persistence safety contract honored: preflight `git status --porcelain -- "$ARTIFACT_PATH"` runs before any artifact mutation; clean → append + exact-path branch commit for shared/local or validated `oat project push --json` for synced; dirty → three-option picker (persist-prior-first / mix / abort-to-reference-file); handoff prompt prints only after the scope-appropriate receipt succeeds.
-- ✅ Handoff target for fold-back resolves correctly per `oat_workflow_mode` + `oat_pr_status`: `oat-project-plan` (spec-driven, no/closed PR) / `oat-project-quick-start` (quick, no/closed PR) / `oat-project-lite` (lite, no/closed PR) / `oat-project-revise` (any mode, open PR).
+- ✅ Handoff target for fold-back resolves correctly per `oat_workflow_mode` + `oat_pr_status`: `oat-project-plan` (spec-driven, no/closed PR) / `oat-project-quick-start` (quick, no/closed PR) / `oat-project-lite` (lite, no/closed PR) / `oat-project-import-plan` (import, no/closed PR) / `oat-project-brief` or `oat-project-implement` (brief, no/closed PR, by phase) / `oat-project-goal` or `oat-project-implement` (goal, no/closed PR, by milestone state) / `oat-project-revise` (any mode, open PR; goal names the target delivery).
 - ✅ Active-project 3-way router (related / independent / supplementary) fires before the standard pack-filtered picker when both `WORKFLOWS_INSTALLED == "true"` and `ACTIVE_PROJECT_VALID == "true"`.
 - ✅ Skill validates cleanly under `pnpm oat:validate-skills` (frontmatter contract, allowed-tools, mode-assertion structure).

package/assets/skills/oat-brainstorm/references/destinations.md

@@ -122,8 +122,8 @@ Confirm to write this to a new backlog item file, or tell me what to change.
 **Required template fields:** `title`, `summary` (Initial Request), `approachesConsidered` (Solution Space), `chosenDirection` (Chosen Direction), key decisions, `openQuestions`. Template: `.oat/templates/discovery.md` (consumed via `oat project new`).
 **Optional template fields:** `motivation`, `vision`, `nextSteps`.
 **Confirmation pattern:** `minimal` (slug + workflow mode)
-Skill proposes `quick` vs `spec-driven` mode based on `chosenDirection` and scope signals from the conversation. User picks; skill confirms slug.
-**Handoff target:** Run `oat project new <slug> --mode <mode>` to scaffold. Write field-filled `discovery.md` only (Initial Request, Solution Space with approaches, Chosen Direction, Key Decisions, Open Questions). Mark `oat_status: complete`, `oat_ready_for: oat-project-quick-start` (for quick mode) or `oat-project-design` (for spec-driven). Update project `state.md` (phase=discovery, status=complete). Print pointer to next skill. **Stop — do NOT inline-execute the next phase.** Project promotion writes `discovery.md` only, never `design.md`.
+Skill proposes `lite`, `brief`, `goal`, `quick`, or `spec-driven` mode based on `chosenDirection` and scope signals from the conversation (`goal` when the direction needs several deliveries over time). User picks; skill confirms slug.
+**Handoff target:** Run `oat project new <slug> --mode <mode>` to scaffold. Write field-filled `discovery.md` only (Initial Request, Solution Space with approaches, Chosen Direction, Key Decisions, Open Questions). Mark `oat_status: complete`, `oat_ready_for: oat-project-quick-start` (for quick mode) or `oat-project-design` (for spec-driven). Update project `state.md` (phase=discovery, status=complete). Print pointer to next skill. **Stop — do NOT inline-execute the next phase.** Project promotion writes `discovery.md` only, never `design.md`. For `brief` mode there is no `discovery.md`: write the synthesized payload to `references/research/brainstorm-YYYY-MM-DD.md`, leave the scaffolded `plan.md` (the Project Brief) for `oat-project-brief` to author through its interview, keep state at plan/in-progress, and point to `oat-project-brief`. `goal` mode arrives the same way and points to `oat-project-goal`, which authors the brief and its milestone split. For `lite` mode, fill `plan.md` as `oat-brainstorm` step 9g describes and point to `oat-project-lite`.
 **If user wants to keep brainstorming after this is offered:** return to flow with destination = promote-to-new-project. Skill probes for missing chosen direction, key decisions, and explicit open questions — these become artifact fields that read poorly when shallow.
 
 ---
@@ -132,7 +132,7 @@ Skill proposes `quick` vs `spec-driven` mode based on `chosenDirection` and scop
 
 **Pack required:** `workflows` AND an active project pointer is set (`oat config get activeProject`) AND its `state.md` is readable.
 **Trigger phrases:** "fold this into the active project", "this is feedback for the active project", "integrate this into design", "add this to discovery", explicit "for the active project" mention. Also offered as the first option when the active-project 3-way router fires after convergence (related → fold-back).
-**Required template fields:** which artifact (`design.md` if exists, else `discovery.md`; user signal can override), the synthesized payload's `chosenDirection`, key decisions, `transcriptSessionNote` (transcript appendix). Template: appended in-place using `## Brainstorming Update: YYYY-MM-DD — <topic>` heading.
+**Required template fields:** which artifact (`plan.md` for lite, brief, and goal; for import `design.md` or `discovery.md` when present, else `plan.md`; otherwise `design.md` if exists, else `discovery.md`; user signal can override), the synthesized payload's `chosenDirection`, key decisions, `transcriptSessionNote` (transcript appendix). Template: appended in-place using `## Brainstorming Update: YYYY-MM-DD — <topic>` heading.
 **Optional template fields:** `openQuestions`, `nextSteps` — appended if surfaced during convergence.
 **Confirmation pattern:** `minimal` (which artifact + dirty-tree handling)
 
@@ -164,7 +164,15 @@ Skill name resolved per workflow mode + PR status (read from `state.md` frontmat
 | ----------- | ---------------------------- | ------------------------- |
 | spec-driven | none / closed                | `oat-project-plan`        |
 | quick       | none / closed                | `oat-project-quick-start` |
-| either      | open (`oat_pr_status: open`) | `oat-project-revise`      |
+| lite        | none / closed                | `oat-project-lite`        |
+| import      | none / closed                | `oat-project-import-plan` |
+| brief       | none / closed                | `oat-project-brief`       |
+| goal        | none / closed                | `oat-project-goal`        |
+| any mode    | open (`oat_pr_status: open`) | `oat-project-revise`      |
+
+For brief, `oat-project-brief` is the target while the brief is still in planning (`oat_phase: plan`) and `oat-project-implement` once implementation has started; the handoff prompt asks for new or amended phases instead of tasks.
+
+For goal, `oat-project-goal` is the target (an amendment during authoring or at re-alignment), or `oat-project-implement` for an update inside the active milestone's approved Outcomes and Approach. With an open PR, the goal handoff to `oat-project-revise` names the target milestone and delivery (`<mNN>/<dNN>`, from the `oat_deliveries` entry whose member URL is `oat_pr_url`), because revise requires an explicit target in goal mode.
 
 After printing the prompt, the skill stops. The user runs the plan-authoring skill at their own pace. The brainstorming skill never auto-chains into plan authoring — the deliberate transition is the point.
 

package/assets/skills/oat-docs/SKILL.md

@@ -6,7 +6,7 @@ disable-model-invocation: false
 user-invocable: true
 allowed-tools: Read, Glob, Grep, AskUserQuestion
 metadata:
-  version: 1.0.4
+  version: 1.0.6
 ---
 
 # OAT Docs
@@ -146,7 +146,7 @@ Based on the docs, here's how OAT project workflows work: [answer]
 You can read more in `workflows/projects/lifecycle.md`.
 
 Would you like me to:
-- Start a new project? (I'd invoke oat-project-lite for single-sitting work, or oat-project-quick-start for a larger quick workflow)
+- Start a new project? (I'd invoke oat-project-lite for single-sitting work, oat-project-brief for one delivery planned as a Project Brief, oat-project-goal for an outcome delivered over several milestones, or oat-project-quick-start for a larger quick workflow)
 - Check your current project status? (I'd read your active project's state.md)
 ```
 
@@ -170,9 +170,18 @@ To create a new OAT project, you have three main approaches:
 3. **Spec-driven mode** (for complex features):
    oat-project-new <project-name>
 
+Brief mode is a fourth option for one delivery whose design you can agree in
+conversation:
+   oat-project-brief <project-name> "project description"
+
+Goal mode is a fifth option for an outcome delivered over several milestones:
+   oat-project-goal <project-name> "project description"
+
 Lite combines the interview and requirements contract in one plan for a
-single sitting. Quick mode goes straight from discovery to plan. Spec-driven
-mode adds formal spec and design phases. If you invoke quick mode with only a
+single sitting. Brief writes one reviewed Project Brief whose phases carry
+intent and exit evidence instead of tasks; goal groups those phases into
+milestones that are delivered and re-aligned in turn. Quick mode goes straight from
+discovery to plan. Spec-driven mode adds formal spec and design phases. If you invoke quick mode with only a
 project name, it should ask you for the missing project description
 before discovery starts.
 

package/assets/skills/oat-pjm-review-backlog/SKILL.md

@@ -6,7 +6,7 @@ disable-model-invocation: true
 allowed-tools: Read, Write, Glob, Grep, Bash(git:*), AskUserQuestion, Task
 user-invocable: true
 metadata:
-  version: 1.6.3
+  version: 1.6.5
 ---
 
 # Review Backlog
@@ -256,7 +256,7 @@ This step mirrors the **Project Kickoff Handoffs** section of the pjm instructio
 **For each item in the agreed kickoff stack**, write or refresh `.oat/repo/pjm/handoffs/<BL-id>.md` with:
 
 - the backlog item reference — its ID **and** human-readable title **and** path (never a bare ID);
-- the recommended project mode (`oat-project-lite` for single-sitting work, `oat-project-quick-start` for quick work, or `oat-project-new` for spec-driven work), including which artifacts (spec/design/plan) to pre-populate from existing research when it exists;
+- the recommended project mode (`oat-project-lite` for single-sitting work, `oat-project-brief` for one delivery planned as a Project Brief, `oat-project-goal` for an outcome delivered over several milestones, `oat-project-quick-start` for quick work, or `oat-project-new` for spec-driven work), including which artifacts (spec/design/plan) to pre-populate from existing research when it exists;
 - authoritative input pointers (research directories, decision records, code paths);
 - repo conventions and verification gates the item file does not restate;
 - a close-out section requiring (a) the **Backlog Lifecycle** — `oat backlog archive <id> --summary "outcome" --json` — in the same PR that ships the item, and (b) filesystem deletion of its owned handoff. Consume the complete returned `affectedPaths`, append the tracked handoff deletion, format existing text with the repository command, and commit the exact list via `oat internal commit-paths` with a unique retained identity and enabled hooks; stop if unavailable or blocked/failed. Include both old/new item names, ledger, index and rewritten references; preserve unrelated staged/unstaged work.

package/assets/skills/oat-project-autonomous/SKILL.md

@@ -6,7 +6,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Task
 metadata:
-  version: 1.0.19
+  version: 1.0.21
 ---
 
 # Autonomous OAT Project
@@ -74,7 +74,7 @@ waits.
 
 - Setting the two autonomy environment variables for the current process tree.
 - Resolving project home and persisted entry state.
-- Selecting lite, quick, or spec-driven mode from the review-density rule.
+- Selecting lite, brief, quick, or spec-driven mode from the review-density rule.
 - Invoking existing OAT lifecycle and dispatch skills in their required order.
 - Auto-resolving only the gates authorized by the autonomy contract.
 - Selecting the first existing compatible dispatch-ladder config scope through
@@ -170,8 +170,9 @@ fi
 ```
 
 For a new goal, derive a safe project slug but do not hand-create the project.
-Mode selection in Step 2 chooses `oat-project-lite`, `oat-project-new`, or
-`oat-project-quick-start`, which owns scaffolding and pointer persistence. If
+Mode selection in Step 2 chooses `oat-project-brief`,
+`oat-project-lite`, `oat-project-new`, or `oat-project-quick-start`, which owns
+scaffolding and pointer persistence. If
 the input is empty, ambiguous, collides with another project, or resolves
 outside the target repository, stop at the applicable product-judgment or
 repository-policy boundary.
@@ -225,6 +226,8 @@ Select the earliest incomplete lifecycle owner:
 | --------------------------------------------------------- | ----------------------------------------------------------- |
 | No project yet                                            | Continue to Step 2, then invoke the selected creation skill |
 | Lite plan incomplete                                      | `oat-project-lite`                                          |
+| Brief not yet reviewed and approved                       | `oat-project-brief`                                         |
+| Existing goal project (`oat_workflow_mode: goal`)         | Stop at a product-judgment boundary: goal is not autonomous |
 | Quick-mode discovery, optional design, or plan incomplete | `oat-project-quick-start`                                   |
 | Spec-driven discovery incomplete                          | `oat-project-discover`                                      |
 | Spec-driven design/spec incomplete                        | `oat-project-design`                                        |
@@ -299,6 +302,15 @@ For a new goal, choose mode as a rigor selector:
 - **Lite:** use when the goal is a clear, single-sitting change whose interview,
   decisions, assumptions, and validation criteria fit one combined plan and one
   sequential implementation phase.
+- **Brief:** use when the goal is one delivery whose outcome and design can be
+  settled from evidence and recorded in one reviewed Project Brief, with
+  phases of intent and exit evidence instead of a pre-approved task plan.
+- **Goal is excluded.** Never select `goal` for a new project, even when the
+  outcome needs several deliveries: each milestone's approval, re-alignment
+  and the terminal declaration need the user (`GOAL-11` through `GOAL-13` in
+  the autonomy contract), so an autonomous run cannot carry a goal end to end.
+  Choose brief for the first delivery, or stop at a product-judgment boundary
+  when one delivery cannot honestly represent the outcome.
 
 Base the choice on uncertainty, integration risk, architecture decisions,
 reversibility, and review needs—not task count. Record the chosen mode and
@@ -306,8 +318,8 @@ evidence-based review-density rationale in the first owned project artifact.
 If evidence cannot support the choice without changing product intent, stop at
 a product-judgment boundary.
 
-Invoke `oat-project-new` for spec-driven mode, `oat-project-quick-start` for quick, or `oat-project-lite` for lite;
-these three entry routes own new-project setup. Load the selected creation
+Invoke `oat-project-new` for spec-driven mode, `oat-project-quick-start` for quick, `oat-project-lite` for lite, or `oat-project-brief` for brief;
+these four entry routes own new-project setup. Load the selected creation
 skill's current `SKILL.md` and follow it, or dispatch a child that carries it,
 never a remembered outcome. Existing projects retain their persisted workflow
 mode.
@@ -507,7 +519,7 @@ On success, report:
 ```text
 Autonomous run: complete
 Project: {path}
-Workflow mode: {lite | quick | spec-driven}
+Workflow mode: {lite | brief | quick | spec-driven}
 Entry state: {phase}
 Phases executed: {list}
 Reviews: {scope → route, target, independence, record}
@@ -585,7 +597,7 @@ reconciliation path. Do not guess or overwrite the tracker.
 - ✅ Both autonomy signals were active only for the current process tree.
 - ✅ The entry phase came from persisted OAT state and completed work was not
   replayed.
-- ✅ Lite/quick/spec-driven selection, when needed, recorded a review-density
+- ✅ Lite/brief/quick/spec-driven selection, when needed, recorded a review-density
   rationale.
 - ✅ External-integration research and evidence gaps were recorded.
 - ✅ Every required review has dispatch provenance and no accepted launch fell