@open-agent-toolkit/cli 0.1.54 → 0.1.59

package/assets/skills/oat-project-dispatch-subagents/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-dispatch-subagents
-version: 1.1.0
+version: 1.1.2
 description: Use when an OAT project lifecycle skill needs to translate project state, phase or task scope, gates, and write authority into a provider-neutral subagent dispatch.
 disable-model-invocation: true
 user-invocable: false
@@ -108,19 +108,25 @@ conversational approval are never project policy.
 
 Map each lifecycle role to a generic baseline class and add project policy:
 
-| Lifecycle role             | Generic class | Project-specific contract                                                                                                                |
-| -------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| Phase coordinator          | `coordinator` | Own one phase dossier. Prefer an explicit suitable native target; inherit only when the root/session target is deliberately suitable.    |
-| Task worker                | `worker`      | Own one task and bounded files. Use an explicit native or pre-selected alternate target; never silently inherit an expensive root model. |
-| Fix worker                 | `worker`      | Own listed findings and bounded files. Preserve retry/fix-loop limits and original task context.                                         |
-| Planning self-review       | `reviewer`    | Inherit the planning parent by default unless the plan-writing contract requires an exact independent reviewer.                          |
-| Implementation self-review | `reviewer`    | Target the resolved reviewer ceiling; inherit only when the review-owning dispatcher is known to satisfy it.                             |
-| Phase gate                 | `reviewer`    | Use the configured independent target and fail closed when unavailable.                                                                  |
-| Lifecycle gate             | `reviewer`    | Stay independent of producer context and fail closed rather than substituting same-context self-review.                                  |
+| Lifecycle role                         | Generic class       | Project-specific contract                                                                                               |
+| -------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| Phase implementer                      | `worker`            | Own one complete phase, execute tasks directly in order, preserve per-task commits, and return phase verification.      |
+| Optional task/recon/specialist child   | `worker` or `recon` | Launch only when benefit justifies nesting; keep objective, files, authority, target, output, and verification bounded. |
+| Phase fix continuation                 | `worker`            | Resume the original phase handle when possible; preserve retry limits, phase context, and original request linkage.     |
+| Planning self-review                   | `reviewer`          | Inherit the planning parent by default unless the plan-writing contract requires an exact independent reviewer.         |
+| Root-owned implementation phase review | `reviewer`          | Target the resolved reviewer ceiling independently of the phase producer.                                               |
+| Phase gate                             | `reviewer`          | Use the configured independent target and fail closed when unavailable.                                                 |
+| Lifecycle gate                         | `reviewer`          | Stay independent of producer context and fail closed rather than substituting same-context self-review.                 |
 
 The calling lifecycle skill remains authoritative when its reviewed contract
 is stricter than this table.
 
+The root owns implementation phase-review selection. A native catalog that
+cannot satisfy the resolved review ceiling must use a policy-resolved
+pre-start CLI reviewer route when available. Record the native mismatch, exact
+target, selection reason, and ordered candidates; never delegate reviewer
+selection to a below-ceiling phase implementer or silently downgrade.
+
 ## Adapt the Request
 
 For every lifecycle dispatch:
@@ -171,12 +177,22 @@ project:
   worktree: root
 ```
 
-## Coordinator and Worker Topology
+## Phase-Agent Topology
+
+The default implementation topology is root → phase implementer plus
+root → phase reviewer. The phase implementer directly owns the planned phase
+tasks. Per-task dispatch is not required.
+
+Optional nested workers or recon agents are benefit-driven and remain subject
+to exact bounded scopes and launcher-owned evidence. They must not widen task
+boundaries, alter plan sequencing, take over phase commits, dispatch the phase
+reviewer, or own user checkpoints.
 
-Use a phase coordinator only when the lifecycle workflow declares that
-topology. A coordinator may dispatch task workers when nesting and authority
-permit it, but it must not widen task boundaries, alter plan sequencing, or
-take over user checkpoints.
+When review findings require fixes, resume the original phase request when the
+host supports continuation. If a completed phase handle is unavailable, allow
+at most one fresh same-target phase implementer for the bounded fix scope and
+link its generic record to the original `request_id` through existing
+`continuation_events`.
 
 For parallel groups, preserve plan-declared isolation. Each worktree receives
 only its assigned phase/task boundaries and must not mutate sibling worktrees.
@@ -229,6 +245,12 @@ fields inside the lifecycle extension.
   engine.
 - Accepted child failure: return the terminal outcome to the lifecycle caller;
   do not select a replacement automatically.
+- A tracked smoke marker makes containment, ownership registration, expected
+  base, and fixture readiness run-validity conditions. Failure of any condition
+  triggers `invalid-run-abort`: terminate accepted child and gate handles owned
+  by that run, preserve the invalidating evidence, clean only journal-owned
+  resources, and stop before any later launch. Never replace an aborted handle
+  or degrade the invalid smoke run to sequential execution.
 - Required gate target unavailable: fail closed.
 - Verification or commit failure after worker completion: lifecycle caller owns
   repair and bookkeeping; do not falsify the child outcome.