Help us improve
Share bugs, ideas, or general feedback.
From workflow-builder
Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.
npx claudepluginhub kruxshnx/claude-skills-devin --plugin workflow-builderHow this skill is triggered — by the user, by Claude, or both
Slash command
/workflow-builder:workflow-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Author runnable workflow scripts for Claude Code's Workflow tool: deterministic multi-agent orchestration files (`.js`) 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 whole run is resumable.
README.mdassets/examples/pr-triage.jsassets/templates/fan-out.jsassets/templates/loop-until-budget.jsassets/templates/pipeline.jsexpected_outputs/intake_pr_review.jsonexpected_outputs/scaffold_pipeline.jsexpected_outputs/validate_sample.txtreferences/api_reference.mdreferences/decision_and_intake_guide.mdreferences/orchestration_patterns.mdscripts/scaffold_workflow.pyscripts/validate_workflow.pyscripts/workflow_intake.pyGuides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Author runnable workflow scripts for Claude Code's Workflow tool: deterministic multi-agent orchestration files (.js) 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 whole run is resumable.
Before proposing or writing any workflow, run the intake. Do not skip to code.
Ask what kind of workflow they want. Use this opening question set:
If the user is vague, do NOT stall. Run the recommendation engine to turn whatever you have into 1-2 concrete proposals, then present them with the reasoning:
python scripts/workflow_intake.py --task "their description" \
--units unknown --stages unknown --needs-all unknown --structured unknown
The engine returns a recommended topology (fan-out / pipeline / loop / barrier / judge-panel), model picks, a budget guard, and a one-line rationale per choice. Present those as "Here's what I'd build and why" — never ask the user to re-answer questions they already half-answered.
Confirm the shape with the user (topology + phases + parallel-vs-pipeline) before writing the file. This is the only approval gate.
See references/decision_and_intake_guide.md for the full question framework, the vague-input playbook, and worked recommendation examples.
| Scenario | Use |
|---|---|
| Single sub-agent, one task | plain Agent tool |
| Reusable procedure, Claude picks steps dynamically | a Skill |
| Many sub-agents in a fixed topology, deterministic + resumable | Workflow ✓ |
Workflows earn their cost when work is parallel or multi-stage, must be reproducible, long enough to fail halfway (so resume matters), or benefits from isolating each step in its own context window. For one-off tasks, just use Claude directly.
python scripts/scaffold_workflow.py --topology pipeline --name pr-triage \
--description "Triage open PRs" > .claude/workflows/pr-triage.js
meta block first (pure literal, first statement), then the async body using the injected globals — agent(), pipeline(), parallel(), phase(), log(), budget, args, workflow(). Full surface in references/api_reference.md; copy-paste shapes in references/orchestration_patterns.md.python scripts/validate_workflow.py .claude/workflows/pr-triage.js
export CLAUDE_CODE_WORKFLOWS=1, save the file under .claude/workflows/, then use /workflows to launch and watch it live. Press P to pause/resume, X to skip a sub-agent. Failed agents retry automatically.meta is a pure literal and the first statement — no variables, spreads, template strings, or function calls inside it.Date.now(), Math.random(), argless new Date() break resume — pass timestamps via args.require, fs, process, network) in the orchestrator — that work belongs inside agent() prompts.parallel() takes thunks (() => agent(...)), not bare promises. Default to pipeline() unless a stage needs the whole prior result set.budget.remaining() check — unguarded loops hit the 1000-agent cap.results.filter(Boolean).scripts/workflow_intake.py — intake recommendation engine (topology + model + budget + rationale from vague input).scripts/validate_workflow.py — stdlib linter for the rules above; PASS / WARN / FAIL with line numbers.scripts/scaffold_workflow.py — generate a starter .js for any topology.assets/templates/ — fan-out, pipeline, loop-until-budget starters. assets/examples/ — a complete runnable workflow.All scripts run with --sample (no args) and --help.