|
| 1 | +--- |
| 2 | +name: rmini |
| 3 | +description: "Launch a compact 5-agent Ruflo swarm for focused task execution. Smaller than /rswarm but still parallel and powerful." |
| 4 | +--- |
| 5 | + |
| 6 | +# Ruflo Mini Swarm — Compact Execution |
| 7 | + |
| 8 | +When this skill is invoked, IMMEDIATELY launch a 5-agent swarm. Do NOT explain how swarms work. Do NOT show code examples. Do NOT ask clarifying questions unless the task is truly ambiguous. ACT. |
| 9 | + |
| 10 | +## Execution Steps |
| 11 | + |
| 12 | +1. Read the user's task (everything they typed after `/rmini`) |
| 13 | +2. **Signal status line**: Run `echo 5 > /tmp/ruflo-mini-active` via Bash to light up the 🍯 indicator |
| 14 | +3. Initialize the swarm in ONE message: |
| 15 | + - Call `mcp__claude-flow__swarm_init` with topology `hierarchical-mesh`, maxAgents 5, strategy `specialized` |
| 16 | + - Spawn ALL 5 agents via the Agent tool with `run_in_background: true` — every agent in ONE message |
| 17 | +4. After spawning, STOP. Do not poll. Do not check status. Wait for agents to return. |
| 18 | +5. When results come back, synthesize and present the combined output. |
| 19 | +6. **Clear status line**: Run `rm -f /tmp/ruflo-mini-active` via Bash to turn off the 🍯 indicator |
| 20 | + |
| 21 | +## The 5 Agents |
| 22 | + |
| 23 | +| # | Agent Type | Role | Task Focus | |
| 24 | +|---|-----------|------|------------| |
| 25 | +| 1 | system-architect | Lead Architect | System design, task decomposition, coordinates all agents | |
| 26 | +| 2 | coder | Primary Dev | Core implementation — frontend or backend depending on task | |
| 27 | +| 3 | tester | Test Engineer | Unit, integration, and edge case tests | |
| 28 | +| 4 | reviewer | Code Reviewer | Quality, patterns, best practices, security check | |
| 29 | +| 5 | researcher | Researcher | Background research, prior art, docs lookup | |
| 30 | + |
| 31 | +Adapt agent assignments to the task — if the task is research-heavy, shift roles accordingly. But ALWAYS spawn 5. |
| 32 | + |
| 33 | +## Rules |
| 34 | + |
| 35 | +- Model: Opus only. Never route to Haiku or Sonnet. |
| 36 | +- Topology: hierarchical-mesh (architect leads, agents coordinate peer-to-peer within their layer) |
| 37 | +- All agents spawned in background in ONE message |
| 38 | +- Each agent gets a clear, specific sub-task with full context — not vague instructions |
| 39 | +- After spawning, STOP and wait |
| 40 | +- When results arrive, review ALL results before presenting final output |
0 commit comments