---
name: dispatching-parallel-agents
description: Safely parallelize independent lanes with isolation checks, explicit ownership, and single-agent integration
permalink: opencode-config/skills/dispatching-parallel-agents/skill
---

# Dispatching Parallel Agents

Use this skill before parallel fan-out.

## Isolation Test (Required)

Parallel lanes are allowed only when lanes do not share:

- files under active mutation
- APIs or schemas being changed
- verification steps that must run in sequence

If any of these overlap, run sequentially.

## Workflow

1. Define lanes with explicit scope, inputs, and outputs.
2. Assign a single integrator (usually builder) for merge and final validation.
3. Require each lane to provide verification evidence, not just code output.
4. Integrate in dependency order.
5. Run final end-to-end verification after integration.

## Planner/Builder Expectations

- Planner: design parallel lanes only when isolation is demonstrable.
- Builder: load this skill before fan-out and enforce lane boundaries strictly.

## Red Flags

- Two lanes editing the same contract.
- Shared test fixtures causing non-deterministic outcomes.
- Missing integrator ownership.