@open-agent-toolkit/cli 0.2.56 → 0.2.58

package/assets/agents/oat-phase-implementer.md

@@ -1,6 +1,6 @@
 ---
 name: oat-phase-implementer
-version: 1.1.1
+version: 1.1.3
 description: Implements one plan phase end-to-end, commits each task separately, self-checks between tasks, and handles bounded review fixes when resumed by oat-project-implement.
 tools: Read, Write, Edit, Bash, Grep, Glob, Task
 color: cyan
@@ -37,7 +37,8 @@ The root supplies:
   candidates, and formal dispatch stamp;
 - `phase_recovery_limit`, `phase_recovery_attempts_used`,
   `original_request_id`, and the root-resolved recovery authorization source;
-- optional `parallel_group`, `expected_base_sha`, and smoke run metadata.
+- optional `parallel_group`, `expected_base_sha`, `recovered_patch`, and
+  smoke run metadata.
 
 Fix mode also supplies:
 
@@ -341,12 +342,62 @@ use ancestry from `expected_base_sha` as a substitute for the exact
 `phase_base_head` check. For a plan-declared parallel group, verify this before
 any task edit.
 
+A fresh child never starts on a dirty tree. The one exception is a supplied
+`recovered_patch`, which carries work a lost child left behind: verify it,
+apply it, review it, and commit it as your first action before task one,
+exactly as `## Mode: Recover` steps 2 and 4 describe, and only after every
+precondition that can park the phase has passed. That single commit is a
+recovery commit rather than a planned task commit, so it does not consume any
+task's one-commit budget; report it under `### Recovery Events` with the
+artifact reference and manifest digest. Without a verified `recovered_patch`,
+any dirt blocks.
+
 When smoke containment, ownership registration, expected base, or fixture
 readiness proves the run invalid, return `INVALID_RUN_ABORT` with the evidence.
 Do not launch a child, continue sequentially, review, or repair the invalid run.
 
 ### 2. Execute Tasks in Plan Order
 
+#### Cross-Cutting Option Sweep
+
+Before the first edit of a task that adds, renames, retypes, or changes the
+default or meaning of an option, argument, flag, configuration field, schema
+property, or policy value consumed outside the module that defines it,
+inventory that symbol repository-wide. A value that is defined, read, and
+written only inside its own module does not trigger this rule.
+
+The inventory is repository-wide. It is never limited to the declared file
+boundary and never limited to production source: sweep declarations and type
+definitions, constructors and factories, adapters and wrappers, serializers and
+deserializers, persisted schemas and templates, fixtures, mocks, snapshots, and
+tests, and every call site that constructs, forwards, or defaults the value.
+Use `rg` or an equivalent repository-wide search together with whatever
+language-aware check this repository already provides; no single tool is proof
+of completeness, so search the property name, its serialized spelling, and its
+accessors.
+
+A declared file list is review scope, not a correctness boundary. When the
+sweep finds files outside that list:
+
+- **Widen mechanically and proceed** when every discovered file is already
+  required by the declared task outcome, the edit to it is mechanical
+  propagation of the same value, and no sibling or active parallel task owns
+  it. The effective task boundary is the declared list plus those mechanically
+  discovered files. Record every addition in the Task Outcomes `Files` cell and
+  in Self-Review Observations, and never edit `plan.md` to match.
+- **Stop and report** the exact discovered file set and the ownership conflict
+  when the expansion would change the declared task outcome, cross sibling or
+  parallel-lane ownership, invalidate a plan-declared parallel group, or
+  require a new design, architecture, or public-behavior decision.
+
+Threading an already-agreed option through four call sites that would otherwise
+keep the stale default is mechanical propagation. Adding new behavior at a
+discovered call site, changing an unrelated default, or deciding how two lanes
+divide a shared file is not, and stops for direction. This pre-edit rule
+matches the mechanically derived, in-phase widening already allowed during
+post-commit recovery, and it never relaxes the standing rule against scope
+expansion beyond the phase.
+
 For every task:
 
 1. Record `PRE_TASK_HEAD`.
