| name | workflow-run |
| description | Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool |
| argument-hint | <workflow-id-or-name> |
| allowed-tools | mcp__claude-flow__workflow_execute mcp__claude-flow__workflow_run mcp__claude-flow__workflow_pause mcp__claude-flow__workflow_resume mcp__claude-flow__workflow_cancel mcp__claude-flow__workflow_status Workflow Read Bash |
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_execute or mcp__claude-flow__workflow_run with the workflow ID
- Monitor — call
mcp__claude-flow__workflow_status to check progress and step outcomes
- Pause — call
mcp__claude-flow__workflow_pause to halt at the current step
- Resume — call
mcp__claude-flow__workflow_resume to continue from where paused
- Cancel — call
mcp__claude-flow__workflow_cancel to 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' })
Workflow({ name: 'plugin-contract-audit', args: 'ruflo-agentdb' })
Workflow({ scriptPath: '.claude/workflows/foo.js' })
Workflow({ scriptPath, resumeFromRunId: 'wf_…' })
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 its runId.
- To author a new native workflow, use the
workflow-create skill.
See ADR-0002.