swarm

Name: swarm
Availability: InStock
Author: mikecubed

Coordinates adaptive agent swarms to decompose and solve complex work.

Updated Mar 18, 2026

Search Tags:#agent #orchestration #decomposition #swarm #topology #coordinator

Ready to run

npx skills add https://github.com/mikecubed/agent-orchestration --skill swarm-mikecubed

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swarm
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/flow/skills/swarm
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill swarm-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dynamically decompose large, uncertain work into a coordinated swarm of agents guided by a central coordinator, enabling scalable, adaptive execution.

Core Features & Use Cases

Roles and governance: coordinator, scout, domain agents, synthesizer, reviewer, and the SWARM.md convergence log.
Topology-aware orchestration: coordinator-worker, pipeline, wave/batch, hierarchical, and mesh topologies with runtime decomposition.
Validation and guardrails: explicit validation commands, TDD discipline for code-bearing domains, and convergence rounds for safe integration.

Quick Start

Define your swarm goal and execute the orchestration to spawn and coordinate domain agents.

Frequently Asked Questions about swarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I orchestrate multiple agents to decompose large interdependent projects?▼

Agent orchestration for large projects uses a central coordinator to dynamically decompose work into adaptive domain agents, applying topology selection and convergence gates to guide scalable execution.

What topology should I use for agent orchestration?▼

Agent orchestration supports coordinator-worker, pipeline, wave/batch, hierarchical, and mesh topologies. The coordinator selects and applies runtime decomposition based on your project's structure.

How does a coordinator-led agent swarm manage integration and convergence?▼

Coordinator-led swarms manage integration by logging convergence in a SWARM.md file and running convergence rounds, using validation commands and TDD discipline to ensure safe integration of code-bearing domains.

When should I use an adaptive agent swarm instead of a single agent for project execution?▼

Adaptive agent swarms are suited for large, uncertain, and interdependent projects where dynamic domain decomposition, topology-aware coordination, and governance artifacts provide scalable execution.

Do I need to define specific roles to set up an agent swarm for complex work?▼

Yes, setting up an agent swarm requires defining roles like coordinator, scout, domain agents, synthesizer, and reviewer to establish governance and guide the decomposition process.

What are the limitations of using coordinator-led topologies for agent orchestration?▼

Coordinator-led topologies require explicit validation commands and convergence rounds for safe integration, meaning complex interdependent projects need strict governance to prevent runtime decomposition failures.