toolkit-scaffoldlisted

# Toolkit scaffold — a job description → a build-clean `.workflow.ts` The toolkit exists to kill one failure mode: hand-rolling the `defineWorkflow` wrapper, the imports, the `meta`, and each pattern call from scratch every time — re-deriving the boilerplate by hand. `workflow-toolbox scaffold` turns a small structured spec into a **complete, build-clean** workflow skeleton that compiles, builds, and passes the linter **as-is** — a working starting point you then customize. It is deliberately lightweight (the toolkit's P1/P6 philosophy): the scaffolder only assembles the skeleton. **Choosing the patterns from the job description is your job** — that is the judgment the L1 table below encodes. ⚠ **Check first whether a workflow is even the right artifact.** Every pattern below spends `agent()` calls, and `agent()` always launches a Claude Code subagent — there is no pattern, and no `agentType`/`verifierType` knob on top of one, that runs a role with zero Claude models involved. This skill covers workflows only. ## The workflow 1. **Read the job.** What does the workflow need to do, end to end? 2. **Pick the patterns** (L1 table). One pattern per logical step; name a phase for each. 3. **Write the spec** — a tiny JSON file: ```json { "meta": { "name": "my-workflow", "description": "One-line summary." }, "steps": [ { "pattern": "classifyAndAct", "phase": "Route" }, { "pattern": "adversarialVerification", "phase": "Verify" } ] } ```