Shipyard plugin
A Claude Code plugin for phased project execution: planning, parallel agents with TDD, security and quality gates, then shipping.
- 67 ★ on the repository
- Last commit
Broad access
Why this level
- Parallel agents write code and run commands in the project, and the plugin installs session hooks.
- Project state is written to `.shipyard/` next to the code.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/shipyardDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Parallel agents write code and run commands in the project, and the plugin installs session hooks.
- Project state is written to `.shipyard/` next to the code.
This is third-party code. Review the repository files before installing.
What it does
Shipyard takes a project from idea to release with `/shipyard:init`, `/shipyard:brainstorm`, `/shipyard:plan N`, `/shipyard:build` and `/shipyard:ship`. Work is split into phases with state in a `.shipyard/` directory (PROJECT.md, ROADMAP.md, phase files). Builds run on parallel agents with tests first, then pass a security audit and quality gates before shipping. The plugin ships ten agents: architect, auditor, builder, debugger, documenter, mapper, researcher, reviewer, simplifier and verifier. A spec can come from spec-kit through `/shipyard:import-spec` or from your own document through `/shipyard:import-spec-file`, which skips the researcher and seeds the architect with a ready task list. For Codex the plugin installs on a best-effort basis: skills work while orchestration runs sequentially in one context.
Who it is for. Developers running a project in Claude Code by phases who want security and quality checks at every step.
Good fit when
- A project needs phases with planning, building and shipping in one flow.
- A spec already exists in spec-kit and must become a plan and tasks.
- Before release a security audit and quality review by separate agents are required.
- Wave-based parallel building speeds up a large feature.
Not a fit when
- You need a one-file tweak; the phased process is heavy.
- You work outside Claude Code; in Codex the plugin gives no parallelism.
- A `.shipyard/` state directory in the repository is unwelcome.
Example request
Run /shipyard:init, then break the feature into phases and show the plan for phase one.Limitations
Claude Code with authentication and `jq` are required; session hooks use `jq` to inject state. In Codex (0.124.0 and newer) the plugin works on a best-effort basis without parity: orchestration runs sequentially in one context, with no parallelism and no fresh-context review isolation. Parallel agents spend many tokens, and project state lives in `.shipyard/` next to the code.
How to disable. Remove the plugin with `claude plugin uninstall shipyard` and delete `.shipyard/` in projects where it was created.
FAQ
How do I install Shipyard?
With `claude plugin marketplace add lgbarn/shipyard` and `claude plugin install shipyard@shipyard`. Verify with `claude /shipyard:status`.
Does Shipyard work in Codex?
Yes, on a best-effort basis: `codex plugin marketplace add lgbarn/shipyard`, then enable the plugin. Skills work while agent flows run sequentially.
How do I use spec-kit?
Build the spec with `/speckit.*`, then run `/shipyard:import-spec specs/001-my-feature`. The researcher is skipped and the architect gets the task list.
What about a handwritten spec?
`/shipyard:import-spec-file` reads the document, maps sections to PROJECT.md and asks short questions about gaps.
Which agents are included?
Architect, auditor, builder, debugger, documenter, mapper, researcher, reviewer, simplifier and verifier.
Discussion
No questions or reviews yet.
Related
PluginsA plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
A gitmark plugin for Claude Code: a project knowledge base from markdown and git with FTS5 search, a link graph and dev-flow
A plugin that turns Claude Code into a 16 agent team: documentation first planning, TDD and 9 pre-merge quality gates.
The AI-SDLC plugin for Claude Code carries a task from spec to PR: a readiness gate, a developer agent and several reviewers.
Six linked skills take a project from a raw idea to a validated build plan and a first draft in Claude Code and Codex.
A universal workflow plugin for Claude Code: 7 agents, 26 commands, 14 skills and 14 hooks for any project
README in short
The plugin defines a command chain from idea to release with mandatory planning, building and review steps. A quickstart, a command reference and a Codex installation guide are included.