@@ -369,7 +420,9 @@ For every task:
    mutate Git config or use `--no-verify`.
 9. Verify:
    - HEAD is exactly one commit after `PRE_TASK_HEAD`;
-   - the commit changes only declared task files;
+   - the commit changes only files in the effective task boundary, which is
+     the declared task files plus any mechanical additions permitted by, and
+     reported under, the cross-cutting option sweep;
    - every task verification passed; and
    - the worktree is clean.
 10. Perform a brief between-task transition check before starting the next
@@ -462,8 +515,18 @@ phase_verification: { relevant phase command }
 dispatch_target: { exact original launcher-owned target }
 dispatch_axes: { unchanged original launcher-owned axes }
 dispatch_stamp: { original formal Dispatch line }
+recovered_patch: { artifact, manifest_digest, size, stat, components }
 ```
 
+`recovered_patch` is optional. It is present only when a lost child left
+uncommitted work that the lifecycle captured before restoring the worktree to
+its clean base. Its `artifact` is a readable path outside the worktree, never a
+mutable worktree path; `manifest_digest` and `size` are the capture's recorded
+values; `stat` is the captured `git diff --cached --stat` summary; and
+`components` lists the `index`, `worktree`, and `untracked` entries the
+artifact holds. The same field may arrive on a same-target `implement`
+continuation.
+
 1. Validate every recover input. Confirm the exact launcher-owned target equals
    the original target and the generic `continuation_events` record links
    `continuation_event` to `original_request_id`.
@@ -471,23 +534,116 @@ dispatch_stamp: { original formal Dispatch line }
    remains immutable at the same history position; and the worktree contains
    only the reconciled pending ledger reservation plus an optional mechanically
    bounded diff inside `bounded_files`. Any other dirt or history change
-   blocks.
+   blocks. Compare against the briefed `recovery_base_head`, never a remembered
+   earlier value: once a recovery-patch commit has landed, the retry's
+   `recovery_base_head` is the reconciled current HEAD, which includes that
+   recovery commit and any candidate or ledger-only commit already durably
+   made, and the brief omits the already-committed artifact because re-applying
+   it would duplicate the work. Beyond that reconciled reservation and its
+   bounded diff, a supplied `recovered_patch` is the only permitted
+   pre-existing dirt, and only after it verifies. Verification is read-only and
+   happens here; the apply and the commit wait for step 4, so every precondition
+   that can park the phase resolves before anything is written. When the brief
+   carries no `recovered_patch` — an ordinary resume, or a retry after the
+   recovery commit already landed — the ordinary permitted-dirt invariant above
+   is the whole of this step: there is no artifact to resolve a script for, so
+   the continuation skips verification and continues to the ledger
+   reconciliation in step 3, and step 4 is a no-op. Resolve
+   `capture-dirty-tree.mjs` through installed scope rather than a
+   repository-relative path, probing in order and binding the first match, and
+   only when an artifact was briefed:
+
+   ```bash
+   set -eu
+   # `recovered_patch` is optional and all-or-nothing. Without one there is
+   # nothing to verify and nothing to apply, so the verifier is skipped
+   # entirely; a partial brief is a named stop rather than an unbound-variable
+   # death. Never dereference an artifact variable outside the branch: under
+   # `set -u` an unset one exits here, and an empty one fails verification —
+   # either way an artifact-free retry parks before the ledger reconciliation
+   # it needs to reach.
+   if [ -z "${ARTIFACT_DIR:-}${MANIFEST_DIGEST:-}${ARTIFACT_SIZE:-}" ]; then
+     : # No recovered_patch: continue to the ledger reconciliation.
+   elif [ -z "${ARTIFACT_DIR:-}" ] || [ -z "${MANIFEST_DIGEST:-}" ] ||
+     [ -z "${ARTIFACT_SIZE:-}" ]; then
+     echo "artifact-verification-failed: a partial recovered_patch is unusable; artifact, manifest_digest and size travel together" >&2
+     exit 1
+   else
+     CAPTURE_SCRIPT=""
+     REPO_ROOT=$(git -C "$PHASE_WORKTREE" rev-parse --show-toplevel 2>/dev/null || true)
+     for CAPTURE_ROOT in "${HOME:-}/.agents/skills/oat-project-implement" \
+       "${REPO_ROOT:+$REPO_ROOT/.agents/skills/oat-project-implement}"; do
+       [ -n "$CAPTURE_ROOT" ] || continue
+       [ -f "$CAPTURE_ROOT/scripts/capture-dirty-tree.mjs" ] || continue
+       CAPTURE_SCRIPT="$CAPTURE_ROOT/scripts/capture-dirty-tree.mjs"
+       break
+     done
+     [ -n "$CAPTURE_SCRIPT" ] || {
+       echo "capture-script-unavailable" >&2
+       exit 1
+     }
+
+     EXPECTED_HEAD=$(git -C "$PHASE_WORKTREE" rev-parse --verify HEAD)
+     node "$CAPTURE_SCRIPT" --verify \
+       --artifact-dir "$ARTIFACT_DIR" \
+       --manifest-digest "$MANIFEST_DIGEST" \
+       --size "$ARTIFACT_SIZE" \
+       --expected-head "$EXPECTED_HEAD"
+   fi
+   ```
+
+   `ARTIFACT_DIR`, `MANIFEST_DIGEST`, and `ARTIFACT_SIZE` are the
+   `recovered_patch` fields; bind them as shell variables rather than pasting
+   `<placeholder>` tokens, which a shell reads as input redirections. The guard
+   terminates rather than warning: `node ""` reads its program from stdin and
+   exits zero at EOF, so a fall-through would report an unverified artifact as
+   verified. Every block that runs the script repeats the resolution and the
+   guard, because shell variables do not survive across separate tool
+   invocations. `--expected-head` and the
+   apply below both resolve against `$PHASE_WORKTREE`, never the ambient
+   working directory. An empty `CAPTURE_SCRIPT` is a
+   `capture-script-unavailable` stop: report it verbatim with the probed roots
+   and the recovery command
+   `oat tools install workflows --scope <user|project>` or
+   `oat tools update --pack workflows --scope <user|project>`, and never fall
+   back to a repository-relative path. With an artifact briefed, verify before
+   touching the tree and stop on any `artifact-verification-failed` mismatch, including the base mismatch
+   `--expected-head` catches: integrity is not base agreement, and a hunk whose
+   context happens to match applies cleanly at the wrong commit. Report an
+   `active-writer`, `unsupported-dirt`, `round-trip-failed`, or
+   `artifact-verification-failed` reason verbatim and stop; never improvise a
+   partial or best-effort restore. Without a verified `recovered_patch` you
+   start on a clean tree.
+
 3. Reconcile the authoritative `pending_attempt` and nonzero
    `phase_recovery_attempts_used` with `state.md`. Recover mode continues that
    same consumed attempt and must not increment usage again. Missing,
-   contradictory, or unreconciled state blocks before editing.
-4. Apply or complete only `bounded_correction_scope`. Recover mode must not
+   contradictory, or unreconciled state blocks before editing. Nothing has been
+   applied or committed yet, so this block leaves the branch exactly at
+   `recovery_base_head` with the artifact untouched and re-verifiable; the root
+   re-briefs from current authoritative state once the ledger is repaired.
+4. Only now apply the verified `recovered_patch`, if one was supplied:
+   `git apply --index` for the `index` component, `git apply` for the
+   `worktree` component, and byte copies plus the manifest's recorded
+   executable bit for the `untracked` component. Review the result and commit
+   it as your first action. That commit is immutable, and so is every commit
+   this mode durably makes after it: if anything later parks the phase, the
+   retry's `recovery_base_head` is the reconciled current HEAD, which includes
+   that recovery commit and any candidate or ledger-only commit already made.
+   That brief omits the already-committed artifact; dirt that accumulated
+   afterwards travels as its own newly captured `recovered_patch`.
+5. Apply or complete only `bounded_correction_scope`. Recover mode must not
    replay planned tasks and must not require, fabricate, or consume a review
    artifact.
-5. Apply the bounded correction, then run `focused_verification` and
+6. Apply the bounded correction, then run `focused_verification` and
    `phase_verification` before creating a candidate commit. If either check
    fails, restore `bounded_files` to their original committed content,
    atomically mark the pending entry `failed`, durably commit only that
    ledger transition, emit one `failed-attempt` event, and stop.
-6. When both pre-commit checks pass, atomically mark the pending entry
+7. When both pre-commit checks pass, atomically mark the pending entry
    `completed` and create one append-only candidate recovery commit containing
    only `bounded_files` plus that ledger transition.
-7. Immediately rerun `focused_verification` and `phase_verification` against the
+8. Immediately rerun `focused_verification` and `phase_verification` against the
    committed HEAD; these reruns are authoritative. On pass, emit one `recovered`
    event and report the candidate as the successful recovery commit. On
    failure, atomically replace `completed` with `failed`, durably commit that
@@ -496,7 +652,7 @@ dispatch_stamp: { original formal Dispatch line }
    commit. If terminal evidence cannot be committed, report an unreconciled
    block that root must reject before bookkeeping. Never amend history or
    launch fallback.
-8. Return the report below. `DONE` is accepted success;
+9. Return the report below. `DONE` is accepted success;
    `DONE_WITH_CONCERNS` and `BLOCKED` may be accepted terminal stops and must
    still report provenance, accounting, immutable history, and the event.
 

package/assets/bundle-metadata.json

@@ -1,4 +1,4 @@
 {
   "schemaVersion": 1,
-  "oatVersion": "0.2.56"
+  "oatVersion": "0.2.58"
 }

package/assets/docs/contributing/smoke-testing.md

@@ -249,6 +249,50 @@ journaled worktree that is already gone from disk is still recoverable; a
 contradictory or unjournaled resource fails closed with a refusal rather than
 guessing.
 
+### Reserved versus registered ownership
+
+The deterministic provider's nested phase worktrees are journaled as a
+transaction, so an interruption can no longer leave an _unjournaled_ child.
+It can still leave state cleanup refuses by design — an interruption inside
+`git worktree add` may leave a path with no Git registration, and that is
+refused rather than deleted.
+
+Other nested creators still register directly after creation. Their entries are
+read as ownership the same way, but they are validated more loosely: a
+directly-registered entry carries no reservation origin, so it is not subject
+to the run-directory containment and run-baseline checks a finalized
+reservation gets. Their creation transaction has not been migrated yet.
+
+The two reservation states are:
+
+- **`reserved`** — the exact branch, worktree path, marker path, expected
+  baseline, shared Git directory, and run identity are written to the manifest
+  _before_ `git worktree add` runs. The entry is durable intent, not ownership.
+- **`registered`** — the child's marker, Git worktree registration, branch,
+  HEAD ancestry, and shared Git directory have all been corroborated.
+  Finalization only flips a matching reservation; it never rewrites what was
+  reserved, and a child contradicting its reservation is refused.
+
+Cleanup reconciles a reservation only against exactly matching state. If
+neither the branch nor the worktree was ever created, nothing is deleted and
+the reservation goes away with the manifest. If both exist exactly as reserved,
+they are removed after baseline, shared Git directory, and run-marker
+corroboration. If only the branch survives, its tip must equal the reserved
+baseline exactly. Anything else — an occupied path Git never registered, a
+different branch at the reserved path, a missing marker — fails closed.
+
+Manifests written before this transaction existed use ownership journal schema
+version 1. They stay readable and all of their entries read as already
+`registered`. Such a manifest is never rewritten to a newer schema version and
+never gains a reservation, and a v1 entry claiming reserved state is refused
+rather than treated as owned. Direct registration may still append a
+`registered` entry to one, which leaves its schema version untouched.
+
+Nothing is ever pruned by `smoke-*` name, path prefix, run age, or ancestry
+alone. Without an ownership lease the runner cannot tell a stale run from an
+active one, so it refuses instead of guessing and leaves the state for you to
+resolve.
+
 To finish a stalled run, re-run the matching `--stage collect` (collection-only
 triggers cleanup) or start a fresh run; the runner reconciles journaled
 resources on the next errored or collection-bearing invocation. If cleanup fails

package/assets/docs/workflows/projects/implementation-execution.md

@@ -88,7 +88,7 @@ The phase implementer receives one `Phase Scope`, reads the relevant artifacts
 once, and directly executes each task in plan order. For every task it:
 
 1. records the pre-task HEAD;
-2. implements only the declared task files;
+2. implements the declared task files plus any mechanical additions permitted by, and reported under, the cross-cutting option sweep (a repository-wide sweep for every consumer of a changed option; cross-owner expansions stop and report instead);
 3. runs task verification;
 4. self-checks requirements and scope before commit;
 5. creates exactly one task commit; and
@@ -152,7 +152,11 @@ by the phase's standing authority. The important distinctions are:
   boundary, not for every eligible defect;
 - a **continuation** preserves the original request and exact target, either in
   the accepted handle or through an explicitly linked fresh same-target
-  recovery launch; and
+  recovery launch, and never starts on a dirty tree: uncommitted work a lost
+  child left behind is first captured into a digest-verified artifact,
+  restored out of the worktree, handed forward as `recovered_patch`, and
+  committed by the continuation as its first action, while unverified or
+  unsupported dirt still blocks; and
 - a **successful repair** produces one immutable append-only recovery commit.
 
 This recovery is not accepted-launch fallback. After a launch is accepted,

package/assets/docs/workflows/skills/explainer-kit.md

@@ -434,11 +434,14 @@ typed adapter settings.
 Private integrations use the core boundary directly: resolve private inputs
 before the run, construct one versioned request, invoke the core once, then
 publish or link the versioned manifest after the run. Wrapper acceptance reads
-the complete post-run `publish-receipt/v2`, verifies every manifest artifact
-and the core run ID, and rejects foreign or stale receipts; `publish-receipt/v1`
-remains readable for replay of older runs only. Presets, private source
-systems, external-document synchronization, and personal destinations remain
-wrapper-owned.
+the complete post-run `publish-receipt/v2`, requires complete manifest and
+catalog evidence, verifies the core run ID, and rejects foreign or stale
+receipts; `publish-receipt/v1` remains readable for replay of older runs only.
+Public and protected v2 receipts must each provide exactly one entry for every
+finalized manifest artifact and exactly one generated catalog entry. The
+`explainer-kit` wrapper extension contract owns this rule; this page restates
+it for integrators. Presets, private source systems, external-document
+synchronization, and personal destinations remain wrapper-owned.
 
 V1 exposes no plugin registry or private mid-pipeline hook. Unsupported
 contract majors and identity mismatches fail closed instead of being guessed

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.2.56",
-  "docs-config": "0.2.56",
-  "docs-theme": "0.2.56",
-  "docs-transforms": "0.2.56"
+  "cli": "0.2.58",
+  "docs-config": "0.2.58",
+  "docs-theme": "0.2.58",
+  "docs-transforms": "0.2.58"
 }

package/assets/skills/analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: analyze
-version: 0.1.1
+version: 0.2.0
 description: Multi-angle analysis of existing artifacts, codebases, documents, or systems. Examines what you have from six analysis angles and produces structured findings with prioritized recommendations.
 argument-hint: 'target [--context path]'
 user-invocable: true
@@ -49,15 +49,16 @@ Print this banner once at start:
 
 Then print step indicators before beginning work:
 
-- `[1/9] Parsing arguments…`
-- `[2/9] Reading context…` (if applicable)
-- `[3/9] Classifying input type…`
-- `[4/9] Selecting analysis angles…`
-- `[5/9] Checking sub-agent availability…`
-- `[6/9] Executing analysis angles…`
-- `[7/9] Checking for comparisons…` (if applicable)
-- `[8/9] Cross-angle synthesis…`
-- `[9/9] Writing artifact…`
+- `[1/10] Parsing arguments…`
+- `[2/10] Reading context…` (if applicable)
+- `[3/10] Classifying input type…`
+- `[4/10] Selecting analysis angles…`
+- `[5/10] Checking sub-agent availability…`
+- `[6/10] Executing analysis angles…`
+- `[7/10] Checking for comparisons…` (if applicable)
+- `[8/10] Cross-angle synthesis…`
+- `[9/10] Resolving output destination…`
+- `[10/10] Writing artifact…`
 
 For long-running operations, print a start line and a completion line:
 
@@ -72,7 +73,7 @@ Keep it concise; don't print a line for every shell command.
 
 ### Step 1: Parse arguments
 
-`[1/9] Parsing arguments…`
+`[1/10] Parsing arguments…`
 
 Parse from `$ARGUMENTS`:
 
@@ -91,7 +92,7 @@ The prompt should ask: _"What would you like me to analyze? Provide a file path,
 
 ### Step 2: Read context (if provided)
 
-`[2/9] Reading context…`
+`[2/10] Reading context…`
 
 If `--context` is specified:
 
@@ -107,7 +108,7 @@ If `--context` is not specified, skip this step.
 
 ### Step 3: Input type classification
 
-`[3/9] Classifying input type…`
+`[3/10] Classifying input type…`
 
 Classify the target to determine analysis angle emphasis:
 
@@ -126,7 +127,7 @@ Log: `→ Input type: {type}`
 
 ### Step 4: Analysis angle selection
 
-`[4/9] Selecting analysis angles…`
+`[4/10] Selecting analysis angles…`
 
 All six angles are ALWAYS run. The input type determines emphasis weighting (primary angles get deeper investigation):
 
@@ -157,7 +158,7 @@ Log the selected emphasis: `→ Primary: {angles} · Secondary: {angles}`
 ### Step 5: Sub-agent availability probe
 
 ```
