
Workflow Create
- 650 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
workflow-create is a ruflo skill that authors Claude Code workflows as either persisted MCP workflow templates with pause-resume lifecycle or native .claude/workflows/*.js orchestration scripts.
About
workflow-create is a ruflo skill for authoring workflows on the surface that fits the job. MCP workflow templates provide persisted definitions with pause-resume lifecycle for long-lived, human-gated, resumable pipelines. Native .claude/workflows/*.js scripts handle agent, parallel, and pipeline fan-out orchestration inside Claude Code. The skill accepts arguments like name, optional --native flag, and --steps N, using claude-flow MCP tools workflow_create, workflow_template, workflow_list, workflow_status, and workflow_delete plus Write, Read, Edit, and Bash. Developers reach for workflow-create when standard slash skills are insufficient and they need durable multi-step agent pipelines with explicit lifecycle control or JavaScript orchestration scripts.
- workflow-create
Workflow Create by the numbers
- 650 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #576 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill workflow-createAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 650 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you create Claude Code agent workflows?
Use workflow-create for development tasks
Who is it for?
Developers building multi-step agent pipelines who need persisted MCP templates or native JavaScript workflow orchestration in Claude Code.
Skip if: Developers running a one-off Task without reusable workflow infrastructure, or teams not using claude-flow MCP workflow tools.
When should I use this skill?
A developer needs to author a new multi-step agent workflow as either an MCP template or a native .claude/workflows/*.js script.
What you get
MCP workflow template with lifecycle controls or native .claude/workflows/*.js orchestration script with agent fan-out steps.
- MCP workflow template
- .claude/workflows/*.js orchestration script
By the numbers
- Supports 2 workflow surfaces: MCP templates and native .claude/workflows/*.js scripts
- Uses 5 claude-flow MCP workflow tools: create, template, list, status, delete
Files
Workflow Create
Author a workflow on whichever surface fits the job.
Pick a surface
- MCP workflow template — a persisted definition with a pause/resume lifecycle. Use for long-lived, human-gated, resumable pipelines.
- *Native `.claude/workflows/.js`** — an imperative orchestration script that fans subagents out. Use for comprehensive fan-out (review, audit, migration, research) where you aggregate structured results in code.
A — MCP workflow template
1. List templates — call mcp__claude-flow__workflow_template to see available templates 2. Create workflow — call mcp__claude-flow__workflow_create with steps, conditions, and execution order 3. List workflows — call mcp__claude-flow__workflow_list to see all defined workflows 4. Check status — call mcp__claude-flow__workflow_status to monitor a workflow 5. Clean up — call mcp__claude-flow__workflow_delete to remove unused workflows
Features: sequential/parallel steps, conditional branching, template inheritance, pause/resume approval gates.
B — Native .claude/workflows/*.js
Write a .js file under .claude/workflows/. It MUST begin with a pure-literal export const meta block; the body runs inside an async wrapper (top-level await/return are legal) with these hooks injected:
| Hook | Purpose |
|---|---|
agent(prompt, opts) | Spawn one subagent; pass opts.schema (JSON Schema) to get validated structured output back |
parallel(thunks) | Run thunks concurrently with a barrier — .filter(Boolean) the results |
pipeline(items, ...stages) | Stream each item through stages independently — prefer this over a barrier |
phase(title) / log(msg) | Progress grouping / narration |
export const meta = {
name: 'my-workflow', // becomes the invocable name — must be a pure literal
description: 'one line',
phases: [{ title: 'Find' }, { title: 'Verify' }],
}
const SCHEMA = { type: 'object', required: ['ok'], properties: { ok: { type: 'boolean' } }, additionalProperties: false }
phase('Find')
const found = await agent('find the things', { schema: SCHEMA, agentType: 'tester' })
phase('Verify')
const checked = await parallel((found.items || []).map((it) => () =>
agent(`verify ${it}`, { schema: SCHEMA })))
return { found, checked: checked.filter(Boolean) }Rules: meta is a pure literal (no variables/calls/interpolation); default to pipeline over parallel; never use Date.now()/Math.random() (they throw — vary by index instead). Validate syntax (the body is ESM-in-async-wrapper, not a bare module):
node -e 'const fs=require("fs");let s=fs.readFileSync(".claude/workflows/my-workflow.js","utf8").replace(/^export\s+const\s+meta/m,"const meta");fs.writeFileSync("/tmp/wf.mjs","let agent,parallel,pipeline,phase,log,args,budget,workflow;async function __wf(){\n"+s+"\n}")' \
&& node --check /tmp/wf.mjs && echo OKRun it with the workflow-run skill or Workflow({ name: 'my-workflow' }). Reference: .claude/workflows/plugin-contract-audit.js. See ADR-0002.
Related skills
FAQ
What two workflow surfaces does workflow-create support?
workflow-create supports MCP workflow templates with persisted pause-resume lifecycle for human-gated pipelines, and native .claude/workflows/*.js scripts for agent, parallel, and pipeline fan-out orchestration inside Claude Code.
Which MCP tools does workflow-create use?
workflow-create uses claude-flow MCP tools including workflow_create, workflow_template, workflow_list, workflow_status, and workflow_delete. These manage template persistence, listing, status checks, and deletion alongside local script authoring.