workflow-builder — Claude Code plugin: what it does, how to install
Designs and writes deterministic multi-agent JavaScript workflows for Claude Code's Workflow tool. It splits complex tasks across fresh sub-agents to save context.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install workflow-builder@claude-code-skillsWhat workflow-builder does
The plugin generates runnable .js files placed inside .claude/workflows/. Plain JavaScript handles orchestrator control flow, so only leaf agent() calls consume model tokens. If a task description lacks detail, the intake engine suggests an appropriate topology and explains its rationale. It does not stall.
The package includes three Python scripts using standard library modules: an intake engine, a topology scaffolder for 5 patterns (fan-out, pipeline, barrier, loop, judge-panel), and a workflow validator. The validator enforces strict rules: no Math.random(), no unseeded dates, and no direct Node filesystem calls inside the orchestrator script.
Without setting CLAUDE_CODE_WORKFLOWS=1 in your environment, Claude Code keeps the workflow runner disabled.
What it helps with
- scaffold multi-agent scripts for 5 orchestration topologies
- lint workflow scripts against non-deterministic functions
- keep main session context clean by delegating to leaf agents
- recommend an orchestration plan from a vague task prompt
Example prompts for the agent
- /cs-workflow-build review open pull requests for bugs and code style
- /cs-workflow-build pipeline to migrate database schema and run tests
- Generate a fan-out workflow starter with scripts/scaffold_workflow.py
How to install workflow-builder
Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install workflow-builder@claude-code-skillsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about workflow-builder
How to install workflow-builder in Claude Code?
First, register the marketplace source by running /plugin marketplace add alirezarezvani/claude-skills. Then install the plugin with /plugin install workflow-builder@claude-code-skills.
What does workflow-builder do?
It designs, scaffolds, and lints multi-agent JavaScript workflows for Claude Code's Workflow tool. Scripts run isolated sub-agents while maintaining resumable execution.
What prerequisite is required to run the generated workflows?
You must export CLAUDE_CODE_WORKFLOWS=1 in your shell, as the feature is disabled by default. Workflows are then launched and managed via /workflows.
Source text
workflow-builder · MIT
# workflow-builder
Design and write deterministic multi-agent **workflow** scripts for Claude Code's Workflow tool — `.js` files in `.claude/workflows/` that fan work out to fresh-context sub-agents under plain JavaScript control flow. Only leaf `agent()` calls spend tokens, so the main session stays clean and the run is resumable.
Targets the Workflow tool introduced in Claude Code v2.1.147 (gated behind `CLAUDE_CODE_WORKFLOWS=1`, browsable via `/workflows`).
## The intake-first rule
Every workflow-creation session opens with an intake question set (what task, what unit of work, known list vs. loop, barrier vs. pipeline, structured output, depth). **When the user is vague, the skill does not stall or interrogate in a loop** — it runs a deterministic recommendation engine that infers a topology and presents it *with the reasoning* ("here's what I'd build and why"), then confirms before writing any file.
## What's in the box
| Component | Where | What it does |
|---|---|---|
| **Intake recommendation engine** | `skills/workflow-builder/scripts/workflow_intake.py` | Classifies a (vague) task → recommended topology + runner-up + per-stage model plan + budget guard + a one-line rationale per choice. |
| **Workflow validator** | `skills/workflow-builder/scripts/validate_workflow.py` | Stdlib linter for `.js` workflows: pure-literal `meta`, no `Date.now()`/`Math.random()`/argless `new Date()`, no FS/Node APIs in the orchestrator, `parallel()` thunks, guarded loops, `filter(Boolean)`, size cap. PASS / WARN / FAIL with line numbers. |
| **Scaffolder** | `skills/workflow-builder/scripts/scaffold_workflow.py` | Emits a runnable starter for any of 5 topologies (fan-out, pipeline, barrier, loop, judge-panel). |
| **3 references** | `skills/workflow-builder/references/` | API reference · orchestration patterns · decision + intake guide (7-8 sources each). |
| **Templates + example** | `skills/workflow-builder/assets/` | Fan-out / pipeline / loop starters + a complete PR-triage workflow. |
| **Persona agent** | `agents/cs-workflow-architect.md` | Design-first interrogator that refuses to write before the topology is confirmed. |
| **Slash command** | `commands/cs-workflow-build.md` | `/cs-workflow-build <task>` — runs the full intake → scaffold → validate flow. |
## Quick start
```bash
cd skills/workflow-builder
# 1. Turn a vague request into a concrete proposal
python scripts/workflow_intake.py --task "review my open PRs for bugs"
# 2. Scaffold the confirmed topology
python scripts/scaffold_workflow.py --topology pipeline --name pr-triage \
--description "Triage open PRs" > /tmp/pr-triage.js
# 3. Validate before running
python scripts/validate_workflow.py /tmp/pr-triage.js
```
All three tools run with `--sample` (no args) and `--help`.
## Running the workflows it writes
```bash
export CLAUDE_CODE_WORKFLOWS=1 # the feature is off by default
# save the .js under .claude/workflows/ , then launch + watch via /workflows
# P = pause/resume , X = skip a sub-agent ; failed agents retry automatically
```
## Attribution
Conceptually inspired by [Ray Amjad's claude-code-workflow-creator](https://github.com/ray-amjad/claude-code-workflow-creator). All content here was written for this repo against Claude Code's publicly-documented Workflow tool API; no text was copied verbatim.
## License
MIT.
© Alireza Rezvani · MIT · alirezarezvani/claude-skills