Workflow Automation
Define and run reusable multi-step agent workflows with claude-flow instead of one-off chat instructions.
Overview
Workflow Automation is an agent skill most often used in Build (also Ship, Operate) that creates and executes multi-step claude-flow workflows from templates like ci, deploy, and release.
Install
npx skills add https://github.com/ruvnet/ruflo --skill workflow-automationWhat is this skill?
- Create, list, execute, and export workflows via npx claude-flow CLI
- Built-in templates: ci, deploy, test, release, review
- YAML workflow structure with named steps, agents, and depends chains
- Environment-scoped execution (e.g. production)
- Explicit skip guidance for simple single-step or ad-hoc tasks
- 5 built-in workflow templates: ci, deploy, test, release, review
Adoption & trust: 817 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You keep repeating multi-step deploy, test, or review sequences in chat instead of a reusable, status-tracked workflow.
Who is it for?
Indie builders using claude-flow who want template-backed CI, deploy, test, release, or review pipelines with agent-per-step orchestration.
Skip if: One-off shell commands, manual debugging sessions, or projects not using claude-flow workflow commands.
When should I use this skill?
Automating processes, creating reusable workflows, orchestrating multi-step tasks; skip for simple single-step tasks or ad-hoc operations.
What do I get? / Deliverables
You get named claude-flow workflows you can execute per environment, export as YAML, and monitor with workflow status—ready to chain into CI/CD habits.
- Created or exported claude-flow workflow definition (YAML)
- Executed workflow run with inspectable status
- Reusable template from ci, deploy, test, release, or review catalog
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
First appears in Build because workflow templates and agent orchestration are created before they automate Ship and Operate pipelines. claude-flow workflow create/execute/status is agent coordination infrastructure, which maps directly to agent-tooling.
Where it fits
Scaffold a deploy-flow workflow with researcher and coder agents and explicit depends edges.
Execute the release template workflow before tagging a solo-shipped SaaS release.
Run the built-in test workflow template as part of pre-ship validation.
Re-run deploy-flow with --env production and poll workflow status after a hotfix.
How it compares
Orchestrates agent steps via claude-flow workflows—not the same as a generic GitHub Actions-only skill with no agent task mapping.
Common Questions / FAQ
Who is workflow-automation for?
Builders on Claude Code ecosystems who use ruflo/claude-flow and want reusable multi-step automation with templates and YAML export.
When should I use workflow-automation?
In Build when defining agent-tooling flows; in Ship when running ci, test, or release templates; in Operate when re-executing deploy-flow against production and checking status.
Is workflow-automation safe to install?
Check the Security Audits panel on this page; workflows can run shell-oriented automation—review exported YAML and environment flags before executing in production.
SKILL.md
READMESKILL.md - Workflow Automation
# Workflow Automation Skill ## Purpose Create and execute automated workflows for complex multi-step processes. ## When to Trigger - Multi-step automated processes - Reusable workflow creation - Complex task orchestration - CI/CD pipeline setup ## Commands ### Create Workflow ```bash npx claude-flow workflow create --name "deploy-flow" --template ci ``` ### Execute Workflow ```bash npx claude-flow workflow execute --name "deploy-flow" --env production ``` ### List Workflows ```bash npx claude-flow workflow list ``` ### Export Template ```bash npx claude-flow workflow export --name "deploy-flow" --format yaml ``` ### View Status ```bash npx claude-flow workflow status --name "deploy-flow" ``` ## Built-in Templates | Template | Description | |----------|-------------| | `ci` | Continuous integration pipeline | | `deploy` | Deployment workflow | | `test` | Testing workflow | | `release` | Release automation | | `review` | Code review workflow | ## Workflow Structure ```yaml name: example-workflow steps: - name: analyze agent: researcher task: "Analyze requirements" - name: implement agent: coder depends: [analyze] task: "Implement solution" - name: test agent: tester depends: [implement] task: "Write and run tests" ``` ## Best Practices 1. Define clear step dependencies 2. Use appropriate agent types per step 3. Include validation gates 4. Export workflows for reuse