-[5/9] Checking sub-agent availability…
+[5/10] Checking sub-agent availability…
   → analysis workers: {available | not resolved} ({reason})
   → Selected: Execution Tier {1|2|3} — {description}
 ```
@@ -184,7 +185,7 @@ Log the selected emphasis: `→ Primary: {angles} · Secondary: {angles}`
 
 ### Step 6: Execute analysis angles
 
-`[6/9] Executing analysis angles…`
+`[6/10] Executing analysis angles…`
 
 For each angle, the worker (sub-agent or self) receives:
 
@@ -209,7 +210,7 @@ Print progress for each angle:
 
 ### Step 7: Conditional /compare dispatch
 
-`[7/9] Checking for comparisons…`
+`[7/10] Checking for comparisons…`
 
 If any angle surfaces comparables (e.g. "this component could use library A or B"):
 

package/assets/skills/oat-brainstorm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-brainstorm
-version: 1.3.4
+version: 1.3.5
 description: Use when the user explicitly invokes the `brainstorm` verb, including `/oat-brainstorm`, "let's brainstorm", "brainstorm this", "can we brainstorm X", or "help me brainstorm X". For ambiguous exploratory phrasing ("I've been thinking", "what if", "help me think through"), do NOT auto-enter; respond conversationally and offer mode only after ≥2 sustained exploratory turns. Do NOT use for review, debug, PR, status, implementation, or active-workflow questions.
 disable-model-invocation: false
 user-invocable: true
@@ -191,7 +191,7 @@ Classify the opening brainstorm topic before running the Node preflight or print
 command -v node >/dev/null 2>&1 && echo "available" || echo "missing"
 ```
 
