alirezarezvani/claude-skills / engineering/workflow-builder/skills/workflow-builder
workflow-builder
VerifiedUse when writing or running a Claude Code Workflow-tool script (.js in .claude/workflows/) for fan-out, pipeline, loop or judge-panel sub-agents. Gathers intent with workflow_intake.py, scaffolds with scaffold_workflow.py and validates with validate_workflow.py.
Workflow Builder
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.
ALWAYS start every session with intake (non-negotiable)
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:
- What repeatable, multi-step task do you want to automate?
- What is the one unit of work a single sub-agent does once?
- How many units — a known list, or discovered by looping?
- Do later steps need all prior results at once, or can each item flow on its own?
- Does any step need structured data back (a verdict, a list, scores)?
- Roughly how many tokens / how deep should it go?
-
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 unknownThe 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.
Decide if a workflow is even the right tool
| 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.
Build → validate → run loop
- Scaffold a starter from the confirmed topology:
python scripts/scaffold_workflow.py --topology pipeline --name pr-triage \ --description "Triage open PRs" > .claude/workflows/pr-triage.js - Edit the file:
metablock 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. - Validate before running — catches the parser-fatal mistakes:
python scripts/validate_workflow.py .claude/workflows/pr-triage.js - Run it: enable the feature with
export CLAUDE_CODE_WORKFLOWS=1, save the file under.claude/workflows/, then use/workflowsto launch and watch it live. Press P to pause/resume, X to skip a sub-agent. Failed agents retry automatically.
Hard rules (validator enforces these)
metais a pure literal and the first statement — no variables, spreads, template strings, or function calls inside it.- No non-determinism:
Date.now(),Math.random(), arglessnew Date()break resume — pass timestamps viaargs. - No filesystem / Node APIs (
require,fs,process, network) in the orchestrator — that work belongs insideagent()prompts. parallel()takes thunks (() => agent(...)), not bare promises. Default topipeline()unless a stage needs the whole prior result set.- Guard every open-ended loop with a counter or
budget.remaining()check — unguarded loops hit the 1000-agent cap. - Filter skipped/failed agents:
results.filter(Boolean).
Tooling
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.jsfor 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |