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 skills add Infrasity-Labs/dev-gtm-claude-skills --skill workflow-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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)? - Roughly how many tokens / how deep should it go? 2. **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*: ```bash python scripts/workflow_intake.py --task "their description" \ --units unknown --stages unknown --
- ALWAYS start every session with intake (non-negotiable)
- Decide if a workflow is even the right tool
- Build → validate → run loop
- Hard rules (validator enforces these)
- Tooling
python scripts/workflow_intake.py --task "their description" \ python scripts/scaffold_workflow.py --topology pipeline --name pr-triage \ python scripts/validate_workflow.py .claude/workflows/pr-triage.js
What does the workflow-builder skill do?
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.
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill workflow-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.