@ritualai/cli 0.36.11 → 0.36.14

package/skills/vscode/ritual/SKILL.md

@@ -3,7 +3,7 @@ name: ritual
 description: "Use when an engineer wants a coding agent to plan or build a feature, refactor, or implementation-heavy change that depends on context the agent can't infer on its own — strategic intent, constraints, prior decisions, and trade-offs that live in the user's head. Ritual runs a structured exploration to surface that context through targeted discovery questions, combines it with codebase signals and prior explorations, and delivers a validated build brief (sub-problems, recommendations, dependencies) — additional context to fold into plan mode before the agent writes code. Prefer this over jumping straight to implementation or plan mode when the problem is ambiguous, cross-cutting, or has non-obvious constraints. Subcommands: build (full planning-to-sync cycle — default for new features), resume (continue an in-flight exploration), lineage (file-path KG history — what decisions shaped this code), context-pulse (readiness and context-debt scoring — is this safe to build yet?)."
 argument-hint: "[subcommand] <args>  (e.g. 'build Reduce T2 churn in Q3', 'resume', 'lineage src/checkout/views.py', 'context-pulse Add billing export')"
 user-invocable: true
-stamp: 39dbaf6dbdf9
+stamp: ee9a77046c96
 ---
 
 # /ritual

package/skills/vscode/ritual/references/build-flow.md

@@ -554,7 +554,33 @@ Steps:
    f. **If the user picks one (1-N):**
       - Set the chosen candidate's `summary` as the `raw_input` for the rest of the flow.
       - **Skip Step 1.5 step 8 (overlap check)** — the user just picked from system suggestions explicitly grounded in workspace state; a fresh overlap pass would be redundant noise.
