Workflow Create

You get two ways to build workflows: MCP templates for long-running, pausable processes with approval gates, or native JavaScript files in .claude/workflows/ for fan-out orchestration. The native route is more interesting. You write imperative code with agent(), parallel(), and pipeline() hooks, return structured data, and the system enforces determinism by blocking Date.now() and Math.random(). The meta export must be a pure literal so the runtime can extract it without execution. Default to pipeline over parallel to avoid unnecessary barriers. If you're doing comprehensive audits, migrations, or research where you need to spawn subagents and aggregate results in code, this is the right tool.

skills.sh installs: 740
GitHub stars: 81.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add ruvnet/ruflo --skill workflow-create --agent claude-code

Installs into .claude/skills of the current project.

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

List templates — call mcp__plugin_ruflo-core_ruflo__workflow_template to see available templates
Create workflow — call mcp__plugin_ruflo-core_ruflo__workflow_create with steps, conditions, and execution order
List workflows — call mcp__plugin_ruflo-core_ruflo__workflow_list to see all defined workflows
Check status — call mcp__plugin_ruflo-core_ruflo__workflow_status to monitor a workflow
Clean up — call mcp__plugin_ruflo-core_ruflo__workflow_delete to remove unused workflows