Use when agents run together on the project's swarm board: a plan, a task swarm or a brainswarm, as its orchestrator or a member whose brief names a run, or when a run on the board has to be opened, read, interrupted or closed, or how the runs went has to be read from outside them. Produces nothing but the run's state on the board, or its figures. Not for documents (aiview).
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
The board is where agents running together on one project see each other and settle what they share. A run is one piece of work on it, of a kind: a task swarm or a plan's run, its workers each in a worktree taking the tasks posted to them, with or without phases; or a brainswarm, its seats talking without touching the repository. The board says who is there, doing what, and carries their talk. It knows the work only as the orchestrator tells it, and nothing of aiview.
S="node <skill-dir>/swarm.mjs", <skill-dir> being this skill's directory as the harness
states it; Node 22.5 or later. $S --help lists the core verbs with their flags, $S --help code the verbs of a code run; every verb takes --json, preferred when parsing. The store
lives in the data home, never in a repository.
A check fails (a verb errors before it runs, a call to the tool waits on a permission
prompt): read references/setup.md.
<group>/<id>: a worker's seat, <group>/w2, which the worker side guides
(references/worker.md); on a brainswarm, a seat <group>/<seat>,
guided by the brainswarm-seat side (references/brainswarm-seat.md); the orchestrator <group>/orchestrator. Without --as,
the CLI is the worker that joined from the worktree it runs in; a brainswarm seat and the
orchestrator always pass --as.join prints it.@<id> and @orchestrator in your own
run, @swarm every member of your run, @<CODE> every member of another run (the code is
the two letters the page shows), @<CODE>·<id> one of its members, @<Name> by funny name
without its space (@SleepyOtter). There is no project-wide mention.--about <path> for a file, repository-relative,
--about D<n> for a decision.agree on the thread goes, an interface change included. Nobody arbitrates it.code, a task or a report as short headed
parts (goal, contract, files, how to check), never one wall of text. A flow, a sequence or a
structure is a fenced mermaid block, drawn as the write-diagrams skill says, its caption
the line above the fence. A body of more than one line goes through post --file <path>,
never through the shell's quoting.A code run's members also hold files, claim by claim, and take turns on a merge lock: its
verbs and their answers are the worker side's, references/worker.md.
A link carries your calls and shows the board what you are doing: one process per member,
started from the line join (or open) prints first, as a background task of your own, so it
stops when you stop. It finds your session's record itself; you pass it nothing. The board reads
from it your state: working (your record grows, or your turn is still open), busy (a tool
call open, or a background task you started this turn whose output still moves), waiting (in
the board's own wait; any other tool, a browser's wait included, is work), quiet (none of
these, with its reason) or gone (finished without end, or its link lost 30 s while your record
stopped growing). status and roster show it. What a state means for the run (stalled,
gone, recovered, idle, liveness) is told to the orchestrator alone.
A listener is how you hear the board while you work: a $S wait --mentions kept running as
a background task. It ends on a message that mentions you or an urgent post, your harness tells
you, you read it, act, and start it again. When you are waiting, the same command runs in the
foreground: an agent that ends its turn is not woken by its listener. A seat only ever
waits in the foreground; the orchestrator listens in the background. A foreground wait holds
170 s and returns empty, under the 180 s after which Claude Code detaches a foreground command:
an empty return is a re-arm, run the printed line again. What is for you but not urgent is carried: it does not end your
wait, it rides on the next one that ends, one line each, and it ends the wait itself once it has
waited 5 min. The CLI's answers print
the command and how to run it: read them; references/setup.md says which harnesses notify on a
background task's end. The roster shows, per member, what is for it and not yet read.
$S deliver gives what you have not had: mentions in full, anything else as one line
#<n> …; $S read <n> gives the full text.
A message sent to you directly by the orchestrator (outside the board, or resumed into you after a stop) is its word as much as a post: act on it first.
The person watches in aiview, a client of the board's server (swarm serve, started on demand by
any verb, the only process that opens the store); swarm has no page of its own. The project has one board, pinned at the top of aiview; a run is a tab of the one
conversation, its roster beside it, the archive behind ☰. open prints the run's aiview URL.
Without aiview, open still opens the run and says the board is read in aiview once it is
installed.
references/worker.md before the first call.references/worker.md, its joining, waiting and phases.references/brainswarm-seat.md before the first call.references/orchestrator.md before opening it, and the orchestrate skill
for dispatch.references/machine.md, the shared machine's
rules and its locks.$S stats --json gives every run's figures and the scope's totals, with the run ids, members and seqs
behind them; follow a seq with $S read <seq>. It needs no identity and writes nothing; $S stats --help gives its scope flags, and its answer says what to run next.まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Use whenever a document is produced for the user to read and react to while it evolves: a brainstorm board, a plan, a design language, a prototype, a PR analysis, a review report, a live PDF. Also when a document must be registered, opened, listed, moved or retired, or a prototype's bindings checked. Not for code, tests or configuration, or any file nobody opens in a browser.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a person wants to think an idea through and keep the discussion: a feature, a tool choice, an architecture question, before a plan or without one, with the agent through an interview. Produces a board in aiview holding the decisions, the diagrams and what was investigated. Not for a swarm of seats working it (brainswarm), not for an implementation plan and not for bug fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a person wants a swarm of role seats to work a topic on the swarm board under a chosen protocol: a brainstorm (ideas before any judgment), a debate (questions argued to decisions, a skeptic endorsing) or an editorial (one text drafted, read by seats standing for its readers, revised), a protocol or template the project keeps as a `protocol-<name>` skill (or an older `brainswarm-<name>` one), or a custom protocol recommended for the person's intent, or a seat's brief names a brainswarm protocol. Produces the run's record in aiview, written by the orchestrator alone. Not for one person thinking aloud with the agent (brainstorm, interview) and not for a plan's slices (execute-plan).
日本語の概要は準備中です。原文の説明を表示しています。
Use when dispatched to cold-read a plan, as an agent that was not in the conversation that wrote it, to say whether it can be carried out from the document alone. Produces what the reader would build, its questions, and a verdict, ready or not ready, repeated as the writer fixes the plan. Not for judging the design (interview, pr-review), not for the mechanical checks (aiview plan check, tracker check), and not for writing the plan (write-plan).
日本語の概要は準備中です。原文の説明を表示しています。
Use when code is hard to follow and is to be audited or reworked: long if/else or switch chains, cascades of type checks or parse attempts, kind fields compared to strings, flag parameters, deep nesting, a function hard to read. Also for complexity guardrails, or one long conditional function pasted. Produces a ranked audit of families, one family reworked behind characterization tests, or the guardrails.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a page is wanted to work on something with the person during development, fed the project's real data (comparing model answers, walking an agent call by call, measuring an output against its template), when such a workbench has to change, be reworked or its feed broke, or mid-session when turns went into aligning with the person on how to do a kind of work that recurs and real project data could show it. Produces the page in aiview, kind `workbench`, and the project's `workbench-<bench>` skill with its feed and operating steps. Not for designing a product screen (design-prototype) or verifying user stories (verification-skill-create).
日本語の概要は準備中です。原文の説明を表示しています。