-- If `node` is **missing**: skip the offer entirely. Do not print the offer message. Log a one-line note in the conversation that the visual companion is unavailable in this environment (a state `oat-doctor` can pick up later: "visual companion suppressed — node not on PATH"). Proceed with `VISUAL_COMPANION = "unavailable"`.
+- If `node` is **missing**: skip the offer entirely. Do not print the offer message. Log a one-line note in the conversation for this session only: "visual companion suppressed — node not on PATH". Nothing persists that note, so no later diagnostic run can report it. Proceed with `VISUAL_COMPANION = "unavailable"`.
 - If `node` is **available**: print the offer as its own message. Suggested wording (adapt freely; the constraint is "own message, no other content"):
 
   > "Some of what we're working on might be easier to explain if I can show it in a local web browser — mockups, diagrams, side-by-side comparisons. The visual companion is bundled with this skill (a small Node-based local server). Want me to start it? (Requires opening a `localhost` URL.)"

package/assets/skills/oat-doctor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-doctor
-version: 1.1.0
+version: 1.2.0
 description: Use when you need to diagnose your OAT setup, check for outdated skills, identify misconfigurations, or get a summary of installed tools and config. Runs health checks and recommends corrective actions.
 argument-hint: '[--summary]'
 disable-model-invocation: true
