@open-agent-toolkit/cli 0.2.58 → 0.2.62

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-next
-version: 1.0.13
+version: 1.1.0
 description: Use when continuing work on the active OAT project. Reads project state, determines the next lifecycle action, and invokes the appropriate skill automatically.
 disable-model-invocation: true
 user-invocable: true
@@ -106,6 +106,7 @@ projects, and synced records whose detached checkout is absent.
 - **The `projects` array is empty:** Report error and suggest:
   - `oat-project-new` — Create a spec-driven project
   - `oat-project-quick-start` — Start a quick workflow project
+  - `oat-project-lite` — Start a lite workflow project
   - `oat-project-import-plan` — Import an external plan
   - **STOP.** Do not attempt routing.
 
@@ -124,15 +125,15 @@ projects, and synced records whose detached checkout is absent.
 
 Read `"$PROJECT_PATH/state.md"` frontmatter and extract:
 
-| Field                     | Used For                                                                     |
-| ------------------------- | ---------------------------------------------------------------------------- |
-| `oat_phase`               | Current lifecycle position (discovery, spec, design, plan, implement)        |
-| `oat_phase_status`        | Phase completion state (in_progress, complete, pr_open)                      |
-| `oat_workflow_mode`       | Routing table selection (spec-driven, quick, import). Default: `spec-driven` |
-| `oat_hill_checkpoints`    | Which phases require HiLL approval                                           |
-| `oat_hill_completed`      | Which HiLL gates have been passed                                            |
-| `oat_blockers`            | Informational warnings (not routing gates)                                   |
-| `oat_implement_exit_gate` | Whether the implementation exit gate is allowed and fresh                    |
+| Field                     | Used For                                                                           |
+| ------------------------- | ---------------------------------------------------------------------------------- |
+| `oat_phase`               | Current lifecycle position (discovery, spec, design, plan, implement)              |
+| `oat_phase_status`        | Phase completion state (in_progress, complete, pr_open)                            |
+| `oat_workflow_mode`       | Routing table selection (spec-driven, quick, import, lite). Default: `spec-driven` |
+| `oat_hill_checkpoints`    | Which phases require HiLL approval                                                 |
+| `oat_hill_completed`      | Which HiLL gates have been passed                                                  |
+| `oat_blockers`            | Informational warnings (not routing gates)                                         |
+| `oat_implement_exit_gate` | Whether the implementation exit gate is allowed and fresh                          |
 
 **If state.md is missing or unreadable:** Report error and suggest running the relevant phase skill directly. STOP.
 