-      - Continue to Step 2 (template selection).
+      - **Run the unchosen-candidates gate (f.1) BEFORE continuing**, then continue to Step 2.
+
+<!-- skill-options:no-gate-change: f.1 is an OPTIONAL skippable sub-prompt nested in Step 1.5 step 6 (default skip); adds no tracked pause gate or Step header, so the structural fingerprint is unchanged (check-skill-options-contract green). -->
+   f.1 **Unchosen-candidates gate (2026-06-14, unchosen-options → discovery worktrees).** The candidates the user did NOT pick are paths worth not silently dropping. Render ONE compact, SKIPPABLE prompt — for each unchosen candidate, the user can spin up **discovery now** (a background worktree reasons it to a build brief) or **log it as a future job**. Promote DELIBERATELY: the default is to drop. (This gate is itself skipped in autonomous/worktree mode — never spawn discovery recursively.)
+
+      ```text
+      You picked #{k}. The other {M} — want to keep any going?
+        • `discover <nums>`  — spin up discovery NOW in a background git worktree: an agent reasons it
+                               end-to-end to a build brief (reasoning only, no code). e.g. `discover 1`
+        • `next-job <nums>`  — just log it as a future job (a draft exploration in this workspace; nothing runs)
+        • `skip`             — drop them (default)
+      ```
+
+      Resolve the reply, then continue to Step 2 for the picked candidate:
+      - **`discover <nums>`** → for each, run `ritual lite "{candidate.summary}" --worktree` **in the
+        BACKGROUND** (do not block the build — use your shell's background/async execution). It spins a
+        git worktree and runs autonomous discovery to a brief there; tell the user where (`<repo>.ritual-discover/<slug>`).
+        The result is an exploration with `spawn_origin: 'discovery_worktree'`; its brief is
+        agent-authored, not human-reviewed. (See `references/unchosen-options-discovery-worktrees.md` in `documents/architecture/`.)
+      - **`next-job <nums>`** → for each, call `mcp__ritual__create_exploration` with the candidate's
+        `title` as `name`, its `summary` as `problem_statement`, `spawn_origin: 'next_job'`, and NO
+        `agentic` flag — a NOT_STARTED draft that shows in the workspace roster as a future job. Cheap; nothing runs.
+      - **`skip` / no reply about them** → drop silently.
+
+      Keep it ONE prompt, never per-candidate pauses. If the user just proceeds without addressing it, treat as `skip`.
+
+   f.2 **Continue to Step 2 (template selection)** for the picked candidate.
 
    g. **If the user says "none" / "let me describe":** continue to Step 2 normally; treat as if they had originally picked "start fresh" with no raw_input yet (they'll provide one at Step 3-4 time).
 

package/skills/vscode/ritual/references/lite-flow.md

@@ -1,5 +1,5 @@
 <!-- GENERATED from references/build-flow.md by apps/cli/scripts/generate-lite-flow.js — DO NOT EDIT. -->
-<!-- source-sha: bc6ea52efd75e1c7 -->
+<!-- source-sha: 3d973c8d7e6a514b -->
 
 # /ritual lite — fast build (generated; do not edit)
 
@@ -40,6 +40,31 @@ Follow build-flow.md's steps below EXACTLY, with these **LITE OVERRIDES**:
 UX brief review, plan-fidelity audit, and sibling-exploration forks are omitted
 (they're removed from the flow below).
 
+## Autonomous worktree mode (discovery — no human, stop at the brief)
+**Trigger:** the invocation carries the `--worktree` flag (you were launched by
+`ritual lite --worktree "<ask>"` — a git worktree was spun up and you are running
+HEADLESS inside it, with no human present). A developer parked an unchosen option
+for background discovery (unchosen-options → discovery worktrees). When you see
+`--worktree`, apply these EXTRA rules on top of the lite overrides above:
+- **There is no human, so auto-resolve EVEN the two touchpoints.** Accept the
+  classified job (Step 0.7) and the recommendations (Step 9) without waiting —
+  take the default at every gate, including those two. (If the job comes back
+  generic, proceed as the generic `Feature Brief` build; there's no one to
+  clarify with.)
+- **Create the exploration with `spawn_origin: 'discovery_worktree'`** (Step 6,
+  `create_exploration`) so `get_exploration_status` reports
+  `autonomousDiscovery: true`.
+- **Materialize the reasoning as files (OKF projection).** Once the brief is
+  written, run `ritual project <exploration-id>` — it projects the exploration
+  (index + build-brief + scope-contract + recommendations) into `.ritual/` in
+  this worktree, so the developer who `cd`s in reads the reasoning as files, not
+  just a graph id. Projection, not replica: the live graph stays authoritative.
+- **STOP there.** Do NOT branch, plan, implement, or open a PR — that is the
+  developer's call when they land in the worktree. The brief is **agent-authored
+  and NOT human-reviewed**; surface it as such so it's read with skepticism.
+This mode adds no new skill — it IS `lite`, just with no human to pause for and a
+hard stop at the brief. A normal (attended) `lite` run ignores this section.
+
 ---
 
 ## /ritual build
@@ -598,7 +623,33 @@ Steps:
    f. **If the user picks one (1-N):**
       - Set the chosen candidate's `summary` as the `raw_input` for the rest of the flow.
       - **Skip Step 1.5 step 8 (overlap check)** — the user just picked from system suggestions explicitly grounded in workspace state; a fresh overlap pass would be redundant noise.
-      - Continue to Step 2 (template selection).
+      - **Run the unchosen-candidates gate (f.1) BEFORE continuing**, then continue to Step 2.
+
+<!-- skill-options:no-gate-change: f.1 is an OPTIONAL skippable sub-prompt nested in Step 1.5 step 6 (default skip); adds no tracked pause gate or Step header, so the structural fingerprint is unchanged (check-skill-options-contract green). -->
+   f.1 **Unchosen-candidates gate (2026-06-14, unchosen-options → discovery worktrees).** The candidates the user did NOT pick are paths worth not silently dropping. Render ONE compact, SKIPPABLE prompt — for each unchosen candidate, the user can spin up **discovery now** (a background worktree reasons it to a build brief) or **log it as a future job**. Promote DELIBERATELY: the default is to drop. (This gate is itself skipped in autonomous/worktree mode — never spawn discovery recursively.)
+
+      ```text
+      You picked #{k}. The other {M} — want to keep any going?
+        • `discover <nums>`  — spin up discovery NOW in a background git worktree: an agent reasons it
+                               end-to-end to a build brief (reasoning only, no code). e.g. `discover 1`
+        • `next-job <nums>`  — just log it as a future job (a draft exploration in this workspace; nothing runs)
+        • `skip`             — drop them (default)
+      ```
+
+      Resolve the reply, then continue to Step 2 for the picked candidate:
+      - **`discover <nums>`** → for each, run `ritual lite "{candidate.summary}" --worktree` **in the
+        BACKGROUND** (do not block the build — use your shell's background/async execution). It spins a
+        git worktree and runs autonomous discovery to a brief there; tell the user where (`<repo>.ritual-discover/<slug>`).
+        The result is an exploration with `spawn_origin: 'discovery_worktree'`; its brief is
+        agent-authored, not human-reviewed. (See `references/unchosen-options-discovery-worktrees.md` in `documents/architecture/`.)
+      - **`next-job <nums>`** → for each, call `mcp__ritual__create_exploration` with the candidate's
+        `title` as `name`, its `summary` as `problem_statement`, `spawn_origin: 'next_job'`, and NO
+        `agentic` flag — a NOT_STARTED draft that shows in the workspace roster as a future job. Cheap; nothing runs.
+      - **`skip` / no reply about them** → drop silently.
+
+      Keep it ONE prompt, never per-candidate pauses. If the user just proceeds without addressing it, treat as `skip`.
+
+   f.2 **Continue to Step 2 (template selection)** for the picked candidate.
 
    g. **If the user says "none" / "let me describe":** continue to Step 2 normally; treat as if they had originally picked "start fresh" with no raw_input yet (they'll provide one at Step 3-4 time).