Files

alex wiesner c02e386846 docs: standardize verification handoffs and lane claims

2026-03-13 21:41:00 +00:00

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)

Before fan-out, verify that no two lanes share:

Claimed Files/Areas under active mutation (paths or named workflow surfaces from the lane-claim entries)
APIs or schemas being changed
Sequential verification dependencies (verification steps that must run in order across lanes)

Overlapping claimed files/areas or sequential verification dependencies forbid parallel fan-out. Run those lanes sequentially.

Builder creates lane-claim entries in the execution note before fan-out, recording for each lane: Owner, Status (→ active), Claimed Files/Areas, Depends On, and Exit Condition.
Run the isolation test above against the claimed files/areas and dependencies. Abort fan-out on any overlap.
Define lane scope, inputs, and outputs for each subagent.
Assign a single integrator (usually builder) for merge and final validation.
Each lane must return compact verification evidence in the shared shape (Goal, Mode, Command/Check, Result, Key Evidence, Artifacts, Residual Risk) — not just code output.
Integrate in dependency order; update lane statuses to released or done.
Run final end-to-end verification (full mode) after integration.

Planner: define intended lanes and claimed files/areas in the approved plan when parallelization is expected.
Builder: load this skill before fan-out, create or update lane-claim entries in the execution note, mark them active/released/done/blocked, and enforce lane boundaries strictly.
Claims are advisory markdown metadata, not hard runtime locks. Do not invent lockfiles or runtime enforcement.