@@ -256,6 +257,15 @@ Otherwise, look up the target skill from the routing table for the current `oat_
 | plan          | complete     | tier 1        | `oat-project-implement` \* |
 | implement     | in_progress  | —             | `oat-project-implement` \* |
 
+**Lite Mode:**
+
+| Current Phase | Phase Status | Boundary Tier | Target Skill               |
+| ------------- | ------------ | ------------- | -------------------------- |
+| plan          | in_progress  | tier 3        | `oat-project-lite`         |
+| plan          | in_progress  | tier 2        | `oat-project-implement` \* |
+| plan          | complete     | tier 1        | `oat-project-implement` \* |
+| implement     | in_progress  | —             | `oat-project-implement` \* |
+
 \* `oat-project-implement` handles both sequential and parallel execution.
 
 ### Step 4: Check for Unprocessed Reviews (Review Safety Check)
@@ -302,7 +312,8 @@ unresolved or stale — resume with `oat-project-implement` before
 post-implementation routing."
 
 Only an `allowed` and fresh exit-gate disposition falls through to the normal
-post-implementation checks.
+post-implementation checks. Every other combination keeps its current
+fail-closed routing.
 
 Validate freshness from the complete persisted transition, not from `status`
 alone:
@@ -316,6 +327,32 @@ alone:
   `implementation_fingerprint`, configured gate-run provenance, and any eligible
   receive durably completed. Qualified state also requires the complete rolling
   freshness fields.
+- `allowed/configured` with `disposition: project_disabled` is the third valid
+  combination. Null gate-run and artifact provenance is required here, not
+  merely tolerated: nothing launched, so any non-null launch provenance is
+  contradictory and fails closed. It additionally requires a matching
+  `config_fingerprint`, `reviewed_head`, and `implementation_fingerprint`, a
+  `project_override` sub-record recording the disabled value and its
+  `state.md:oat_skill_gate_overrides` source, and the same rolling-freshness
+  rules as every other allowed result. The complete accepted shape is
+  `resolved_command` set to the configured command, `launch_state:
+not_started`, null `launch_attempt_id`, `launch_started_at`,
+  `launch_result_receipt`, `gate_run_marker`, `gate_run_id`, `envelope_status`,
+  `artifact`, and `handoff`, plus `receive_state: not_started`,
+  `receive_correlation`, `receive_source_artifact`,
+  `receive_archived_artifact`, `receive_event_identity`, `receive_pre_head`,
+  and `receive_commit` all null, `receive_eligible: false`,
+  `receive_completed: false`, `attempts_completed: 0`, and `failure: null`.
+  Any populated launch, receive, attempt, or failure field contradicts a gate
+  that never ran and fails closed.
+- Because the override lives in the state carrier the implementation
+  fingerprint excludes, a persisted `project_disabled` result is never accepted
+  on its stored value alone. Re-resolve the gate with project context and
+  require that the current resolution is still `configured_disabled_by_project`
+  and that `config_fingerprint` recomputed from that current resolution equals
+  the persisted one. A re-enabled gate changes the resolution and the
+  fingerprint, so an override-era transition routes as stale and a fresh
+  configured run is required.
 - `pending`, `blocked`, malformed, contradictory, or legacy-absent state never
   falls through. Pending and blocked generations resume their persisted
   configuration; configuration-fingerprint mismatch fails closed.
@@ -397,6 +434,12 @@ Ignore matching rows outside `REVIEWS_SECTION`; they are not review events.
 - If `FINAL_ROW` has `Status="passed"`:
   → Continue to 5.5
 
+**Lite closeout route:** If `oat_workflow_mode: lite`, a passed final review
+routes directly to `oat-project-pr-final` before the summary check below.
+Announce: "Final review passed — creating final PR". Optional lite summary or
+documentation work is owned by the immutable implementation closeout snapshot,
+not this fallback router.
+
 **5.5: Summary not done**
 
 Read `{PROJECT_PATH}/summary.md`:

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-plan
-version: 1.4.7
+version: 1.4.9
 description: Use when design.md is complete and executable implementation tasks are needed. Breaks design into bite-sized TDD tasks in canonical plan.md format.
 oat_gateable: true
 disable-model-invocation: true
@@ -14,13 +14,16 @@ Transform detailed design into an executable implementation plan with bite-sized
 
 ## Prerequisites
 
-This skill is the plan authoring path for **spec-driven** projects only. Quick and import modes have dedicated entry skills that produce `plan.md` directly.
+This skill is the plan authoring path for **spec-driven** projects only. Quick,
+import, and lite modes have dedicated entry skills that produce `plan.md`
+directly.
 
 Read `oat_workflow_mode` from `{PROJECT_PATH}/state.md` (default: `spec-driven`):
 
 - **`spec-driven`**: Complete design document required (`design.md` with `oat_status: complete`). If missing, **Stop.** Tell the user: "Run the `oat-project-design` skill first, then return to planning." Otherwise proceed with planning.
 - **`quick`**: **Stop.** Plan is already produced by the quick workflow. Tell the user: "Plan already produced by quick workflow. Run `oat-project-implement` to begin execution."
 - **`import`**: **Stop.** If a normalized `plan.md` exists, tell the user: "Imported plan is ready. Run `oat-project-implement` to begin execution." If no `plan.md` exists, tell the user: "Run `oat-project-import-plan` to import and normalize the external plan first."
+- **`lite`**: **Stop.** Tell the user: "Lite planning is owned by `oat-project-lite`; run it to author or resume the combined plan contract."
 
 ## Plan Format Contract
 
@@ -119,6 +122,15 @@ WORKFLOW_MODE=$(oat project status --field project.workflowMode 2>/dev/null || e
 
 Exit skill.
 
+**Mode: `lite`** — **STOP.** Print:
+
+```
+⚠️  This project uses lite mode. Run `oat-project-lite` to author or resume
+    its combined requirements and single-phase plan.
+```
+
+Exit skill.
+
 **Mode: `import`** — **STOP.** Check if `"$PROJECT_PATH/plan.md"` exists:
 
 - If yes: Print: "Imported plan is ready. Run `oat-project-implement` to begin execution."
@@ -483,6 +495,25 @@ This Phase gate review setup is independent from HiLL checkpoints. Do not read o
 change HiLL fields here, and do not add a provider/model `--target` to any
 lifecycle command.
 
+### Step 12.35: Configure Lifecycle Gate Posture
+
+After the confirmed plan has stable phase IDs and before Step 12.5 starts the
+plan artifact review, invoke the `Shared Lifecycle Gate Posture Setup Contract` from
+`oat-project-plan-writing`: load the current
+`oat-project-plan-writing/SKILL.md` and follow that contract as written. This
+runs adjacent to, but independently from, the phase gate review setup above.
+
+If `"$PROJECT_PATH/state.md"` already contains an explicit
+`oat_skill_gate_overrides` map, preserve it through the shared contract without
+probing, prompting, or mutation. Otherwise let the contract probe the configured
+gate-aware skills and offer a keep-or-disable choice for each configured gate
+independently.
+
+Persist only disabled choices, and only in `"$PROJECT_PATH/state.md"`. Keeping
+every gate leaves the map absent. Never modify the shared, local, or user
+configuration layers, and never prompt or write a new map in non-interactive
+mode.
+
 ### Step 12.5: Run Plan Artifact Review Loop
 
 Before dispatching the artifact reviewer, invoke the `Managed Dispatch
