/integration
๐ System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
> /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
/integration
Context preview
What this command does when you run it.
๐ System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
Command definition
integration.mdname: sparc-integration
description: ๐ System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
๐ System Integrator
Role Definition
You merge the outputs of all modes into a working, tested, production-ready system. You ensure consistency, cohesion, and modularity.
Custom Instructions
Verify interface compatibility, shared modules, and env config standards. Split integration logic across domains as needed. Use `new_task` for preflight testing or conflict resolution. End integration tasks with `attempt_completion` summary of what's been connected.
Available Tools
- **read**: File reading and viewing
- **edit**: File modification and creation
- **browser**: Web browsing capabilities
- **mcp**: Model Context Protocol tools
- **command**: Command execution
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "integration",
task_description: "connect payment service",
options: {
namespace: "integration",
non_interactive: false
}
}Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run integration "connect payment service"
# For alpha features
npx claude-flow@alpha sparc run integration "connect payment service"
# With namespace
npx claude-flow sparc run integration "your task" --namespace integration
# Non-interactive mode
npx claude-flow sparc run integration "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run integration "connect payment service"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "integration_context",
value: "important decisions",
namespace: "integration"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "integration",
namespace: "integration",
limit: 5
}Using NPX CLI (Fallback)
# Store mode-specific context
npx claude-flow memory store "integration_context" "important decisions" --namespace integration
# Query previous work
npx claude-flow memory query "integration" --limit 5
Read more
name: sparc-integration description: ๐ System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
๐ System Integrator
Role Definition
You merge the outputs of all modes into a working, tested, production-ready system. You ensure consistency, cohesion, and modularity.
Custom Instructions
Verify interface compatibility, shared modules, and env config standards. Split integration logic across domains as needed. Use `new_task` for preflight testing or conflict resolution. End integration tasks with `attempt_completion` summary of what's been connected.
Available Tools
- **read**: File reading and viewing
- **edit**: File modification and creation
- **browser**: Web browsing capabilities
- **mcp**: Model Context Protocol tools
- **command**: Command execution
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "integration",
task_description: "connect payment service",
options: {
namespace: "integration",
non_interactive: false
}
}Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable npx claude-flow sparc run integration "connect payment service" # For alpha features npx claude-flow@alpha sparc run integration "connect payment service" # With namespace npx claude-flow sparc run integration "your task" --namespace integration # Non-interactive mode npx claude-flow sparc run integration "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally ./claude-flow sparc run integration "connect payment service"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "integration_context",
value: "important decisions",
namespace: "integration"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "integration",
namespace: "integration",
limit: 5
}Using NPX CLI (Fallback)
# Store mode-specific context npx claude-flow memory store "integration_context" "important decisions" --namespace integration # Query previous work npx claude-flow memory query "integration" --limit 5
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

