@open-agent-toolkit/cli 0.2.58 → 0.2.62

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-capture
-version: 1.0.1
+version: 1.0.2
 description: Use when work happened outside the OAT project workflow and needs retroactive project tracking. Creates a full project from an existing branch and conversation context.
 disable-model-invocation: true
 user-invocable: true
@@ -24,7 +24,7 @@ Use when:
 Don't use when:
 
 - A project already exists for the current branch — use `oat-project-reconcile` instead
-- You haven't started any work yet — use `oat-project-quick-start` or `oat-project-new`
+- You haven't started any work yet — use `oat-project-lite` for single-sitting work, `oat-project-quick-start` for quick work, or `oat-project-new` for spec-driven work
 - You only need to map new commits to an existing plan — use `oat-project-reconcile`
 
 ## Prerequisites

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-design
-version: 2.3.3
+version: 2.3.4
 description: Use when discovery is complete and implementation-ready decisions are needed. Runs a collaborative, selective collaborative, or draft-and-review design flow, confirms requirements and produces both `spec.md` and `design.md`, and commits artifacts before the user-review gate.
 disable-model-invocation: true
 user-invocable: true
@@ -656,14 +656,19 @@ Wait for user response:
 After artifact finalization and any configured HiLL approval, run the configured
 gate as the last check before the completion boundary:
 
-1. Resolve the gate for this skill:
+1. Resolve the gate for this skill with project context:
 
    ```bash
-   oat gate resolve <this-skill> --json
+   oat gate resolve <this-skill> --project "$PROJECT_PATH" --json
    ```
 
-   If the command returns JSON `null`, no gate is configured; proceed directly
-   to the completion steps in Step 8 below.
+   Handle all three `resolution` values explicitly:
+   - `not_configured`: no gate is configured; proceed directly to the completion steps in Step 8 below.
+   - `configured`: continue with the steps below, executing `effectiveGate` exactly as configured.
+   - `configured_disabled_by_project`: unreachable for this skill. Per-project override keys are accepted only for `oat_gateable` skills, and this skill is not one, so a configured gate here applies to every project and no project override can disable it. Treat this value as an unexpected result and fail closed as unresolved.
+
+   A null, missing, malformed, or unrecognized result is an operational failure
+   that fails closed as unresolved. Never treat it as "no gate configured."
 
 2. Export the resolved project path into the command shell:
 

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

@@ -1,7 +1,7 @@
 ---
 name: oat-project-discover
-version: 2.2.3
-description: Use when the user explicitly asks to continue discovery for an active spec-driven OAT project — e.g. "continue discovery", "run discovery", or confirms a previously offered discovery step. Do NOT auto-invoke for new ideas or quick-mode projects. Gathers requirements and context before spec/design.
+version: 2.2.5
+description: Use when the user explicitly asks to continue discovery for an active spec-driven OAT project — e.g. "continue discovery", "run discovery", or confirms a previously offered discovery step. Do NOT auto-invoke for new ideas or quick/lite-mode projects. Gathers requirements and context before spec/design.
 disable-model-invocation: false
 user-invocable: true
 allowed-tools: Read, Write, Bash(git:*), Bash(oat:*), Bash(pnpm:*), Glob, Grep, AskUserQuestion
@@ -15,11 +15,11 @@ Gather requirements and understand the problem space through natural collaborati
 
 **Required:** Knowledge base must exist. If missing, run the `oat-repo-knowledge-index` skill first.
 
-**Required for model invocation:** An active spec-driven OAT project must already exist. If no active project exists, route to `oat-project-new` for spec-driven setup or `oat-project-quick-start` for quick workflow. If the active project is quick or import mode, decline this skill and route to the current mode's next step instead.
+**Required for model invocation:** An active spec-driven OAT project must already exist. If no active project exists, route to `oat-project-new` for spec-driven setup, `oat-project-quick-start` for quick workflow, or `oat-project-lite` for single-sitting lite work. If the active project is quick, import, or lite mode, decline this skill and route to the current mode's next step instead.
 
 ## Model Invocation Gate
 
