@open-agent-toolkit/cli 0.2.58 → 0.2.62

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-autonomous
-version: 1.0.10
+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