/run
Execute a custom stream chain with your own prompts.
> /plugin marketplace add ruvnet/rufloHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/run
Context preview
What this command does when you run it.
Execute a custom stream chain with your own prompts.
Command definition
run.mdstream-chain run
Execute a custom stream chain with your own prompts.
Usage
claude-flow stream-chain run <prompt1> <prompt2> [...] [options]
Minimum 2 prompts required for chaining.
Options
- `--verbose` - Show detailed execution information
- `--timeout <seconds>` - Timeout per step (default: 30)
- `--debug` - Enable debug mode
How It Works
Each prompt in the chain receives the complete output from the previous step as context, enabling complex multi-step workflows.
Examples
Basic Chain
claude-flow stream-chain run \
"Write a function" \
"Add tests for it"
Complex Workflow
claude-flow stream-chain run \
"Analyze the authentication system" \
"Identify security vulnerabilities" \
"Propose fixes with priority levels" \
"Implement the critical fixes" \
"Generate tests for the fixes"
With Options
claude-flow stream-chain run \
"Complex analysis task" \
"Detailed implementation" \
--timeout 60 \
--verbose
Context Preservation
The output from each step is injected into the next prompt:
Step 1: "Write a sorting function"
Output: [function code]
Step 2 receives: "Previous step output:
[function code]
Next step: Optimize for performance"
Best Practices
1. **Clear Instructions**: Make each prompt specific 2. **Logical Flow**: Order prompts in logical sequence 3. **Appropriate Timeouts**: Increase for complex tasks 4. **Verification**: Add verification steps in chain
Read more
stream-chain run
Execute a custom stream chain with your own prompts.
Usage
claude-flow stream-chain run <prompt1> <prompt2> [...] [options]
Minimum 2 prompts required for chaining.
Options
- `--verbose` - Show detailed execution information
- `--timeout <seconds>` - Timeout per step (default: 30)
- `--debug` - Enable debug mode
How It Works
Each prompt in the chain receives the complete output from the previous step as context, enabling complex multi-step workflows.
Examples
Basic Chain
claude-flow stream-chain run \ "Write a function" \ "Add tests for it"
Complex Workflow
claude-flow stream-chain run \ "Analyze the authentication system" \ "Identify security vulnerabilities" \ "Propose fixes with priority levels" \ "Implement the critical fixes" \ "Generate tests for the fixes"
With Options
claude-flow stream-chain run \ "Complex analysis task" \ "Detailed implementation" \ --timeout 60 \ --verbose
Context Preservation
The output from each step is injected into the next prompt:
Step 1: "Write a sorting function" Output: [function code] Step 2 receives: "Previous step output: [function code] Next step: Optimize for performance"
Best Practices
1. **Clear Instructions**: Make each prompt specific 2. **Logical Flow**: Order prompts in logical sequence 3. **Appropriate Timeouts**: Increase for complex tasks 4. **Verification**: Add verification steps in chain
An agent meta-harness for Claude Code and Codex. Agent = Model + Harness. The model writes; the harness gives it tools, memory, loops, sandboxes, and controls so it can actually work.
Repo: ruvnet/ruflo
Other commands on claude-flow.
- /agent-capabilities
Matrix of agent capabilities and their specializations.
Open command - /agent-coordination
Coordination patterns for multi-agent collaboration.
Open command - /agent-spawning
Guide to spawning agents with Claude Code's Task tool.
Open command - /agent-types
Complete guide to all 54 available agent types in Claude Flow.
Open command - /COMMAND_COMPLIANCE_REPORT
Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools (preferred) - `npx claude-flow` commands (as fallback) - No direct implementation calls
Open command - /bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
Open command

