swarmstorm 플러그인

Defines the architecture on the swarm board before any code is built: reads the code it lands in and writes the architecture (deep modules, entries as signatures, flows as pseudo-code, decisions) in the one design format, posts it, and settles it with the orchestrator until accepted. Use for the arc

Takes one seat on the swarm board, under a brainswarm protocol (brainstorm, debate, editorial). Use for every seat a brainswarm dispatches, its brief naming the run, the seat and the board.

Orchestrates one swarm run handed to it by the session the person talks to: opens the run on the board, dispatches its members, posts their tasks, watches, judges findings and runs the loop, from a settled charter, escalating only to the session that sent it. Use for every handoff an orchestrating s

Prototypes the screens of a piece of work on the swarm board before any of it is architected or built: reads the ideas the other members post to it, builds the prototype in the project's own design language through the design-prototype skill, posts its link, and revises it with the orchestrator and

Takes tasks from the swarm board, in any run that builds code (a task swarm, a plan run, a build-verify run): joins, the board making its worktree, does each task the orchestrator posts to it, shaping the code around it and naming it well, merges what it changed, reports, and hands back, the orchest

Judges, alone, the product quality of what was delivered (done as specified, usable, finished) over the scope its brief or phase message gives, from a project's verify-<app>-<focus> skill or from the steps it is given, and returns the verdict and findings table. Use for every verification an orchest

Use when an agent orchestrates other agents on a piece of work, of any kind (a plan, a task swarm, a brainswarm): proposing a run tuned to the work, built on the closest protocol (build-verify, idea-to-outcome, brainstorm, debate, editorial, a project's own), settling it with the person, dispatching each member with its brief and role, watching them, judging their findings and steering a drift. Not for the duties one kind adds (orchestrate-plan for a plan, swarm for a task swarm, brainswarm for a seat swarm), and not for the board they talk on (swarm-board).

Use when a person asks to swarm, delegate or parallelize work without a plan ('swarm this', 'run a swarm on…', 'get a few agents on it'), or when a task in front of you splits into independent parts or is long enough to hand off: then propose a swarm in one line, workers and why, and open it only on a yes. Runs a task swarm on the board: this session orchestrates, N swarm-worker agents take the tasks posted to them, report, and take the next, for as long as the person keeps giving work, on call or under a protocol (build-verify: builders, then verifiers walking the running product, looped until it holds). Produces the run on the board and the workers' results and merges. Not for work an approved plan covers (execute-plan), a discussion of seats (brainswarm), or a task small enough to do yourself.