Shipyard

Shipyard

A Claude Code plugin for structured project execution. Plan work in phases, build with parallel agents and TDD, review with security audits and quality gates, and ship with confidence.

Prerequisites

- Claude Code CLI installed and authenticated
- jq (used by session hooks for state injection)

Installation

From GitHub (recommended)

From a local clone

Verify

Using Shipyard with Codex

Shipyard also installs under Codex CLI (0.124.0+) on a
best-effort, not-parity basis — all skills run natively; the multi-agent workflows
degrade to inline sequential personas.

What you get and what degrades is documented in full in
docs/using-shipyard-with-codex.md. In short: skills
auto-activate identically; orchestration (build/audit/ship/review) runs sequentially in one
context (no parallelism, no fresh-context review isolation); and state loads on demand
instead of via a session hook.

Quick Start

Once installed, navigate to any project directory and run:

For the full command reference and common workflows, see docs/QUICKSTART.md.

spec-kit Integration

Shipyard integrates with spec-kit (GitHub's Spec-Driven Development toolkit), letting you use spec-kit's structured specification workflow as a higher-quality alternative to /shipyard:brainstorm.

How It Works

spec-kit produces a rich set of artifacts in specs/[###-feature]/:

The /shipyard:plan command automatically detects these staged artifacts:
- Skips the researcher agent when RESEARCH.md already exists
- Seeds the architect with SPECKIT-TASKS.md to generate accurate wave/plan decomposition with less hallucination

Workflow

/shipyard:import-spec also handles:
- Auto-discovery: if no argument is given, lists available specs/ directories
- [NEEDS CLARIFICATION] markers: surfaced as an Open Questions section in…