toolkit-scaffoldlisted
Install: claude install-skill home-dev-lab/workflow-toolbox
# 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.
## 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" }
]
}
```
`meta.name` must be non-empty kebab-case (same rule the build enforces). `pattern` is
one of the seven canonical names below; `phase` is the title shown in the `/workflows` UI.
4. **Scaffold, then build + check** (see below).
5. **Fill in the placeholders** — the emitted prompts, the `items`/`claims`/`tasks` data,
a