@@ -151,47 +151,60 @@ For summary mode, compare installed skills against the full manifest to identify
 
 **Bundled skill manifest (source of truth):**
 
-Core pack skills:
+Each heading below names a pack exactly as `oat tools install <pack>` expects
+it, and lists every skill that pack ships.
 
-- oat-docs, oat-doctor
+`core` pack skills:
 
-Workflow pack skills:
+- oat-docs, oat-doctor
 
-- oat-project-capture, oat-project-clear-active, oat-project-complete
-- oat-project-design, oat-project-discover, oat-project-document
-- oat-project-implement, oat-project-import-plan, oat-project-new
-- oat-project-open, oat-project-plan, oat-project-plan-writing
-- oat-project-pr-final, oat-project-pr-progress, oat-project-progress
-- oat-project-promote-spec-driven, oat-project-quick-start
-- oat-project-reconcile, oat-project-revise, oat-project-review-provide
-- oat-project-review-receive, oat-project-review-receive-remote
-- oat-project-spec, oat-project-summary
-- oat-repo-knowledge-index, oat-worktree-bootstrap, oat-worktree-bootstrap-auto
-
-Ideas pack skills:
+`ideas` pack skills:
 
 - oat-idea-new, oat-idea-ideate, oat-idea-summarize, oat-idea-scratchpad
 