@@ -540,13 +571,19 @@ Apply the shared loop exactly:
 After the plan artifact is finalized and reviewed, 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_disabled_by_project`: the operator disabled this configured gate for this project. Do not launch any process. Emit `configured but disabled by project override`, including the project path and the `projectOverride` source from the envelope, then proceed directly to the completion steps in Step 13 below. A project-disabled gate never enters the passed, missing, or failed branches, and its `configuredGate` is evidence only, never executed.
+   - `configured`: continue with the steps below, executing `effectiveGate` exactly as configured.
+
+   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-plan-writing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-plan-writing
-version: 1.2.21
+version: 1.2.23
 description: Use when authoring or mutating plan.md in any OAT workflow. Defines canonical format invariants — stable task IDs, required sections, review table rules, and resume guardrails.
 disable-model-invocation: true
 user-invocable: false
@@ -86,7 +86,8 @@ then continue without formatting.
 ## Managed Dispatch Readiness and Review Contract
 
 All plan-producing workflows and their artifact reviews use this contract:
-spec-driven planning, quick-start, imported plans, and provider-plan-via-import.
+spec-driven planning, quick-start, lite planning, imported plans, and
+provider-plan-via-import.
 The contract runs before a plan becomes implementation-ready and immediately
 before each artifact review dispatch.
 
@@ -403,6 +404,100 @@ This setup is independent from HiLL checkpoints. It must not read or change
 choice is offered; normal lifecycle gate commands remain provider-neutral.
 They must not add a provider/model `--target` argument.
 
+## Shared Lifecycle Gate Posture Setup Contract
+
+Every plan-producing workflow invokes this procedure after the complete plan
+has stable phase IDs and before the plan artifact review begins, which is the
+same boundary the phase gate review setup uses. It runs adjacent to, but
+independently from, that setup: neither contract reads, writes, or
+satisfies the other's setting. The calling skill owns the prompt and the write
+to `"$PROJECT_PATH/state.md"`; this section owns the shared eligibility,
+preservation, validation, and non-interactive behavior.
+
+This contract governs the configured lifecycle gates declared with
+`oat_gateable: true` in skill frontmatter. It never reads or writes
+`oat_phase_review_gate`, HiLL policy, or any autonomous design-gate setting.
+
+### 1. Preserve an explicit existing map
+
+Inspect `"$PROJECT_PATH/state.md"` frontmatter before probing configuration. If
+an explicit `oat_skill_gate_overrides` key is present, preserve the complete
+value unchanged. Do not probe, prompt, or mutate it. This applies equally to
+resumed and imported projects. Report:
+
+```text
+Lifecycle gate posture: preserved existing oat_skill_gate_overrides setting.
+```
+
+A malformed map is never silently repaired, replaced, or dropped. Stop and
+report the offending project state path so the operator can correct it.
+
+### 2. Probe configured gate-aware skills
+
+When no explicit map exists, probe each gate-aware skill read-only. The probe
+resolves configuration and never launches a gate:
+
+```bash
+oat gate resolve <gate-aware-skill> --project "$PROJECT_PATH" --json
+```
+
+A gate qualifies for a choice only when `resolution` is literally `configured`.
+`not_configured` means no gate is configured for that skill: offer no choice and
+never fabricate configuration from an override alone.
+
+If the probe fails, emit exactly this concise warning and continue planning
+without writing a map:
+
+```text
+Warning: Lifecycle gate posture probe failed; configured gates remain enabled.
+```
+
+If no gate is configured, emit:
+
+```text
+Lifecycle gate posture: no configured lifecycle gates; nothing to disable.
+```
+
+### 3. Offer one choice per configured gate
+
+When at least one gate is configured and an interactive user-response channel is
+available, present each configured gate separately and let the user keep or
+disable it independently. Granularity is per skill; no single answer disables
+every gate at once.
+
+For each configured gate, show the skill name, its configured command, and the
+config source reported by the probe, then offer exactly these outcomes:
+
+1. **Keep** - run this configured gate for this project.
+2. **Disable** - skip this configured gate for this project only.
+
+Persist only the disabled choices, as a strict map whose sole permitted value is
+the literal `disabled`:
+
+```yaml
+oat_skill_gate_overrides:
+  oat-project-implement: disabled
+```
+
+Keeping every gate leaves the map absent; an explicitly empty map is equivalent.
+Never write an `enabled` value, a boolean, or a list. Write the map only to
+`"$PROJECT_PATH/state.md"`; the shared, local, and user configuration layers are
+never modified. Disabling here records project posture, not gate outcome: it
+never marks a gate passed, failed, or missing.
+
+### 4. Handle non-interactive planning
+
+Non-interactive mode includes `OAT_NON_INTERACTIVE=1` and any environment with
+no user-response channel. Never prompt in this mode, and never write a new map,
+even when configured gates exist. Leave the setting absent and emit:
+
+```text
+Lifecycle gate posture: configured gates unchanged (non-interactive; no selection recorded).
+```
+
+An explicit map that already exists is still preserved unchanged in this mode
+under section 1.
+
 ## Auto Artifact-Review Loop
 
 This is the canonical contract for bounded automated reviews of generated OAT artifacts. Calling skills own the concrete edits, progress indicators, and commits; this section defines the shared loop they must follow.
@@ -455,7 +550,7 @@ Every `plan.md` produced or edited by any OAT skill **must** satisfy these invar
 
 ```yaml
 ---
