菜单
Analyze BLOCKED/DRAIN run history, cluster recurring causes, and propose one structural fix per wedge via `dos decisions`. Use when a fleet keeps stalling and you want a systemic unblock rather than another manual nudge.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Plan and ship the next batch on one lane: run `dos-next-up`, acquire a lease with `dos arbitrate`, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with `dos verify`, render who-does-what, and emit a `dos gate` verdict. Use when you need the current next-work view before dispatching agents.
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and `dos arbitrate` file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
Run one DOS plan-class lifecycle tick from the workspace `[lifecycle]` table: evaluate declared transitions, have a judge approve/defer them, write gated plan-meta edits, and log the cycle. Use when gardening plan lifecycle classes automatically.
Run recurring `dos-dispatch` cycles, switching to `dos-replan` when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.
Tune DOS enforcement policy knobs (`[intervention_policy]`, `[intervention]`, `[improve]`) from false-deny versus held-catch evidence. Use when running `dos enforce-tune` to keep only measured net_task_delta gains and escalate repeated non-keeps.
| name | dos-unstick |
| description | Analyze BLOCKED/DRAIN run history, cluster recurring causes, and propose one structural fix per wedge via `dos decisions`. Use when a fleet keeps stalling and you want a systemic unblock rather than another manual nudge. |
Stop the cause, not the instance. A one-off unblock fixes today's stall;
/dos-unstickasks the different question — what keeps blocking progress across runs, and what one change would unblock it? It mines the run archive, normalizes every blocker to a canonical cause key, clusters the recurring ones, ranks by recurrence × measured stall-cost, and proposes a structural fix per cluster. Read-only; it writes no code and surfaces findings, never acts.
The shape: mine the trail → key each blocker → cluster the recurring ones →
rank → propose a structural fix → surface. The recurrence fold is the kernel's
(recurring_wedge); the cause TAXONOMY is [reasons] data — a host adds a cause
by declaring a reason, never by editing this skill.
--runs <N> (optional) — how many most-recent runs to sweep (default: a recent
window). --since <Nd|Nh> overrides with a time window.--min-recurrence <N> (optional) — a cause is "recurring" at N+ distinct runs
(default 2 — the recurring_wedge DEFAULT_MIN_RECURRENCE).dos doctor --workspace . --json
Read paths.runs (the run-archive dir to sweep) and run dos man wedge to read
the closed reason vocabulary — the canonical cause keys this workspace knows.
Use these; never hardcode a run path or a cause string. A cause the workspace
cares about is a declared [reasons] entry, surfaced by dos man wedge.
dos man wedge
Read the run records under paths.runs (read each once, sequentially — no
tailing/polling, the very anti-pattern this sweep exists to surface). For each
run that STOPPED on a BLOCKED / DRAIN / STALLED outcome, capture: the run id, the
iteration, the blocker text, and the measured stall cost ($/wall) if recorded.
No host evidence reader is wired by default. A host that curates a postmortem stream or a hand-ranked next-hits file can expose it as a
dos.evidence_sourcesdriver hook; the generic sweep reads only the run-archive verdicts.loga one-line note when a host evidence source is not consulted — no silent gap (the/dos-dispatch-loopdiscipline).
Normalize each blocker text to ONE cause key from the declared [reasons]
vocabulary (the host's cue table maps an Outcome-cell string to a key — the same
kernel-catalog ↔ host-cue split dos man wedge documents). A blocker that maps to
no declared cause is keyed UNCATEGORIZED (surfaced as a gap, never dropped).
Feed the keyed blockers to the recurrence fold. It clusters by cause key, ranks by
recurrence (dominant) × stall-cost (the tie-break), and tells you whether the
cause the CURRENT sweep hit spans >= min-recurrence distinct runs:
The fold is recurring_wedge.classify_recurring_wedge — pure, frozen-data-in,
verdict-out. A cluster spanning ≥ min-recurrence runs is recurring (worth a
structural fix); a one-off is noise the sweep cannot help.
For each recurring cluster, propose a structural change — a contract edit, an
oracle rung, a preflight check — that would stop the cause RECURRING, not a
one-off unblock of today's instance. Rank the proposals by the cluster's
stall-score (recurrence × cost). The cause→fix mapping is the host's [reasons]
fix-sketch (the reason's documented remediation), not a literal in this skill.
Route each proposal to the operator-decision queue:
dos decisions add # the routing surface; the proposal is a finding, not an edit
This skill is read-only: it writes no code, edits no plan, takes no lease. A recurring cause is a finding for a human (or a follow-up plan), not an auto-applied change — the structural fix is a real engineering decision.
dos.evidence_sources hook. log when it is not consulting one.dos man wedge and the path from dos doctor --json.