-Docs pack skills:
+`docs` pack skills:
+
+- authoring-docs, oat-agent-instructions-analyze
+- oat-agent-instructions-apply, oat-docs-analyze
+- oat-docs-apply, oat-docs-authoring, oat-docs-bootstrap
 
-- oat-agent-instructions-analyze, oat-agent-instructions-apply
-- oat-docs-analyze, oat-docs-apply
+`workflows` pack skills:
 
-Utility pack skills:
+- oat-cursor-cloud-projects, oat-explainer-kit, oat-project-autonomous
+- oat-project-capture, oat-project-clear-active, oat-project-complete
+- oat-project-design, oat-project-dispatch-subagents, oat-project-discover
+- oat-project-document, oat-project-implement, oat-project-import-plan
+- oat-project-new, oat-project-next, oat-project-open
+- oat-project-plan, oat-project-plan-writing, oat-project-pr-final
+- oat-project-pr-progress, oat-project-progress, oat-project-promote-spec-driven
+- oat-project-quick-start, oat-project-reconcile, oat-project-retro
+- oat-project-retro-file, oat-project-revise, oat-project-review-provide
+- oat-project-review-provide-remote, oat-project-review-receive
+- oat-project-review-receive-remote, oat-project-spec, oat-project-split
+- oat-project-summary, oat-repo-knowledge-index, oat-worktree-bootstrap
+- oat-worktree-bootstrap-auto, oat-wave-execute, oat-wave-program
+- oat-wrap-up
+
+`utility` pack skills:
 
