# Orchestrate Parallel Coding Agents

Large features are hard to split across autonomous coding agents. This skill provides a worktree-based workflow for issue design, wave planning, monitoring, merging, and cleanup.

## Install

```bash
npx skillstore add 4eyedengineer/orchestrating-parallel-agents
```

## Metadata

- Status: approved
- Slug: 4eyedengineer-orchestrating-parallel-agents
- Skillstore revision: r1
- Version status: missing
- Tree hash: c6cf1ba0500dc8b162b663bf57ad13b5b42b24bc2f8992a33bea71cb259e3582
- Author: 4eyedengineer
- GitHub username: 4eyedengineer
- License: MIT
- Repository: https://github.com/4eyedengineer/4eyed\_development/tree/main/.claude/skills/orchestrating-parallel-agents
- Ref: e9e4712298ed071d92417a41714be123eb8364fa
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/4eyedengineer-orchestrating-parallel-agents
- Manifest: https://skillstore.pages.dev/api/skills/4eyedengineer-orchestrating-parallel-agents/manifest

## Capabilities

- Breaks large implementation work into isolated GitHub issues for separate agents.
- Organizes issue batches into waves based on file overlap and dependencies.
- Shows how to configure Claude permissions for non-interactive worktree commands.
- Provides shell examples for launching, monitoring, merging, and cleaning worktrees.
- Gives conflict handling guidance for sequential PR merges and rebases.

## Use Cases

- Plan a Feature Wave: Split a feature into independent GitHub issues and run one agent per issue.
- Batch Small Fixes: Group small changes into waves while keeping same-file edits sequential.
- Coordinate Integration Work: Schedule dependent waves after agents finish implementation work and initial PRs land.

## Prompt Templates

### Plan a Safe First Wave

```
Use orchestrating-parallel-agents to split this feature into three independent issues. Identify files, dependencies, and review steps before spawning agents.
```

### Draft Agent-Ready Issues

```
Draft issue bodies for a parallel agent wave. Include problem, solution, files to modify, implementation notes, and acceptance criteria.
```

### Run and Monitor a Wave

```
Prepare the commands and checklist for launching agents for issues 101, 102, and 103. Include monitoring, logs, and failure handling.
```

### Resolve Dependent Waves

```
Design a multi-wave rollout for issues that share files. Show merge order, rebase checkpoints, and cleanup after PRs land.
```

## Limitations

- It does not create issues, branches, or worktrees by itself.
- It assumes Claude CLI, Git, and GitHub CLI are installed and authenticated.
- It requires manual review of diffs, PRs, and merge conflicts.
- It can increase repository risk if broad git permissions are approved.

## Best Practices

- Keep each issue scoped to one to three files with clear acceptance criteria.
- Review every diff and PR before merging or pushing.
- Run same-file changes sequentially or assign them to one agent.

## Anti Patterns

- Starting many agents against vague issues with no file guidance.
- Pre-approving broad git permissions on a shared repository.
- Merging parallel PRs without rebasing after earlier merges.

## Security Audit

- Audited at: 2026-07-04T16:53:19.907\+00:00
- Summary: The static Ruby backtick findings are Markdown fences, inline code, or documented command examples rather than executable Ruby code. No prompt injection was found in SKILL.md. The main security concern is explicit guidance to pre-approve git add, commit, and push for non-interactive agents.

## Stats

- Views: 198
- Downloads: 17
- Favorites: 0
- Popularity score: 0