Claude Shipyard

Shipyard

A Claude Code plugin marketplace for building and running **fleets of autonomous coding agents** — planning work they can finish unsupervised, dispatching them, and landing the result.

Install

/plugin marketplace add felipearomani/claude-shipyard
/plugin install fleet@shipyard

Plugins

Plugin	What it does
`fleet`	/fleet:planner turns an idea, spec or messy board into a dispatchable work package. /fleet:coordinator runs the fleet from the pre-dispatch gate to a clean shutdown. Ships /fleet:open-pr, /fleet:review-pr and three adversarial reviewer agents.

Why this exists

A single agent session can implement a task. It cannot hold an epic. The moment you run several agents in parallel, the work stops being about code and starts being about four things that have nothing to do with code:

• Ambiguity becomes a decision you never see. A person asks when a requirement is unclear; an agent picks, and picks differently from the agent next to it. You find out at merge.
• Two agents in one file is a rebase you pay for twice. Boundaries have to be declared before dispatch, in globs, with an owner for every shared file.
• Every stall costs a round trip. A missing credential found at 3am costs the night. The work of a coordinator is mostly work done before launching.
• Reviews generate work that generates reviews. Without somewhere for out-of-scope findings to land, the round never converges. One epic here gained 20 tasks in a night.

The two skills in `fleet` are the accumulated answer to those, written as procedure rather than advice — including the parts that are counter-intuitive, like the fact that a coordinator **cannot** pass along the human's authorization to an agent, and that an agent which refuses the relay is correct to refuse.

Much of the material carries the real case that produced it. That is deliberate: a rule without its case degrades into a slogan, an