agentleFS
Sign inStart free
fidgetcodingfidgetcoding/fidgetflo/.agents/skills/swarm-orchestration/SKILL.md

swarm-orchestration

Skill1 starsChanged 7 months agoMITView on GitHub

Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules. Use when: 3+ files need changes, new feature implementation, cross-module refactoring, API changes with tests, security-related changes, performance optimization across codebase, database schema changes. Skip when: single file edits, simple bug fixes (1-2 lines), documentation updates, configuration changes, quick exploration.

6 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start a new swarm with hierarchical topology (anti-drift)

    line 33
  2. Distinctive:

    Check the current swarm status

    line 69
  3. Distinctive:

    Check memory for existing patterns before starting

    line 111
  4. Distinctive:

    Use hierarchical topology for coordination

    line 112
  5. Distinctive:

    Document any new learnings

    line 114

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swarm Orchestration Skill

Purpose

Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules.

When to Trigger

  • 3+ files need changes
  • new feature implementation
  • cross-module refactoring
  • API changes with tests
  • security-related changes
  • performance optimization across codebase
  • database schema changes

When to Skip

  • single file edits
  • simple bug fixes (1-2 lines)
  • documentation updates
  • configuration changes
  • quick exploration

Commands

Initialize Swarm

Start a new swarm with hierarchical topology (anti-drift)

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

Example:

npx @claude-flow/cli swarm init --topology hierarchical --max-agents 6 --strategy specialized

Route Task

Route a task to the appropriate agents based on task type

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

Example:

npx @claude-flow/cli hooks route --task "implement OAuth2 authentication flow"

Spawn Agent

Spawn a specific agent type

npx @claude-flow/cli agent spawn --type [type] --name [name]

Example:

npx @claude-flow/cli agent spawn --type coder --name impl-auth

Monitor Status

Check the current swarm status

npx @claude-flow/cli swarm status --verbose

Orchestrate Task

Orchestrate a task across multiple agents

npx @claude-flow/cli task orchestrate --task "[task]" --strategy adaptive

Example:

npx @claude-flow/cli task orchestrate --task "refactor auth module" --strategy parallel --max-agents 4

List Agents

List all active agents

npx @claude-flow/cli agent list --filter active

Scripts

ScriptPathDescription
swarm-start.agents/scripts/swarm-start.shInitialize swarm with default settings
swarm-monitor.agents/scripts/swarm-monitor.shReal-time swarm monitoring dashboard

References

DocumentPathDescription
Agent Typesdocs/agents.mdComplete list of agent types and capabilities
Topology Guidedocs/topology.mdSwarm topology configuration guide

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free