Individual skill

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.

notion-skills/workflow-builder/SKILL.md

Read pinned source

Source commit 02cfefb3a213041de8b80bc659ebc5f17b5e746a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 11, 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): 164
Repository last updated: Jun 28, 2026
License: MIT

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

ai-citation Repository topic
ai-visibility Repository topic
claude Repository topic
claude-skills Repository topic
geo Repository topic
skills Repository topic
dev-gtm Repository topic
design 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,366 bytes
SKILL.mdcore · 5,252 bytes
SKILL.mdcore · 5,252 bytes
SKILL.mdcore · 5,252 bytes
SKILL.mdcore · 5,252 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 · 5,613 bytes
references/decision_and_intake_guide.mddoc · 5,260 bytes
references/orchestration_patterns.mddoc · 4,816 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)?