@open-agent-toolkit/cli 0.2.59 → 0.2.62

package/assets/docs/workflows/skills/index.md

@@ -18,7 +18,7 @@ Use this section when you want to choose the right OAT skill for a task. If you
 
 ## Key Skills by Use Case
 
-- Start a new tracked project: `oat-project-new` or `oat-project-quick-start` (quick start accepts a project name plus optional description; if you omit the description it should ask before discovery begins)
+- Start a new tracked project: `oat-project-new`, `oat-project-quick-start`, or `oat-project-lite` for a single-sitting change with one batched interview and one approval (quick start accepts a project name plus optional description; if you omit the description it should ask before discovery begins)
 - Resume an existing project: `oat-project-open` and `oat-project-progress`
 - Execute a ready plan: `oat-project-implement`
 - Import an existing plan: `oat-project-import-plan`
@@ -58,6 +58,7 @@ Use this section when you want to choose the right OAT skill for a task. If you
 
     - `oat-project-new`
     - `oat-project-quick-start`
+    - `oat-project-lite`
     - `oat-project-import-plan`
     - `oat-project-promote-spec-driven`
     - `oat-project-open`

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.2.59",
-  "docs-config": "0.2.59",
-  "docs-theme": "0.2.59",
-  "docs-transforms": "0.2.59"
+  "cli": "0.2.62",
+  "docs-config": "0.2.62",
+  "docs-theme": "0.2.62",
+  "docs-transforms": "0.2.62"
 }

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

@@ -1,6 +1,6 @@
 ---
 name: oat-brainstorm
-version: 1.3.5
+version: 1.3.6
 description: Use when the user explicitly invokes the `brainstorm` verb, including `/oat-brainstorm`, "let's brainstorm", "brainstorm this", "can we brainstorm X", or "help me brainstorm X". For ambiguous exploratory phrasing ("I've been thinking", "what if", "help me think through"), do NOT auto-enter; respond conversationally and offer mode only after ≥2 sustained exploratory turns. Do NOT use for review, debug, PR, status, implementation, or active-workflow questions.
 disable-model-invocation: false
 user-invocable: true
@@ -233,7 +233,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")
+  #   oat_workflow_mode → ACTIVE_PROJECT_MODE        (e.g., "spec-driven", "quick", "lite")
   #   oat_phase         → ACTIVE_PROJECT_PHASE       (e.g., "discovery", "design", "plan", "implement")
   #   oat_pr_status     → ACTIVE_PROJECT_PR_STATUS   (e.g., "none", "open", "closed")
 fi
@@ -396,8 +396,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 (`quick` vs `spec-driven`, with skill proposing a default based on the chosen direction and scope signals).
-  - Active-project fold-back → 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`, `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).
   - 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.
@@ -505,13 +505,50 @@ End mode assertion when the backlog-add hands control back.
 
 #### 9g — Promote to new OAT project
 
-The slug and workflow mode (`quick` vs `spec-driven`) were confirmed at step 8. Run:
+The slug and workflow mode (`lite`, `quick`, or `spec-driven`) were confirmed at
+step 8. Run:
 
 ```bash
 oat project new <slug> --mode <mode>
 ```
 
-This scaffolds the project directory under `.oat/projects/<scope>/<slug>/` with the standard core files (state.md, discovery.md, etc.).
+This scaffolds the project directory under `.oat/projects/<scope>/<slug>/` with
+the files owned by the selected mode.
+
+**Lite branch:** When mode is `lite`, use and preserve `<project>/plan.md` as
+the canonical artifact. Fill its `Summary`, `Decisions`, `Assumptions`, `Out of
+Scope`, and `Validation Criteria` sections from the synthesized payload without
+replacing an already populated section or the scaffolded `## Phase 1`. Do not
+create, write, or complete `discovery.md` or `design.md`. Set the project state
+to plan/in-progress with `oat_ready_for: oat-project-lite`, print the
+`oat-project-lite` handoff, and stop.
+
+Use this branch contract to validate the lite scaffold before the handoff:
+
+```bash
+# BEGIN LITE PROJECT PROMOTION CONTRACT
+if [ "$PROMOTION_MODE" = "lite" ]; then
+  LITE_PLAN_PATH="$PROMOTED_PROJECT/plan.md"
+  if [ ! -f "$LITE_PLAN_PATH" ]; then
+    mkdir -p "$PROMOTED_PROJECT"
+    printf '%s\n' '# Plan' '' '## Summary' '' '## Decisions' '' \
+      '## Assumptions' '' '## Out of Scope' '' '## Validation Criteria' '' \
+      '## Phase 1' > "$LITE_PLAN_PATH"
+  fi
+  if [ -e "$PROMOTED_PROJECT/discovery.md" ]; then
+    echo "oat: lite promotion must not create discovery.md" >&2
+    exit 64
+  fi
+  NEXT_SKILL="oat-project-lite"
+else
+  LITE_PLAN_PATH=""
+  NEXT_SKILL="oat-project-quick-start-or-design"
+fi
+# END LITE PROJECT PROMOTION CONTRACT
+```
+
+**Quick/spec-driven branch:** Only for those two modes, continue with the
+discovery flow below.
 
 Then **write a field-filled `discovery.md`** at `<project>/discovery.md` using the synthesized payload:
 
@@ -536,7 +573,7 @@ Print a pointer to the next skill, e.g.:
 
 **Stop here. Do NOT inline-execute the next phase.** The deliberate transition is the point — the user runs the next skill at their own pace.
 
-End mode assertion.
+End mode assertion after the selected branch stops.
 
 #### 9h — Active-project router (3-way picker)
 
@@ -556,14 +593,25 @@ 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 and quick 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, and lite 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.
 - `<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).
 
+Use this executable artifact-selection contract before confirming the path:
+
+```bash
+# BEGIN LITE FOLD-BACK CONTRACT
+if [ "$ACTIVE_PROJECT_MODE" = "lite" ]; then
+  ARTIFACT_PATH="$ACTIVE_PROJECT/plan.md"
+fi
+# END LITE FOLD-BACK CONTRACT
+```
+
 Confirm the chosen artifact with the user (minimal confirmation per `references/destinations.md`). Set `ARTIFACT_PATH` to the absolute path.
 
 **Persistence invariant:** shared and local project artifacts remain ordinary
@@ -602,7 +650,7 @@ beside another dirty project file must take Step 4.
    ## Brainstorming Update: YYYY-MM-DD — <topic>
    ```
 
-   Section body contains: `chosenDirection` (with rationale), key decisions (extracted from the conversation), and a transcript appendix (`transcriptSessionNote`). Optionally include `openQuestions` and `nextSteps` if surfaced.
+   Section body contains: `chosenDirection` (with rationale), key decisions (extracted from the conversation), and a transcript appendix (`transcriptSessionNote`). Optionally include `openQuestions` and `nextSteps` if surfaced. In lite mode, insert this section above `## Phase 1` in `plan.md` rather than appending after the task plan.
 
 2. Persist **only** the artifact under the scope guard:
 
@@ -621,7 +669,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 `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, 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).
 
@@ -695,7 +743,8 @@ 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` |
-| either      | open (`oat_pr_status: open`) | `oat-project-revise`      |
+| lite        | none / closed                | `oat-project-lite`        |
+| any mode    | open (`oat_pr_status: open`) | `oat-project-revise`      |
 
 Print the handoff prompt template, substituting `<skill-name>`, `<artifact>`, `<hash>`, and `<subject>` from the actual branch commit or synced push receipt:
 
@@ -771,6 +820,6 @@ End mode assertion when the split handoff completes or reports its own blocker.
 - ✅ 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.
 - ✅ 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-revise` (either 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-revise` (any mode, open PR).
 - ✅ 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-docs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-docs
-version: 1.0.1
+version: 1.0.2
 description: Use when a user asks questions about OAT workflows, CLI commands, skill authoring, configuration, or project lifecycle. Answers questions by reading locally-bundled OAT documentation.
 argument-hint: '[question]'
 disable-model-invocation: false
@@ -145,7 +145,7 @@ Based on the docs, here's how OAT project workflows work: [answer]
 You can read more in `guide/workflow/lifecycle.md`.
 
 Would you like me to:
-- Start a new project? (I'd invoke oat-project-quick-start)
+- Start a new project? (I'd invoke oat-project-lite for single-sitting work, or oat-project-quick-start for a larger quick workflow)
 - Check your current project status? (I'd read your active project's state.md)
 ```
 
@@ -158,22 +158,27 @@ Would you like me to:
 **Response:**
 
 ```
-To create a new OAT project, you have two main approaches:
+To create a new OAT project, you have three main approaches:
 
-1. **Quick mode** (recommended for most tasks):
+1. **Lite mode** (recommended for single-sitting changes):
+   oat-project-lite <project-name> "project description"
+
+2. **Quick mode** (recommended for larger bounded work):
    oat-project-quick-start <project-name> "project description"
 
-2. **Spec-driven mode** (for complex features):
+3. **Spec-driven mode** (for complex features):
    oat-project-new <project-name>
 
-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
+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
 project name, it should ask you for the missing project description
 before discovery starts.
 
 Both create a project directory under your projects root
 (default: .oat/projects/shared/<project-name>/) with standard artifacts:
-state.md, discovery.md, plan.md, and implementation.md.
+state.md, plan.md, and implementation.md; quick and spec-driven modes also use
+discovery.md.
 
 See: guide/workflow/lifecycle.md, guide/getting-started.md
 

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

@@ -1,6 +1,6 @@
 ---
 name: oat-doctor
-version: 1.2.0
+version: 1.2.1
 description: Use when you need to diagnose your OAT setup, check for outdated skills, identify misconfigurations, or get a summary of installed tools and config. Runs health checks and recommends corrective actions.
 argument-hint: '[--summary]'
 disable-model-invocation: true
@@ -174,7 +174,7 @@ it, and lists every skill that pack ships.
 - oat-project-capture, oat-project-clear-active, oat-project-complete
 - oat-project-design, oat-project-dispatch-subagents, oat-project-discover
 - oat-project-document, oat-project-implement, oat-project-import-plan
-- oat-project-new, oat-project-next, oat-project-open
+- oat-project-lite, oat-project-new, oat-project-next, oat-project-open
 - oat-project-plan, oat-project-plan-writing, oat-project-pr-final
 - oat-project-pr-progress, oat-project-progress, oat-project-promote-spec-driven
 - oat-project-quick-start, oat-project-reconcile, oat-project-retro
@@ -238,7 +238,7 @@ OAT ▸ DOCTOR SUMMARY
 | --------- | ------- | ------ | -------- |
 | core      | user    | 2/2    | current  |
 | docs      | project | 7/7    | current  |
-| workflows | project | 39/39  | current  |
+| workflows | project | 40/40  | current  |
 | ideas     | user    | 4/4    | current  |
 | project-management | project | 4/4 | current |
 | research  | project | 6/6    | current  |

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

@@ -1,6 +1,6 @@
 ---
 name: oat-pjm-review-backlog
-version: 1.6.0
+version: 1.6.1
 description: Use when prioritizing the file-backed repo backlog or evaluating roadmap alignment. Produces value-effort ratings, dependency mapping, execution recommendations, and an optional external-plan handoff.
 argument-hint: '[backlog-root] [--roadmap=<path>] [--output=<path>]'
 disable-model-invocation: true
@@ -255,7 +255,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-quick-start` vs `oat-project-new`), 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-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>` — executed in the same PR that ships the item, and (b) deletion of the handoff file (`git rm`) in that same PR.

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-autonomous
-version: 1.0.11
+version: 1.0.12
 description: Use when a user explicitly asks to run an OAT project autonomously end-to-end. Activates session-only autonomy, resumes the correct lifecycle phase, and drives the existing OAT skills through final PR or a reported boundary.
 argument-hint: '<goal | project-slug | ticket-ref>'
 disable-model-invocation: true
@@ -69,7 +69,7 @@ waits.
 
 - Setting the two autonomy environment variables for the current process tree.
 - Resolving project home and persisted entry state.
-- Selecting quick or spec-driven mode from the review-density rule.
+- Selecting lite, 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
@@ -165,7 +165,7 @@ 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-new` or
+Mode selection in Step 2 chooses `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
@@ -219,6 +219,7 @@ Select the earliest incomplete lifecycle owner:
 | Persisted state                                           | Route                                                       |
 | --------------------------------------------------------- | ----------------------------------------------------------- |
 | No project yet                                            | Continue to Step 2, then invoke the selected creation skill |
+| Lite plan incomplete                                      | `oat-project-lite`                                          |
 | 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`                                        |
@@ -239,6 +240,9 @@ For a new goal, choose mode as a rigor selector:
   independent review before implementation.
 - **Quick:** use when one independent bundled pre-implementation review of
   discovery, optional lightweight design, and plan provides sufficient rigor.
+- **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.
 
 Base the choice on uncertainty, integration risk, architecture decisions,
 reversibility, and review needs—not task count. Record the chosen mode and
@@ -246,10 +250,11 @@ 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 or `oat-project-quick-start` for
-quick mode: 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.
+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
+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.
 
 ### Step 2.5: Persist Autonomous Explainer Intent
 
@@ -436,7 +441,7 @@ On success, report:
 ```text
 Autonomous run: complete
 Project: {path}
-Workflow mode: {quick | spec-driven}
+Workflow mode: {lite | quick | spec-driven}
 Entry state: {phase}
 Phases executed: {list}
 Reviews: {scope → route, target, independence, record}
@@ -514,7 +519,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.
-- ✅ Quick/spec-driven selection, when needed, recorded a review-density
+- ✅ Lite/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