@open-agent-toolkit/cli 0.2.59 → 0.2.63

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-next
-version: 1.0.14
+version: 1.1.1
 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,16 @@ 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                                    |
+| `oat_lifecycle`           | Terminal status (active, paused, complete). `complete` is the terminal signal Step 5.2 reads |
 
 **If state.md is missing or unreadable:** Report error and suggest running the relevant phase skill directly. STOP.
 
@@ -164,12 +166,22 @@ Apply the following tiers in order:
 
 - `oat_status == "complete"` AND `oat_ready_for` is not null
 - → Use `oat_ready_for` as the target skill
+- Exception: in quick mode at the `plan` phase, the Quick Mode table's
+  `Quick Plan Readiness` column decides the target. A tier-1 quick plan that
+  fails readiness returns to the quick workflow, and `oat_ready_for` is not
+  followed on its own.
 
 **Tier 1b (Complete without target):**
 
 - `oat_status == "complete"` AND `oat_ready_for` is null
 - → Route to the NEXT phase's skill (the artifact is complete, so advance)
 - This handles cases where a phase skill completed the artifact but didn't set `oat_ready_for`.
+- Exception: in quick mode at the `plan` phase, a tier-1b artifact is evaluated
+  against **quick plan readiness** like every other plan-phase classification.
+  Tier 1b means `oat_ready_for` is null, so readiness always fails, so it
+  returns to the quick workflow instead of advancing to the next phase's skill.
+  This state is reachable when the Step 3.7 frontmatter write is interrupted or
+  after a hand edit, and it must not reach implementation unchecked.
 
 **Tier 2 (Substantive content):**
 
@@ -237,21 +249,51 @@ Otherwise, look up the target skill from the routing table for the current `oat_
 
 **Quick Mode:**
 
+| Current Phase | Phase Status | Boundary Tier | Quick Plan Readiness | Target Skill               |
+| ------------- | ------------ | ------------- | -------------------- | -------------------------- |
+| discovery     | in_progress  | tier 3        | —                    | `oat-project-discover`     |
+| discovery     | in_progress  | tier 2        | —                    | `oat-project-plan`         |
+| discovery     | complete     | tier 1        | —                    | `oat-project-plan`         |
+| plan          | in_progress  | tier 3        | not ready            | `oat-project-quick-start`  |
+| plan          | in_progress  | tier 2        | not ready            | `oat-project-quick-start`  |
+| plan          | in_progress  | tier 1        | not ready            | `oat-project-quick-start`  |
+| plan          | in_progress  | tier 1        | ready                | `oat-project-implement` \* |
+| plan          | complete     | tier 1        | not ready            | `oat-project-quick-start`  |
+| plan          | complete     | tier 1        | ready                | `oat-project-implement` \* |
+| plan          | any          | tier 1b       | not ready (always)   | `oat-project-quick-start`  |
+| implement     | in_progress  | —             | —                    | `oat-project-implement` \* |
+
+The `Quick Plan Readiness` column applies to the `plan` phase only, and only
+after the boundary tier has already been classified by Step 2, so tier semantics
+are unchanged: it discriminates the two `plan` outcomes that would otherwise
+share one tier. A tier-2 or tier-1 quick plan is no longer assumed ready, and a
+tier-1 plan whose readiness fails is returned to the quick workflow rather than
+advanced. Both recorded phase statuses carry a tier-1 pair of rows, so a plan
+artifact that has already advanced past the `state.md` phase status still
+matches a route instead of falling through the table. Tier 1b carries one row
+under either phase status because a null `oat_ready_for` can never satisfy
+readiness. Readiness is the named **quick plan readiness** predicate: load
+`oat-project-quick-start/SKILL.md` and apply it as written to
+`{PROJECT_PATH}/plan.md` instead of restating its conditions here, and never
+infer readiness from the presence of substantive tasks. A `not ready` result
+resumes the quick workflow in place: load `oat-project-quick-start/SKILL.md` and
+follow its Step 0.5 resume branch. Spec-driven planning is not the recovery path
+for a quick project.
+
+**Import Mode:**
+
 | Current Phase | Phase Status | Boundary Tier | Target Skill               |
 | ------------- | ------------ | ------------- | -------------------------- |
-| discovery     | in_progress  | tier 3        | `oat-project-discover`     |
-| discovery     | in_progress  | tier 2        | `oat-project-plan`         |
-| discovery     | complete     | tier 1        | `oat-project-plan`         |
-| plan          | in_progress  | tier 3        | `oat-project-quick-start`  |
+| plan          | in_progress  | tier 3        | `oat-project-import-plan`  |
 | plan          | in_progress  | tier 2        | `oat-project-implement` \* |
 | plan          | complete     | tier 1        | `oat-project-implement` \* |
 | implement     | in_progress  | —             | `oat-project-implement` \* |
 
-**Import Mode:**
+**Lite Mode:**
 
 | Current Phase | Phase Status | Boundary Tier | Target Skill               |
 | ------------- | ------------ | ------------- | -------------------------- |
-| plan          | in_progress  | tier 3        | `oat-project-import-plan`  |
+| 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` \* |
@@ -382,6 +424,17 @@ or a summary exists. A completed snapshot falls through to the normal router.
 
 **5.2: Incomplete revision tasks**
 
