work-swarm

Implements approved designs as file-disjoint tasks with concurrent review and verification.

3|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/philipobenito/elelem --skill work-swarm-philipobenito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-swarm
Source: https://github.com/philipobenito/elelem/tree/main/skills/work-swarm
Command: npx skills add https://github.com/philipobenito/elelem --skill work-swarm-philipobenito

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-agent implementation of an approved design is error-prone: tasks collide on shared files, unreviewed code slips through, and completion claims go unverified. This Skill turns coordination into executable control flow, decomposing a design into file-disjoint tasks and running implementation, per-task review, and verification concurrently through a shipped workflow script. ## Core Features & Use Cases - Evidence-Based Sizing: Sizes the whole design against six criteria (uniform change type, no new logic, no new interfaces, determinism, independent verifiability, line count) to decide between a single SIMPLE task and a COMPLEX decomposition. - Enforced Coordination Invariants: The shipped implementation-workflow.js script enforces pre-flight file-disjointness, ready-set scheduling over blockedBy edges, review-before-verification, and an integer fix budget of two as code, not convention. - Checkpoint Drain and Final Review: Verified tasks drain through a user checkpoint in deterministic board order with scoped diffs and evidence, followed by a feature-level review over the full range from baseSha. - Use Case: After approving a design for a multi-module feature, ask the agent to swarm the work: it decomposes the design into disjoint tasks, dispatches implementer, reviewer, and verifier agents concurrently, and commits each verified task only after you approve it at the drain. ## Quick Start Ask the agent to implement the approved design using the orchestrated swarm workflow, decomposing it into file-disjoint tasks with per-task review and verification.

Frequently Asked Questions about work-swarm

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

FAQPage Schema
How do I parallelize implementation of an approved design across multiple agents?

Decompose the design into file-disjoint tasks with blockedBy edges for ordering, then launch the shipped implementation-workflow.js script via the Workflow tool. It dispatches implementer, reviewer, and verifier agents concurrently per ready task while enforcing disjointness and fix budgets as control flow.

How does the skill decide between a single task and a multi-task decomposition?

It sizes the whole design against six evidence criteria: uniform change type, no new logic, no new interfaces, determinism from spec, independent verifiability, and 39 or fewer substantive changed lines. All six passing yields a SIMPLE single-task run; any failure means COMPLEX decomposition.

What happens when a task fails its review or verification?

The task gets an integer fix budget of two round-trips; each fix re-enters code review before verification. If the budget is exhausted, the task fails, dependent tasks are quarantined, verified tasks still drain, and the run stops with a structured report.

Can tasks without a test framework skip test-driven development?

Yes, by marking a task noTestFramework when the project genuinely has no test framework for those files, such as Terraform, shell scripts, or SQL migrations. The marking requires evidence, the reviewer re-checks it against the real diff, and the task's verifyCommand becomes its proof.

What are the limitations of the work-swarm orchestration approach?

It requires an approved design upfront and a Workflow-capable environment; without Workflow it falls back to sequential Agent dispatches, losing concurrency. Tasks sharing mutable state need blockedBy edges or isolated worktrees, and the lead must never patch a failed task's files directly.