Parallel Agents Skill · Devops

Parallel Agents: Run Coding Agents Side by Side Without an App

Run coding agents in parallel without an app, inspired by herdr: git worktrees per task, a STATUS.md board, branch review, ordered merges and cleanup.

Updated November 2026.

  • Git worktrees
  • Multi-agent
  • Status board
  • Safe merges
  • No app

About This Skill

Parallel Agents lets a lead agent split one coding task into independent pieces, run several agent sessions on them in separate git worktrees, track them in a plain STATUS.md board, then review, merge in order and clean up. Herdr is a desktop app; this is an app-free skill that needs only git and a way to open more sessions, and it falls back to one-by-one work when only one session is available. Inspired by herdr by herdrdev (Apache-2.0). Not affiliated.

New to the original tool? Read our Herdr App guide: what it does, how to install it and how this skill differs.

Quick Start

  1. 1Download the skill (1 credit) and unzip the parallel-agents folder.
  2. 2Copy the folder into your skills directory: Antigravity ~/.gemini/config/skills/ (or .agents/skills/ in a project), Claude Code ~/.claude/skills/, Codex ~/.agents/skills/.
  3. 3Start from a clean base branch with passing tests and git user.name and user.email set.
  4. 4Approve the task table, then start one agent per worktree in separate terminals, tmux windows or your agent's own sub-sessions.
Example Command
Fan out this task to parallel agents using worktrees

Core Capabilities

Independent task split

Groups changes into 2 to 4 tasks with explicit file lists and resolves any overlap before work starts.

One worktree per task

Creates an agent/<slug> branch and a sibling worktree for each task so workers never share files or branches.

Self-contained briefs

Writes a BRIEF.md per worker with goal, allowed files, background, done criteria and commit rules.

STATUS.md board

Tracks each worker as Working, Blocked, Done or Idle in a git-excluded markdown file.

Reviewed, ordered merges

Scope-checks and tests each branch, merges foundations first, and runs the full suite after every merge.

Safe cleanup

Removes worktrees and merged branches with the non-forcing commands, and asks before discarding any work.

Usage Examples

Input

Add pagination to the items API and an empty state to the list UI. Run agents in parallel.

Output

A task table with slugs, allowed files and dependencies for approval, then worktrees, briefs, a STATUS.md board, reviewed merges in order and a final report.

Input

Use worktrees for these three changes, but I can only run one session.

Output

The single-session fallback: same worktrees, briefs, board, review and merge steps, with the tasks done one at a time in dependency order.

SKILL.md

---
name: parallel-agents
description: Lets a lead agent split one coding task into independent pieces and run several coding-agent sessions on them in parallel, each in its own git worktree and branch, with a plain STATUS.md board, branch review, ordered merges and cleanup. Use when a task has two or more parts that touch different files and the user wants them done side by side (or asks to "fan out", "run agents in parallel", "use worktrees"); falls back to doing the parts one by one when only one session is available.
---

# Parallel Agents

Run several coding-agent workers on one repository at the same time without them
overwriting each other. The lead agent (the one reading this) plans, briefs,
tracks, reviews and merges. Workers only build. No extra app is needed: git
worktrees keep the work apart, and a markdown file keeps the status.

## Prerequisites

- `git` 2.20 or newer (`git worktree` support). Check with `git --version`.
- A clean working tree on the base branch: `git status` shows nothing to commit.
  If it does not, stop and ask the user whether to commit, stash, or abort.
- A way to start more agent sessions (a second terminal, tmux, or the agent
  product's own "new session" feature). If there is none, use the
  single-session fallback in Step 5.
- A known test command (for example `npm test`, `pytest`, `go test ./...`).
  If the project has none, ask the user what "passing" means before Step 3.
- A green baseline: run the test command on the base branch before splitting
  any work. If it fails, stop and tell the user; do not start workers on a
  broken base, or later failures cannot be traced to a branch.
- Git identity: `git config user.name` and `git config user.email` both print a
  value. If either is empty, tell the user and ask them to set it before any
  commit is made; do not invent one.

## Roles

| Role | Does | Never does |
| --- | --- | --- |
| Lead | Decomposes, creates worktrees, writes briefs, updates STATUS.md, reviews, merges, cle

Frequently Asked Questions

FAQ

How is this different from herdr?
Herdr is a desktop app for terminals and coding agents that shows several agents side by side with their status. Parallel Agents is an app-free skill: it teaches a lead agent to decompose a task, isolate workers in git worktrees, brief them, track them in STATUS.md, review, merge and clean up.
Is this the official herdr app?
No. It is not herdr, contains no herdr code or binaries, and is not affiliated with herdrdev. The official herdr-app repository is https://github.com/herdrdev/herdr-app.
What do I need?
Git 2.20 or newer, a clean base branch with a known, passing test command, and a way to start more agent sessions. tmux is optional; with only one session the skill runs tasks one by one.
Will it force-push or delete my work?
No. It never force-pushes, pushes only when you ask, and refuses to delete worktrees or branches with unmerged or uncommitted work without your agreement.
What does a download cost?
Each skill download costs 1 credit. New accounts start with 3 free credits.

Discussion

Discussion

0 comments
U

Trigger Phrases

Use these phrases to activate this skill in your AI coding assistant:

run agents in parallelfan out this taskuse worktrees for thissplit this across several agentsparallelize this changeherdr-style agent workflow