+Read `oat_lifecycle` from `state.md` before grepping anything. When
+`oat_lifecycle` is `complete`, revision phases are historical: skip this check
+and fall through to 5.3, and do not route to `oat-project-implement` even when
+`p-revN` tasks are still marked incomplete. Lifecycle is the only terminal
+signal here — neither a null current task nor a `complete` or `pr_open`
+`oat_phase_status` is terminal, because an active project reaches both while it
+still owns pending revision work. The guard is workflow-mode independent: it
+applies identically to `spec-driven`, `quick`, `import`, and `lite` projects.
+
+For every other `oat_lifecycle` value the check below is unchanged.
+
 Grep plan.md for `p-revN` phases. If any `p-revN` tasks exist with status != completed in implementation.md:
 → Route to `oat-project-implement`
 → Announce: "Revision tasks pending — continuing implementation"
@@ -424,6 +477,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.8
+version: 1.4.10
 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."
+- **`quick`**: **Stop.** Spec-driven planning does not apply here: the quick workflow authors `plan.md` itself and owns it through its own review disposition. Step 1 routes the project by the named **quick plan readiness** predicate instead of assuming the plan is finished.
 - **`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
 
@@ -110,11 +113,46 @@ PROJECTS_ROOT="${PROJECTS_ROOT%/}"
 WORKFLOW_MODE=$(oat project status --field project.workflowMode 2>/dev/null || echo null)
 ```
 
-**Mode: `quick`** — **STOP.** Print:
+**Mode: `quick`** — **STOP.** Spec-driven planning does not apply: the quick
+workflow owns `plan.md` from discovery through the review disposition it records
+at its Step 3.7, so this skill never authors, finishes, or reviews a quick plan.
+It still has to say where the project continues, and a quick plan that is not
+implementation-ready must not be handed to implementation. Decide the
+continuation with the named **quick plan readiness** predicate: load
+`oat-project-quick-start/SKILL.md` and apply that predicate as written to
+`"$PROJECT_PATH/plan.md"`, rather than restating or re-deriving its conditions
+here.
+
+**Not implementation-ready** (the predicate fails; substantive tasks alone never
+satisfy it). Print:
+
+```
+⚠️  This project uses quick mode and its plan is not implementation-ready.
+    Spec-driven planning does not apply — the quick workflow finishes its own
+    plan in place, without re-scaffolding the project.
+
+    Continue with: oat-project-quick-start
+```
+
+Then load `oat-project-quick-start/SKILL.md` and follow its Step 0.5 resume
+branch. Exit skill.
+
+**Implementation-ready** (every predicate condition holds). Print:
+
+```
+⚠️  This project uses quick mode and its plan is implementation-ready.
+
+    Continue with: oat-project-implement
+```
+
+Then load `oat-project-implement/SKILL.md` and follow it to begin execution.
+Exit skill.
+
+**Mode: `lite`** — **STOP.** Print:
 
 ```
-⚠️  This project uses quick mode. Plan is produced by the quick workflow.
-    Run the `oat-project-implement` skill to begin execution.
+⚠️  This project uses lite mode. Run `oat-project-lite` to author or resume
+    its combined requirements and single-phase plan.
 ```
 
 Exit skill.

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-plan-writing
-version: 1.2.22
+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.
 
@@ -549,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:
@@ -653,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