workflow-composerlisted

# Authoring workflows for Claude Code's Workflow tool A workflow moves a multi-step plan out of the conversation and into code. Normally Claude is the orchestrator: it decides turn by turn what subagent to spawn, and every intermediate result lands back in its context. A workflow inverts that — a script holds the plan, the runtime executes it in isolation, and intermediate results stay in script variables. Only the leaf `agent()` calls spend model tokens; the loops, conditionals, and fan-out are plain deterministic JavaScript. There are **two ways to author one**, and choosing correctly is the first decision: - **Toolkit path (`@workflow-toolbox`)** — for workflows that will be **kept, re-run, and maintained**. You write a typed TypeScript file against a tested pattern library and compile it to a self-contained `.js` artifact. This is the default for anything repeatable. See [the toolkit path](#the-toolkit-path-repeatable-workflows). - **Raw `.js` path** — for **one-offs**, for shapes that fit none of the patterns, or when the toolkit's build chain is not available. You hand-write the orchestrator directly against the runtime globals. See [the raw path](#the-raw-authoring-path-one-offs). Two reference files carry the deep material — read them when a step points you there: - `references/api-reference.md` — every global, option, cap, and constant, each tagged with its evidence tier (documented / observed / verified). - `references/patterns.md` — the seven orche