
Agent Swarm Issue
Turn a GitHub issue into a decomposed multi-agent swarm with tracked progress and issue comments for solo builders shipping with Claude Flow.
Overview
agent-swarm-issue is an agent skill most often used in Build (also Ship review, Operate iterate) that maps GitHub issues to multi-agent swarm tasks with orchestration and progress comments.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-swarm-issueWhat is this skill?
- Converts GitHub issues into swarm tasks with automatic decomposition
- Uses gh CLI plus MCP GitHub (get/create/update issues and comments) and claude-flow orchestration
- Pre-hooks initialize topology and stash issue metadata in swarm memory; post-hooks write progress back to the issue
- TodoRead/TodoWrite integrated with Bash, Read, Write for execution loops
- Coordination type agent (`swarm-issue`) with explicit tool list for auditability
- 10+ named MCP/bash tools in frontmatter
- Pre and post coordination hook pairs documented
Adoption & trust: 638 installs on skills.sh; 58.5k GitHub stars; 0/3 security scanners passed (skills.sh audits).
What problem does it solve?
A GitHub issue describes a large change but your agent has no structured way to split it into coordinated sub-agents with visible progress on the ticket.
Who is it for?
Indie maintainers using GitHub Issues plus Claude Flow MCP who want issue-driven parallel agents without manual task spreadsheets.
Skip if: Repos without GitHub, teams blocked from MCP/bash/git tools, or trivial one-line fixes that do not need swarm overhead.
When should I use this skill?
A GitHub issue should drive swarm_init, agent_spawn, and task_orchestrate with progress mirrored back to the issue.
What do I get? / Deliverables
The issue becomes an orchestrated swarm with assignments, memory-backed metadata, and updated comments plus a coordination report after the run.
- Decomposed swarm task plan
- Updated issue comments and follow-up issues
- Swarm coordination report
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Primary shelf is Build agent-tooling because the skill orchestrates swarm_init, agent_spawn, and task_orchestrate around implementation work. Agent-tooling captures GitHub MCP tools, memory_usage, and coordination hooks rather than generic PM docs.
Where it fits
Spawn specialists from a feature issue body to implement API, tests, and docs in parallel.
Attach a review swarm to a release-blocking issue and post incremental findings as issue comments.
Re-open a production bug issue and re-init swarm topology with memory of prior remediation steps.
How it compares
Issue-to-swarm orchestration workflow—not a replacement for vanilla code review skills or standalone gh issue templates.
Common Questions / FAQ
Who is agent-swarm-issue for?
Solo and small-team builders running Claude Flow with GitHub MCP who coordinate multi-step work from issues.
When should I use agent-swarm-issue?
During Build when an issue needs decomposition into agents; during Ship when tracking review/fix swarms on the same issue; during Operate when iterating on production bugs filed as issues.
Is agent-swarm-issue safe to install?
It uses shell, git, GitHub APIs, and file write tools; review the Security Audits panel on this page before granting MCP and Bash in your environment.
SKILL.md
READMESKILL.md - Agent Swarm Issue
--- name: swarm-issue description: GitHub issue-based swarm coordination agent that transforms issues into intelligent multi-agent tasks with automatic decomposition and progress tracking type: coordination color: "#FF6B35" tools: - mcp__github__get_issue - mcp__github__create_issue - mcp__github__update_issue - mcp__github__list_issues - mcp__github__create_issue_comment - mcp__claude-flow__swarm_init - mcp__claude-flow__agent_spawn - mcp__claude-flow__task_orchestrate - mcp__claude-flow__memory_usage - TodoWrite - TodoRead - Bash - Grep - Read - Write hooks: pre: - "Initialize swarm coordination system for GitHub issue management" - "Analyze issue context and determine optimal swarm topology" - "Store issue metadata in swarm memory for cross-agent access" post: - "Update issue with swarm progress and agent assignments" - "Create follow-up tasks based on swarm analysis results" - "Generate comprehensive swarm coordination report" --- # Swarm Issue - Issue-Based Swarm Coordination ## Overview Transform GitHub Issues into intelligent swarm tasks, enabling automatic task decomposition and agent coordination with advanced multi-agent orchestration. ## Core Features ### 1. Issue-to-Swarm Conversion ```bash # Create swarm from issue using gh CLI # Get issue details ISSUE_DATA=$(gh issue view 456 --json title,body,labels,assignees,comments) # Create swarm from issue npx ruv-swarm github issue-to-swarm 456 \ --issue-data "$ISSUE_DATA" \ --auto-decompose \ --assign-agents # Batch process multiple issues ISSUES=$(gh issue list --label "swarm-ready" --json number,title,body,labels) npx ruv-swarm github issues-batch \ --issues "$ISSUES" \ --parallel # Update issues with swarm status echo "$ISSUES" | jq -r '.[].number' | while read -r num; do gh issue edit $num --add-label "swarm-processing" done ``` ### 2. Issue Comment Commands Execute swarm operations via issue comments: ```markdown <!-- In issue comment --> $swarm analyze $swarm decompose 5 $swarm assign @agent-coder $swarm estimate $swarm start ``` ### 3. Issue Templates for Swarms ```markdown <!-- .github/ISSUE_TEMPLATE$swarm-task.yml --> name: Swarm Task description: Create a task for AI swarm processing body: - type: dropdown id: topology attributes: label: Swarm Topology options: - mesh - hierarchical - ring - star - type: input id: agents attributes: label: Required Agents placeholder: "coder, tester, analyst" - type: textarea id: tasks attributes: label: Task Breakdown placeholder: | 1. Task one description 2. Task two description ``` ## Issue Label Automation ### Auto-Label Based on Content ```javascript // .github$swarm-labels.json { "rules": [ { "keywords": ["bug", "error", "broken"], "labels": ["bug", "swarm-debugger"], "agents": ["debugger", "tester"] }, { "keywords": ["feature", "implement", "add"], "labels": ["enhancement", "swarm-feature"], "agents": ["architect", "coder", "tester"] }, { "keywords": ["slow", "performance", "optimize"], "labels": ["performance", "swarm-optimizer"], "agents": ["analyst", "optimizer"] } ] } ``` ### Dynamic Agent Assignment ```bash # Assign agents based on issue content npx ruv-swarm github issue-analyze 456 \ --suggest-agents \ --estimate-complexity \ --create-subtasks ``` ## Issue Swarm Commands ### Initialize from Issue ```bash # Create swarm with full issue context using gh CLI # Get complete issue data ISSUE=$(gh issue view 456 --json title,body,labels,assignees,comments,projectItems) # Get referenced issues and PRs REFERENCES=$(gh issue view 456 --json body --jq '.body' | \ grep -oE '#[0-9]+' | while read -r ref; do NUM=${ref#\#} gh iss