Skip to content
cccskills
FreePublished on GitHubEnglish overview

swarm-orchestration

Coordinate multiple AI agents for feature development or refactoring across several files. The skill guides team setup, task assignment, status checks, and recording successful approaches for use in later work.

OriginalShow the original description

Multi-agent swarm coordination for complex tasks. Use when: 3+ files need changes, new features, refactoring. Skip when: single file edits, simple fixes, documentation.

AI rating70/ 100See how to install

Good for

  • Coordinating changes across three or more files
  • Assigning feature development tasks to multiple agents
  • Checking progress during a shared refactoring task
  • Recording successful approaches for future work

Overview

What it does

This skill coordinates multiple AI agents for development work that spans several files. It uses @claude-flow/cli to initialize a group of agents, route tasks to suitable agents, and check the group's current status. The initialization example specifies a hierarchical structure, with a chain of coordination and a maximum of eight agents.

When it helps

Use it when a task requires changes to three or more files, when developing a new feature, or when refactoring the structure of existing code. It also describes a working process that starts by checking saved knowledge for existing patterns. After the work is complete, successful patterns and newly learned information are recorded for later use. This makes both coordination during the task and recording what worked part of the process.

Example requests

  • “Assign the work for this new feature across the relevant agents; it involves several files.”
  • “Check the status of the agents working on the refactoring.”

Notes

The listed commands use npx @claude-flow/cli. Single-file edits, simple fixes, and documentation work are explicitly excluded from this skill's intended scope.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodUsage conditions include changes to three or more files, while exclusions include single-file edits.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
BPartly lackingInitialization, routing, and status commands are provided, but recording methods and output formats are not specified.
SafetyAre sending data, deleting files, and running commands disclosed?
BPartly lackingIt executes commands through npx and assigns agent tasks, but provides no procedure for confirming the scope of changes.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingUse of npx @claude-flow/cli is shown, but environment preparation steps are absent.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md1.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Swarm Orchestration Skill

Purpose

Multi-agent swarm coordination for complex tasks.

When to Trigger

  • 3+ files need changes
  • new features
  • refactoring

When to Skip

  • single file edits
  • simple fixes
  • documentation

Commands

Initialize Swarm

Start a new swarm with hierarchical topology

npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8

Route Task

Route a task to the appropriate agents

npx @claude-flow/cli hooks route --task "[task description]"

Monitor Status

Check the current swarm status

npx @claude-flow/cli swarm status

Best Practices

  1. Check memory for existing patterns before starting
  2. Use hierarchical topology for coordination
  3. Store successful patterns after completion
  4. Document any new learnings

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-model-descriptions

FreeSummaryAI rating 80

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo78.3KUpdated Oct 22, 2026

adr-create

FreeSummaryAI rating 80

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo78.3KUpdated Oct 22, 2026

adr-index

FreeSummaryAI rating 90

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo78.3KUpdated Oct 22, 2026

adr-reindex

FreeSummaryAI rating 70

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo78.3KUpdated Oct 22, 2026

adr-review

FreeSummaryAI rating 80

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo78.3KUpdated Oct 22, 2026

adr-verify

FreeSummaryAI rating 90

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo78.3KUpdated Oct 22, 2026

See all skills by ruvnet

Report a problem with this skill