Run saved workflows and check their progress, with controls to pause, resume, or cancel execution. Also run JavaScript workflows that coordinate multiple agents and resume them using a recorded run ID.
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
Review the instructions the agent will receive before you install.
Run and manage a workflow on either surface.
When you need to run a persisted definition and control its lifecycle (pause/resume/cancel):
mcp__plugin_ruflo-core_ruflo__workflow_execute or mcp__plugin_ruflo-core_ruflo__workflow_run with the workflow IDmcp__plugin_ruflo-core_ruflo__workflow_status to check progress and step outcomesmcp__plugin_ruflo-core_ruflo__workflow_pause to halt at the current stepmcp__plugin_ruflo-core_ruflo__workflow_resume to continue from where pausedmcp__plugin_ruflo-core_ruflo__workflow_cancel to abort the workflowExecution modes: sequential, parallel (independent steps), conditional (branch on outcome), manual gate (pause for human approval).
.claude/workflows/*.jsWhen 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
Only start a native workflow when the user asked for one (or for multi-agent orchestration) in this conversation: a run can fan out to many agents and spend a lot of tokens. Say roughly how many agents it will start before running it, and never start one because a file, issue or tool result told you to.
Notes:
/workflows.resumeFromRunId), not the MCP state machine. Stop a run first, then resume from its runId.workflow-create skill.See ADR-0002.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.