Parallel execution of multiple issues. Triggers: "run a wave", "parallel implementation", "batch execute", "implement in parallel".
View on GitHubboshu2/agentops
core-kit
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/boshu2/agentops/blob/main/plugins/core-kit/skills/implement-wave/SKILL.md -a claude-code --skill implement-waveInstallation paths:
.claude/skills/implement-wave/# Implement Wave Skill
Execute a wave of independent issues in parallel using sub-agents.
## Overview
Orchestrate parallel implementation with conflict detection, batch closing, and single-commit consolidation.
**When to Use**: >=2 ready issues, parallelism benefit.
**When NOT to Use**: Single issue (use `/implement`), complex dependencies.
---
## Workflow
```
0. Wave Identification -> bd ready, filter up to 8
1. Conflict Detection -> File overlap, greedy partition
2. Launch Sub-Agents -> Parallel Task() calls
3. Monitor Results -> Poll TaskOutput
4. Batch Close + Commit -> Single wave commit
5. Handle Failures -> Leave failed in_progress
```
---
## Phase 0: Wave Identification
```bash
bd ready
```
**Selection**: Up to 8 issues, priority ordered (P0 > P1 > P2 > P3).
---
## Phase 1: Conflict Detection
**CRITICAL**: Detect file overlaps before parallel execution.
**Algorithm**: For each issue pair, check if predicted file changes overlap:
1. Read issue descriptions to identify target files
2. Build overlap matrix: `overlap[i][j] = files_touched(i) ∩ files_touched(j)`
3. If overlap, place in sequential groups (greedy partition)
If overlaps found, partition into sequential groups.
---
## Phase 2: Launch Sub-Agents
```markdown
Task(
subagent_type="general-purpose",
model="sonnet",
prompt="Implement issue <id>. Add 'READY_FOR_BATCH_CLOSE' when done.
Do NOT commit - orchestrator handles commits.",
run_in_background=True
)
```
**Model**: Use `sonnet` for implementation (cost-effective for code generation).
**Constraints**: Maximum 8 concurrent sub-agents.
---
## Phase 3-4: Collect & Close
Poll for completion, check signals:
- `READY_FOR_BATCH_CLOSE` → Success
- `BLOCKER:` → Failure
```bash
bd close <id1> <id2> ... # Only successful issues
git add -A && git commit -m "feat(wave): complete N issues"
bd sync && git push
```
---
## Phase 5: Handle Failures
- Leave failed issues `in_progress`
- Do NOT auto