Plan it.Build it.Ship it.

Shipper is a standalone CLI that orchestrates AI coding agents to plan and build features in any repository. Anyone on the team can ship confidently.

curl -fsSL https://raw.githubusercontent.com/shipper-is/shipper/main/install.sh | sh

Docs View on GitHub

Built for every role on the team

Shipper turns feature ideas into committed plans and working code — whether you write the code yourself or not.

Developers

Stay in flow. Plans are committed markdown in your repo; builds run phase-by-phase with your agent of choice — Claude Code, Cursor CLI, or opencode.

Vibe-coders

Structure without ceremony. Describe the feature, answer a few clarifying questions in the TUI, and watch Shipper build it phase by phase — then ship a reviewable PR.

Non-developers

Ship real changes. The plan/build/ship loop asks clarifying questions and handles the code — you focus on what to build, not how.

How to use Shipper

Install once, then invoke skills in your coding agent — Claude Code, Cursor, or opencode. Planning and building happen there. Run shipper when you want the setup console: configuration, installed skills, search, and MCP. Artifact directories default to .shipper/ and can be changed in .shipper/config.json.

Get started

Two terminal commands and you're ready to plan features in your agent.

1
Install Shipper
Run the install script once on your machine. Shipper ships as a single compiled binary — no Node.js required.
```
curl -fsSL https://raw.githubusercontent.com/shipper-is/shipper/main/install.sh | sh
```
2
Install skills in your repo
From your project directory, install the bundled agent skills. On first run this also detects your coding agent (Claude Code, Cursor CLI, or opencode).
```
cd your-repo && shipper skills
```

Plan, build, ship

The core loop for larger features. Paste each command into your coding agent as you move through the workflow.

Plan

shipper-plan

Explores your codebase, asks clarifying questions, and writes a phased markdown plan to the configured plans directory (default .shipper/plans/open/).

/shipper-plan add a user settings page

Open your coding agent in the repo.
Run the slash command with a short description of the feature.
Answer clarifying questions inline.
A phased plan lands in the configured plans directory (default .shipper/plans/open/) — commit it so the team stays aligned.

Build

shipper-loop

Orchestrates the full plan in one chat: a fresh subagent runs shipper-build for each phase until the plan moves to the configured done folder (default .shipper/plans/done/).

/shipper-loop on .shipper/plans/open/my-feature.md

Run the slash command with the path to an open plan file.
The orchestrator spins up a new subagent per phase (via shipper-build).
Progress updates as checkboxes and Completion Notes land in the plan.
When every phase is done, the plan moves to the configured done folder (default .shipper/plans/done/).

Ship

shipper-ship

Scaffolds a reviewable pull request from a completed plan — what changed, how to verify, and known risks.

/shipper-ship on .shipper/plans/done/my-feature.md

Run the slash command with the path to a completed plan in .shipper/plans/done/.
The agent writes a PR summary with verification steps and test evidence.
A pull request is created via gh — ready for review.

Also available

Single-phase builds, small spikes, and bug fixes have dedicated skills with the same agent-first workflow.

Single phase

shipper-build

Implement one phase of an open plan in a single agent session. Prefer shipper-loop when you want the whole plan done.

/shipper-build on .shipper/plans/open/my-feature.md Phase 2

Run the slash command with the plan path and optional phase number.
The agent implements that phase, checks off tasks, and writes Completion Notes.
Re-run for the next phase, or switch to shipper-loop to finish the rest.

Spike

shipper-spike

Small one-off features: plan and build in a single agent session.

/shipper-spike add a copy button to the hero

Describe a small change that fits in one session.
The agent gathers context, writes a lightweight spike plan, and implements it.
The spike file moves to the configured spikes directory (default .shipper/spikes/done/) when finished.

Bug

shipper-bug

Evidence-first bug workflow: reproduce, diagnose, fix, and prove it in the configured bugs directory (default .shipper/bugs/).

/shipper-bug fix the login redirect loop

Run the slash command with a short description of the bug.
The agent reproduces it before diagnosing root cause.
A targeted fix is applied with proof it works.
The bug file moves to the configured bugs directory (default .shipper/bugs/done/).

Plans are committed markdown. By default they live under .shipper/plans/; a repo can point paths.plans somewhere else. The setup console shows that location. Skills write the files. Full skills reference →