swarm-coordination

Coordinate multiple agents to manage OpenCode swarm workflows.

729|67|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/joelhooks/swarm-tools --skill swarm-coordination-joelhooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-coordination
Source: https://github.com/joelhooks/swarm-tools/tree/main/packages/claude-code-swarm-plugin/skills/swarm-coordination
Command: npx skills add https://github.com/joelhooks/swarm-tools --skill swarm-coordination-joelhooks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode swarm workflows often require breaking work into parallel tasks and coordinating multiple agents to maintain consistency, visibility, and faster delivery.

Core Features & Use Cases

  • Decomposition & Planning: Break complex work into independent subtasks that can run concurrently.
  • Worker Orchestration: Spawn and manage subagents, assign tasks, and balance workloads.
  • Coordination & Review: Track progress with persistent logs, handle file reservations, and perform post-completion reviews.
  • Use Case: When shipping a feature with multiple components (frontend, API, tests) across a shared codebase, this skill coordinates tasks to minimize conflicts and maximize throughput.

Quick Start

To begin coordinating a swarm task, initialize the swarm planning flow and spawn parallel workers for a multi-file change, then monitor progress and review results.

Frequently Asked Questions about swarm-coordination

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

FAQPage Schema
How do I coordinate multiple agents for parallel task decomposition in OpenCode?

Multi-agent coordination in OpenCode breaks complex work into independent subtasks that run concurrently. You initialize a swarm planning flow, spawn parallel workers for multi-file changes, and monitor progress through persistent logs and post-completion reviews.

What's the best way to manage file reservation conflicts across parallel agents?

File reservation conflicts across parallel agents are managed through coordinated spawning workflows. The swarm coordination skill assigns file reservations to each worker, tracks progress with persistent logs, and performs reviews to minimize conflicts and maximize throughput.

When do I need multi-agent swarm workflows for software engineering tasks?

Multi-agent swarm workflows are needed when shipping features with multiple components across a shared codebase, such as frontend, API, and tests. Tasks that benefit from decomposition, parallel execution, and cross-agent collaboration across files and milestones are ideal candidates.

Does OpenCode swarm coordination require Swarm Mail integration?

OpenCode swarm coordination requires integration with Swarm Mail and hive-like task tracking. These components provide the persistent logging and cross-agent communication needed to manage subagent orchestration and track progress across milestones.

Can I balance workloads across spawned subagents in a multi-agent swarm?

Workload balancing across spawned subagents is supported through worker orchestration. The coordination skill manages subagent spawning, assigns tasks based on decomposition, and balances workloads while tracking progress with persistent logs and file reservations.

What are the limitations of using swarm coordination for single-file changes?

Swarm coordination is not suited for single-file or linear tasks that lack decomposition opportunities. It is designed for parallel execution and cross-agent collaboration across multiple files and milestones, so simpler tasks gain minimal throughput benefit from spawning workers.