-This skill is model-invokable only for explicit discovery-continuation asks on an active spec-driven project. Do NOT auto-invoke when the user mentions a new idea, asks for a quick workflow, or has an active quick/import project.
+This skill is model-invokable only for explicit discovery-continuation asks on an active spec-driven project. Do NOT auto-invoke when the user mentions a new idea, asks for a quick or lite workflow, or has an active quick/import/lite project.
 
 Before acting:
 
@@ -27,7 +27,7 @@ Before acting:
 2. Confirm `{PROJECT_PATH}/state.md` exists.
 3. Confirm `oat_workflow_mode` is `spec-driven` or absent only in a legacy spec-driven project.
 
-If any check fails, decline this skill. Offer `oat-project-new` for a new spec-driven project, `oat-project-quick-start` for a quick project, or `oat-project-open` for switching to an existing project. When the gate passes, summarize the active project and ask before continuing discovery.
+If any check fails, decline this skill. Offer `oat-project-new` for a new spec-driven project, `oat-project-quick-start` for a quick project, `oat-project-lite` for single-sitting work, or `oat-project-open` for switching to an existing project. When the gate passes, summarize the active project and ask before continuing discovery.
 
 ## Mode Assertion
 
@@ -101,6 +101,7 @@ PROJECTS_ROOT="${PROJECTS_ROOT%/}"
 - Read `oat_workflow_mode` from `{PROJECT_PATH}/state.md`
 - If `oat_workflow_mode` is present and not `spec-driven`, stop and route:
   - quick project: continue with `oat-project-quick-start` / `oat-project-progress`
+  - lite project: continue with `oat-project-lite` / `oat-project-progress`
   - import project: continue with `oat-project-import-plan` / `oat-project-progress`
 - Ask user:
   - **Continue** with active project, or
@@ -429,14 +430,19 @@ If discovery is not configured as a HiLL checkpoint, or user explicitly approves
 After artifact finalization and any configured HiLL approval, run the configured
 gate as the last check before the completion boundary:
 
-1. Resolve the gate for this skill:
+1. Resolve the gate for this skill with project context:
 
    ```bash
-   oat gate resolve <this-skill> --json
+   oat gate resolve <this-skill> --project "$PROJECT_PATH" --json
    ```
 
-   If the command returns JSON `null`, no gate is configured; proceed directly
-   to the completion steps in Step 13 below.
+   Handle all three `resolution` values explicitly:
+   - `not_configured`: no gate is configured; proceed directly to the completion steps in Step 13 below.
+   - `configured`: continue with the steps below, executing `effectiveGate` exactly as configured.
+   - `configured_disabled_by_project`: unreachable for this skill. Per-project override keys are accepted only for `oat_gateable` skills, and this skill is not one, so a configured gate here applies to every project and no project override can disable it. Treat this value as an unexpected result and fail closed as unresolved.
+
+   A null, missing, malformed, or unrecognized result is an operational failure
+   that fails closed as unresolved. Never treat it as "no gate configured."
 
 2. Export the resolved project path into the command shell:
 

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-document
-version: 1.8.1
+version: 1.8.2
 description: Use when the user requests or confirms documenting an active OAT project — e.g. "document the project", "update the docs", "run oat-project-document", or confirms a previously offered documentation run. Do NOT auto-invoke when implementation completes. Analyzes project artifacts, presents a documentation delta plan, and applies approved changes.
 argument-hint: '[project-path] [--auto]'
 disable-model-invocation: false
@@ -196,6 +196,16 @@ adoption could not be determined — the usual causes are `jq` missing from
 
 Read all available project artifacts to build an understanding of what was built.
 
+For `oat_workflow_mode: lite`, use the reduced artifact contract instead of
+the numbered artifact list below. Read the five `plan.md` sections `Summary`,
+`Decisions`, `Assumptions`, `Out of Scope`, and `Validation Criteria`, then read
+`implementation.md` task outcomes and `Final Summary (for PR/docs)` as the
+shipped results. A lite project accepts `discovery.md`, `spec.md`, and
+`design.md` as absent; do not read or require them. Build the documentation
+delta from what actually shipped and continue with code verification.
+
+For every other workflow mode, read the numbered artifact list below.
+
 **Read in order:**
 
 1. `$PROJECT_PATH/discovery.md` — initial requirements, key decisions, constraints