1.2 KiB
1.2 KiB
name, description, permalink
| name | description | permalink |
|---|---|---|
| dispatching-parallel-agents | Safely parallelize independent lanes with isolation checks, explicit ownership, and single-agent integration | 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
- Define lanes with explicit scope, inputs, and outputs.
- Assign a single integrator (usually builder) for merge and final validation.
- Require each lane to provide verification evidence, not just code output.
- Integrate in dependency order.
- 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.