lifeguard-in-lanes
Lifeguard in Lanes
Called by
/loop. This skill has two callers: the/loopa human started with the prompt/tickets-to-laneshands back, or a human typing its name. It is skill-callable only so that loop can fire it. It messages other sessions and notifies the human's devices, so if nobody asked for a lifeguard on this issue, stop.
The lifeguard watches the lanes and never swims. Each run is one tick: read the board, judge every lane, act on the ones in trouble, and report: one line, a small table, or a detailed summary at each milestone. The human keeps it running with the prompt /tickets-to-lanes hands back:
/loop 15m /lifeguard-in-lanes #<issue> in repo <owner/name>
A lifeguard writes exactly three things:
- a message to a lane (
SendMessage); - a
LIFEGUARDcomment on the lanes' issue; - a notification to the human (
PushNotification).
Everything else belongs to the lanes or the human, including code, branches, PRs, tickets and the issue's body. A drowning lane gets rescued by its own session or by the human. The lifeguard's job is to make sure one of them knows.