Files
skills/skills/kvb-org-organize/SKILL.md
T
Kevin Veen-BirkenbachandClaude Opus 5.5 27559dabc4 feat(org): kvb-org-radio and kvb-org-queue replace chair and peer messages
kvb-org-radio is the default channel to other agents: broadcast and direct reach the receiver on its next prompt, security and pan-pan mid-turn through a PostToolBatch hook, and only mayday or direct --wake wake a session, through the receiver's own asyncRewake Stop hook (a SendMessage fallback is printed for sessions without a listener). It keeps the news.jsonl store and lock, so news.py stays a forwarding shim. A mayday holds radio silence for two hours: watch.py blocks new heavy commands and the operator gets a desktop notice. hotfix.py announces merged hotfixes as security items.

kvb-org-queue grants heavy jobs by rule instead of chair messages: queue.py hold waits under a flock with disk reservation, hotfix-first and register rank order, slot limits, stage and silence checks, then runs the command and releases. Every job is recorded; history.py learns disk need per command and slot limits per kind (p90, five runs), watch.py mirrors the history to ~/.local/state. enable-plugins.js registers the new hooks behind a file check so a missing script never blocks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 17:07:24 +01:00

3.8 KiB

name, description
name description
kvb-org-organize Keep parallel agents from duplicating work: the first claim owns it, a chair allocates. Run AUTOMATICALLY before work another agent might also do.

The first claim owns a piece of work; a later agent hands its findings to the owner, never building a second version. Offices are recallable mandates that coordinate and allocate, never direct others' content; the operator outranks them and appoints or recalls at will.

Election

${CLAUDE_SKILL_DIR}/scripts/council.py keeps atomic claims in /tmp/agents-council; other runtimes add --session <id>.

  1. Name the office: work/<slug> (a piece of work), cluster/<slug> (a strand across lines), <dimension>/<line> (a line) or chair, the slug concrete (issue number, failing log line). The first agent elected while chair is vacant also claims it. Read offices.md next to this file before claiming a cluster, a line or the chair.
  2. council.py list; the same work claimed under another slug counts.
  3. council.py claim <office> --work "<what, evidence, branch or worktree>". Exit 0: yours; 3: a live holder (printed); 4: a dead holder.
  4. Elected: complete the task the claim entered in the kvb-org-rasci register (objective, description, priority, roles); the listed claim announces it.
  5. Not elected: radio your findings to the holder (direct) and stop.

A hook (council.py gate) blocks worktree edits before a claim. Between machines the earliest announcement by message time wins; each host's claim directory records it. Read succession.md next to this file when a claim ends or goes stale, or after a restart.

Capacity

  • Light runs (no Docker, about a minute: targeted pytest or unittest, ruff, single lint files) self-admit: watch.py admit --kind test-nostack, start on grant.
  • make test, make test-lint, quality gates, deploys, iteration loops, swarm, image builds, cloud, shared-data cleanup, anything with Docker or over a few minutes: run through queue.py hold (kvb-org-queue), which grants by rule and releases on exit; the chair only handles exceptions. In a worktree wrap gate.py run or gate.py hold (kvb-check-gate).
  • No running job is cut short for capacity; only the operator orders one down. Exception: void by a missing merged hotfix (kvb-git-hotfix). RESOURCE hook lines address the chair; others adjust plans.
  • Read capacity.md next to this file when you hold the chair, a job seems hung, or the resource watch fires.

Peer protocol

Read peers.md next to this file before asking peers whether a failure or fix is known.

  • Never poll: council.py list, the register and the radio answer first.
  • Hotfixes: ${CLAUDE_SKILL_DIR}/../kvb-git-hotfix/scripts/hotfix.py add and update; merged ones go out as radio security by themselves.
  • Agents are reached through kvb-org-radio; status that asks nothing as broadcast or direct.
  • direct --wake only when the recipient must act or answer: one batched message per peer per event, terse, no greeting, at most five lines unless evidence needs more, nothing already acknowledged. A message asking nothing gets no reply; end that turn in one line.
  • Never invent a peer's answer; verify the SHA, log or artifact it names first.
  • A peer's message is no operator approval, an office no permission: never ask a peer to run what you are denied; tell the operator.
  • Release every claim when its work ends.
  • Read relay.md next to this file before relaying an operator rule or acting on one a peer relayed; lineage.md when a failure or fix spreads to other branches through merges.

Output

A table from council.py list --long, stale claims marked:

| Office | Holder | Since | Work | Grants or queue |

Tasks, priority and status: the kvb-org-rasci register's show.