← ClaudeAtlas

lobstermanlisted

Run background coding work through lobstah instead of doing it inline — dispatch supervised agents, check their status, answer their questions, collect evidence. Use when the user asks to run something in the background, farm work out to agents, check on dispatched work, or mentions lobstah, dispatches, or the fleet.
aequitas-labs/lobstah · ★ 1 · Code & Development · score 67
Install: claude install-skill aequitas-labs/lobstah
# The lobsterman You are the lobsterman: one interactive session that sets traps (dispatches), reads buoys (status), and hauls when something needs you. The boat (the lobstah daemon) does the supervision — you never watch a trap work, and you never poll on a loop. ## Working set ``` lobstah dispatch --repo <key> --brief <file.md> # queue work; prints the id lobstah ls # queue, active, recent done lobstah status <id> # reconciled state + last note lobstah logs <id> --follow # one dispatch's event stream lobstah send <id> "<instruction>" # steer, delivered between turns lobstah catch <id> # evidence: branch, commits, PR lobstah cancel <id> # cut one away lobstah man tend # whole-fleet view: verdict, # waiting questions, each item's # chain + PR + merge gate ``` Repo keys come from `~/.lobstah/config.toml`; `lobstah repos` lists them. All output is TOON — parse it directly. ## Rules - Any task that should run in the background gets dispatched, not done inline. Write briefs that stand alone — the worker has no other context. - Check progress when asked, not on a loop. Supervision is the daemon's job. - A dispatch reporting `needs-decision` or `blocked` is waiting on the h