Workflow Run
Run and manage a workflow on either surface.
A — MCP workflow lifecycle
When you need to run a persisted definition and control its lifecycle (pause/resume/cancel):
- Execute — call
mcp__claude-flow__workflow_executeormcp__claude-flow__workflow_runwith the workflow ID - Monitor — call
mcp__claude-flow__workflow_statusto check progress and step outcomes - Pause — call
mcp__claude-flow__workflow_pauseto halt at the current step - Resume — call
mcp__claude-flow__workflow_resumeto continue from where paused - Cancel — call
mcp__claude-flow__workflow_cancelto abort the workflow
Execution modes: sequential, parallel (independent steps), conditional (branch on outcome), manual gate (pause for human approval).
B — Native .claude/workflows/*.js
When you need a deterministic subagent fan-out, run a named native workflow with the Workflow tool. The named workflows are the meta.name of each .claude/workflows/*.js file (list them with /workflow or ls .claude/workflows/).
Workflow({ name: 'plugin-contract-audit' }) // run a named workflow
Workflow({ name: 'plugin-contract-audit', args: 'ruflo-agentdb' }) // pass args → the script's `args` global
Workflow({ scriptPath: '.claude/workflows/foo.js' }) // run a script by path
Workflow({ scriptPath, resumeFromRunId: 'wf_…' }) // resume — unchanged agent() calls return cached
Notes:
- A native workflow runs in the background; you are notified on completion (don't poll). Watch live progress with
/workflows. - Pause/resume here is journal-based (
resumeFromRunId), not the MCP state machine. Stop a run first, then resume from itsrunId. - To author a new native workflow, use the
workflow-createskill.
See ADR-0002.