Samiixo

Swarm Skill — Development skill for Claude Code

Development community

Скилл swarm — оркестратор роя субагентов.

How to install Swarm Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Samiixo/Swarm-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Swarm Skill does

Скилл swarm — оркестратор роя субагентов. Агент-оркестратор не пишет код и не проводит ревью сам: он разбивает задачу, собирает команду, гоняет конвейер разведка → план → контракт → параллельное исполнение → машинные шлюзы → цикл ревью и останавливается только на настоящем PASS от ревьюеров.

Alternatives in Development

  • Meal Plan — План питания на неделю 17 ★
  • Landing Skill — Скилл для Claude Code: лендинги, которые не выглядят как вайб-код 16 ★
  • Razbor Servisa — Скилл для Claude Code: превращает сервис без API в CLI-инструмент, которым управляет агент 16 ★

README

![SWARM](assets/banner.png)

**An orchestrator skill that turns one agent into a swarm.**

`recon → plan → contract → parallel execution → machine gates → review loop → PASS`

[![License: MIT](https://img.shields.io/badge/license-MIT-D6FF00.svg)](LICENSE) ![Skill](https://img.shields.io/badge/skill-SKILL.md-111111.svg) ![No dependencies](https://img.shields.io/badge/dependencies-none-111111.svg)


Most coding agents fail at one of two things: they do everything themselves, slowly and with a shallow review, or they fan out work without any way to tell whether the result is actually good. `swarm` takes a third route — a **gated pipeline with a bounded feedback loop**:

  • the orchestrator decides, subagents produce, machines verify;
  • nothing counts as done until a real PASS comes back from a reviewer;
  • every stage has a gate, and gates run cheapest-first;
  • the loop is bounded — it stops and reports instead of rewriting forever.

The pipeline

![The swarm pipeline](assets/pipeline.png)

Stage What happens Who runs it
0 · Recon Map files, patterns, tools, risks. Never skipped. explore
1 · Plan Split into independent subtasks, each with its own done-when. planner / architect
2 · Contract Fix data shape + API signatures, name one owner per state, commit it. orchestrator + state owner
3 · Parallel Disjoint file zones, own branches, background calls. workers × N
4 · Gates Typecheck → lint → unit → integration → build → e2e → human. machines
5 · Review Every reviewer answers the same verdict block. Route FAILs back. reviewers
6 · Finalize Commit, hand-off note, and the exact steps to verify by hand. orchestrator

The rules that make it work

  1. The orchestrator does not write code and does not review code. It routes. A stage that was only narrated — never actually delegated — is not done.
  2. **M