-- create-agnostic-skill
-- oat-repo-maintainability-review, oat-review-provide
-- oat-review-receive, oat-review-receive-remote
+- create-agnostic-skill, explainer-kit, oat-dispatch-subagents
+- subagent-orchestration, oat-repo-improve, oat-repo-maintainability-review
+- oat-review-provide, oat-review-provide-remote, oat-review-receive
+- oat-review-receive-remote
 
-Project management pack skills:
+`project-management` pack skills:
 
-- oat-pjm-add-backlog-item, oat-pjm-update-repo-reference
-- oat-pjm-review-backlog
+- oat-pjm-add-backlog-item, oat-pjm-decision
+- oat-pjm-update-repo-reference, oat-pjm-review-backlog
 
-Research pack skills:
+`research` pack skills:
 
 - analyze, compare, deep-research
-- skeptic, synthesize
+- recon, skeptic, synthesize
+
+`brainstorm` pack skills:
+
+- oat-brainstorm
 
 For each pack, determine:
 
@@ -224,12 +237,12 @@ OAT ▸ DOCTOR SUMMARY
 | Pack      | Scope   | Skills | Status   |
 | --------- | ------- | ------ | -------- |
 | core      | user    | 2/2    | current  |
-| docs      | project | 4/4    | current  |
-| workflows | project | 26/26  | current  |
+| docs      | project | 7/7    | current  |
+| workflows | project | 39/39  | current  |
 | ideas     | user    | 4/4    | current  |