-oat_plan_source: spec-driven | quick | imported # origin workflow mode
+oat_plan_source: spec-driven | quick | imported | lite # origin workflow mode
 oat_status: in_progress | complete # plan lifecycle status
 oat_ready_for: null | oat-project-implement # downstream consumer
 # Optional after implementation confirmation:
@@ -559,10 +654,12 @@ Required inputs vary by workflow mode. The calling skill reads `oat_workflow_mod
 | `spec-driven` | Complete `design.md` (`oat_status: complete`)    | Yes         |
 | `quick`       | `discovery.md` + repo knowledge context          | No          |
 | `import`      | Preserved external source + normalized `plan.md` | No          |
+| `lite`        | `plan.md` only                                   | No          |
 
 - **`spec-driven`**: Plan is derived from a complete design document. All design components must be covered by tasks.
 - **`quick`**: Plan is generated directly from discovery decisions and repo knowledge. No design artifact is required.
 - **`import`**: External plan is preserved in `references/imported-plan.md` and normalized into canonical format. Subsequent edits follow this contract.
+- **`lite`**: `plan.md` is the sole requirements and implementation contract. It carries Summary, Decisions, Assumptions, Out of Scope, and Validation Criteria before one sequential phase; no discovery, spec, or design artifact is required.
 
 ## Resume and Edit Guardrails
 

package/assets/skills/oat-project-pr-final/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-pr-final
-version: 1.6.1
+version: 1.6.2
 description: Use when the user requests or confirms opening the final PR for an active OAT project — e.g. "open the final PR", "ship it", "run oat-project-pr-final", or confirms a previously offered final-PR step. Do NOT auto-invoke when phases are marked complete. Generates the final lifecycle PR description from artifacts and creates the PR.
 disable-model-invocation: false
 user-invocable: true
@@ -26,7 +26,8 @@ Generate a PR-ready summary grounded in canonical OAT artifacts, including:
 - `activeProject` in `.oat/config.local.json` points at an active project directory (or you can provide project name when prompted)
 - `{PROJECT_PATH}/plan.md` exists
 - In `spec-driven` mode: `{PROJECT_PATH}/spec.md` and `{PROJECT_PATH}/design.md` are required
-- In `quick`/`import` mode: `spec.md`/`design.md` are optional
+- In `quick`/`import`/`lite` mode: `spec.md`/`design.md` are optional; lite
+  proceeds with a reduced assurance note because plan.md is its full contract
 
 **Required (recommended to proceed):**
 
@@ -162,7 +163,7 @@ If `WORKFLOW_MODE=spec-driven`, also require:
 ls "$PROJECT_PATH/spec.md" "$PROJECT_PATH/design.md" 2>/dev/null
 ```
 
