# Agent Squad

> Plans parallel agents or worktrees with isolated ownership, validation lanes, and merge rules. Use only for safely separable work.

- Skill: `mesteriis/agent-squad` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mesteriis/agent-squad`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mesteriis/agent-squad/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: Mesteriis (https://skillmd.com/u/mesteriis)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/mesteriis/agent-squad

---


# Agent Squad

Use this skill when parallel agent work can reduce risk or time without
creating file conflicts.

This skill is inspired by multi-agent terminal orchestrators. It is not a TUI
installer. It defines the planning, isolation, review, and merge contract for
Codex-compatible parallel work.

## When To Use

Use for:

- large refactors with separable modules;
- implementation plus tests plus review lanes;
- independent security, performance, UI, and docs reviews;
- migration slices that can be validated independently;
- comparing alternative approaches before selecting one.

Avoid for:

- tiny changes;
- tasks where all lanes must edit the same file;
- unclear goals;
- work that needs secrets or production access in multiple contexts.

## Lane Design

Each lane needs:

- goal;
- allowed files or directories;
- forbidden files or directories;
- validation command;
- expected artifact;
- merge owner.

Common lanes:

- implementation;
- tests/TDD;
- security review;
- architecture review;
- docs/update notes;
- regression validation.

## Isolation Rules

- Prefer separate git worktrees or read-only subagents for parallel work.
- Do not let two write lanes own the same files.
- Keep secret-bearing files out of all lanes unless explicitly scoped.
- Merge through one owner after reviewing diffs.
- If lanes conflict, stop and re-plan before editing more.

## Merge Contract

Before finalizing:

1. Collect lane results.
2. Deduplicate findings.
3. Verify changed files against allowed scopes.
4. Run integration validation from the main worktree.
5. Summarize what was accepted, rejected, or deferred.

## Output

Report:

- lanes created;
- isolation method;
- per-lane result;
- merge decision;
- final validation.