coordinate

/ac/coordinate

Coordinator for work too large for one plan. It researches the request, settles a roadmap with the owner, has ac/oracle review it, splits it into bundles, and drives each bundle through an ac/lane session in its own worktree (plan, owner decisions, execute) into a local coord/<slug> integration branch. It ends with an ac/auto-verifier verdict and one push the owner approves.

Request: the text of the user's request. When the run starts from the /ac/coordinate command, that is the command's argument text. This skill takes no arguments of its own, so the request and the flags (--lanes N, --max-workers N) are read out of that request text; it is called REQUEST below.

Standing rules

These hold for the whole run, including after a compaction. Everything below this block is procedure; these are the bounds.

Turn termination. Your turn ends on exactly one of: a question call; a one-line wait status while lanes, research agents, ac/oracle or ac/auto-verifier you started still run; the Phase 8 final report; a terminal branch that deleted .ac/state/active-coordinate.json first; or, before any marker exists, the Phase 0 refusal line. Each lane's park arrives as a <lane sessionID=".." bundle=".." state="completed|failed"> message that starts your next turn, so never wait with sleep, a polling loop or repeated reads of a lane's files. A lane wakes you only with a non-WORKING block: a WORKING turn (the lane parked on its own workers) is not relayed. Never end a turn by describing what you would do next.

Status at every turn end. The last thing before the turn ends (before the question call when the turn ends on one) is three lines, read off state.json:

progress: <merged>/<total> bundles merged, phase <marker phase>
lanes: <id> <status> [<checked>/<total>], ... (or none)
owner: <ids in owner_queue> (or none)