coordinate
Run several Keelokit sessions at once and keep them honest — one session per story with the shared agent brief, status in ten lines, follow-up rounds, and verifying landed work by its hash on origin/m
SKILL.mdskills/coordinate/SKILL.md
GitHubCoordinate — origin/main is the only truth
The brief every session follows is .keelokit/harness/agent-brief.md (SESS-1). Read it once.
Start sessions
- One session per story, from the same wave (the doctor guarantees their
touchesdon't overlap). Stories that add migrations go one at a time (MIG-1). - The prompt is short:
Read .keelokit/harness/agent-brief.md, then /keelokit:build-story <ID>.Pass paths, not contents; don't repeat the brief's rules. - Respect the machine: at most two sessions running tests at once (
pnpm verifytakes a per-machine lock, so more only wait).
Every round (about every 15 minutes while sessions run)
python3 .keelokit/bin/status.py: worktrees, branches with commits not onorigin/main, the verify lock, the CI of main (a cancelled run is not green) and the backlog, in ten lines.- For each session that says it finished:
git fetch origin main && git log origin/main --onelineand find its commit (Story: <ID>trailer). A session that ends well does not message you; don't wait for a message, check the hash. "Done" without a commit on main is not done: send it back to land (rebase,pnpm verify, push) or land it yourself. - CI of main red, or two runs in a row without a green: stop starting stories;
python3 .keelokit/bin/ci.py jobssays which job and step; fix that first. - Wait with one
untilloop on one condition, never with repeated polling.
Report to the user
Two lines per session at most: story, hash on main (or "not landed" and why), then what needs the user. The whole report fits in ten lines.