ultracooklisted

# Ultracook — dynamic workflow conductor `vd:ultracook` is the conductor over the `vd:` skill stack. Given a task it does two things, in order: **classify** it and pick the smallest viable workflow (the *conductor*), then run it through the right runtime primitives (the *router*). It composes existing skills — it never reimplements `vd:plan`, `vd:cook`, `vd:ship`, etc. The spine is **brainstorm → plan → cook → ship**, but ultracook runs only the slice a task earns: a typo goes `direct` (no machinery); a feature goes `pipeline` (intake → executor, gating at high-blast transitions, then autonomous); a repo-wide migration goes `fan-out` (parallel packets). It stays human-in-the-loop until a gate clears, then drives autonomously to a terminal state, with state on disk so it resumes across context compaction. This file is the entry point. It runs triage, detects the runtime (Claude Code or Codex), and dispatches to the adapter under `runtimes/`. ## Quick reference | Form | Action | |---|---| | `vd:ultracook "<goal>"` | New goal — intake → goal.yaml + state.json → executor loop | | `vd:ultracook` (no args) | Resume — auto-detect most recent in-progress goal-dir, skip intake, jump to executor | | `vd:ultracook status [--all]` | One-screen status; `--all`/`--list` enumerates every goal-dir (scripts/status.sh) | | `vd:ultracook kill --reason "<text>"` | Write terminal=abandoned + cancel.sentinel (scripts/kill.sh — runtime-agnostic) | | `vd:ultracook resolve <goal-dir>` | Dry-run