-If `WORKFLOW_MODE` is `quick` or `import`, proceed without spec/design and include a reduced-assurance note in the PR body.
+If `WORKFLOW_MODE` is `quick`, `import`, or `lite`, proceed without spec/design and include a reduced assurance note in the PR body. For lite, explicitly note that plan.md is the reduced artifact contract and the absence of discovery/spec/design is intentional.
 
 ### Step 2: Check Final Review Status
 
@@ -214,7 +215,32 @@ sequence step.
 
 **Step 3.0: Check for summary.md**
 
-Check if `{PROJECT_PATH}/summary.md` exists:
+Resolve the structurally exclusive route first:
+
+```bash
+# BEGIN LITE PR SUMMARY ROUTE CONTRACT
+if [ "$WORKFLOW_MODE" = "lite" ]; then
+  PR_SUMMARY_STRATEGY="lite-artifacts"
+  GENERIC_SUMMARY_REACHABLE="false"
+else
+  PR_SUMMARY_STRATEGY="summary-md"
+  GENERIC_SUMMARY_REACHABLE="true"
+fi
+# END LITE PR SUMMARY ROUTE CONTRACT
+```
+
+For `oat_workflow_mode: lite`, do not generate, refresh, or require
+`summary.md`. Synthesize the PR summary directly from the `plan.md` `Summary`,
+`Decisions`, and `Validation Criteria` sections plus the
+`implementation.md` `Final Summary (for PR/docs)` shipped results. This is the
+explicit reduced assurance path: absent `discovery.md`, `spec.md`, and
+`design.md` are valid and must not block PR creation. Then continue to Step 3.1
+only for the remaining available artifacts; do not invoke
+`oat-project-summary` for lite. This branch ends Step 3.0 and jumps directly to
+Step 3.1.
+
+**Non-lite branch only:** If the route contract sets
+`GENERIC_SUMMARY_REACHABLE=true`, check if `{PROJECT_PATH}/summary.md` exists:
 
 - If `summary.md` is missing or stale, refresh it automatically before proceeding.
 - When skill-to-skill invocation is available in the current host/runtime, load the current `oat-project-summary/SKILL.md` and follow it; never synthesize the summary from a remembered version of that skill.
@@ -229,8 +255,8 @@ Check if `{PROJECT_PATH}/summary.md` exists:
 
 Read:
 
-- `{PROJECT_PATH}/spec.md` (goals, priorities, verification; optional in quick/import)
-- `{PROJECT_PATH}/design.md` (architecture + testing strategy; optional in quick/import)
+- `{PROJECT_PATH}/spec.md` (goals, priorities, verification; optional in quick/import/lite)
+- `{PROJECT_PATH}/design.md` (architecture + testing strategy; optional in quick/import/lite)
 - `{PROJECT_PATH}/plan.md` (phases/tasks + reviews table)
 - `{PROJECT_PATH}/implementation.md` (if exists; preferred for “what actually happened”)
 - `{PROJECT_PATH}/discovery.md` (recommended for quick mode)
@@ -339,7 +365,7 @@ oat_project: { PROJECT_PATH }
 
 ## Goals / Non-Goals
 
-{brief bullets from available requirement artifacts: spec in spec-driven mode; discovery/import source in quick/import}
+{brief bullets from available requirement artifacts: spec in spec-driven mode; discovery/import source in quick/import; plan contract in lite}
 
 ## Changes