-| project-management | project | 3/3 | current |
-| research  | project | 5/5    | current  |
-| utility   | project | 5/5    | outdated |
+| project-management | project | 4/4 | current |
+| research  | project | 6/6    | current  |
+| utility   | project | 10/10  | outdated |
 
 ## Outdated Skills
 
@@ -239,11 +252,11 @@ OAT ▸ DOCTOR SUMMARY
 
 ## Available But Not Installed
 
-- **docs** pack: oat-docs-analyze, oat-docs-apply, oat-agent-instructions-analyze, oat-agent-instructions-apply (4 skills available)
+- **docs** pack: authoring-docs, oat-agent-instructions-analyze, oat-agent-instructions-apply, oat-docs-analyze, oat-docs-apply, oat-docs-authoring, oat-docs-bootstrap (7 skills available)
   → Run: oat tools install docs --scope {scope}
-- **project-management** pack: oat-pjm-add-backlog-item, oat-pjm-update-repo-reference, oat-pjm-review-backlog (3 skills available)
+- **project-management** pack: oat-pjm-add-backlog-item, oat-pjm-decision, oat-pjm-update-repo-reference, oat-pjm-review-backlog (4 skills available)
   → Run: oat tools install project-management --scope {scope}
-- **research** pack: analyze, compare, deep-research, skeptic, synthesize (5 skills available)
+- **research** pack: analyze, compare, deep-research, recon, skeptic, synthesize (6 skills available)
   → Run: oat tools install research --scope {scope}
 
 ## Configuration

package/assets/skills/oat-idea-summarize/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: oat-idea-summarize
-version: 1.2.1
+version: 1.3.0
 description: Use when an idea is mature enough to move from brainstorming into the backlog. Generates a summary document and adds the idea to the backlog.
 argument-hint: '[--global]'
 disable-model-invocation: true
 user-invocable: true
-allowed-tools: Read, Write, Grep, AskUserQuestion
+allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
 ---
 
 # Summarize Idea