Individual skill

workflow-builder

Use 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.

engineering/workflow-builder/skills/workflow-builder/SKILL.md

Read pinned source

Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 29,522
Repository last updated: Nov 5, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agentic-ai Repository topic
anthropic-claude Repository topic
claude-ai Repository topic
claude-code Repository topic
claude-skills Repository topic
claude-code-skills Repository topic
ai-coding-agent Repository topic
claude-code-plugins Repository topic
developer-tools Repository topic
openai-codex Repository topic
operations Derived category
writing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 1,468 bytes
SKILL.mdcore · 5,278 bytes
SKILL.mdcore · 5,278 bytes
SKILL.mdcore · 5,278 bytes
SKILL.mdcore · 5,278 bytes
assets/examples/pr-triage.jsruns · 3,610 bytes
assets/templates/fan-out.jsruns · 1,127 bytes
assets/templates/loop-until-budget.jsruns · 1,203 bytes
assets/templates/pipeline.jsruns · 1,250 bytes
expected_outputs/intake_pr_review.jsonasset · 1,206 bytes
expected_outputs/scaffold_pipeline.jsruns · 1,233 bytes
expected_outputs/validate_sample.txtdoc · 555 bytes
references/api_reference.mddoc · 6,413 bytes
references/decision_and_intake_guide.mddoc · 5,948 bytes
references/orchestration_patterns.mddoc · 5,522 bytes
scripts/scaffold_workflow.pyruns · 6,816 bytes
scripts/validate_workflow.pyruns · 10,940 bytes
scripts/workflow_intake.pyruns · 10,485 bytes

Read excerpt


# 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.

1. **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)?