Agent skills
Planning and building are plain agent skills installed globally for your coding agent. Invoke them from Claude Code, Cursor, or opencode. The setup console shows configuration; it does not run these skills.
On your first shipper run (or via shipper skills), skills are installed into ~/.claude/skills/, ~/.cursor/skills/, or ~/.config/opencode/skills/ depending on your agent.
When the Shipper MCP server is installed, the skills use shipper_search to find related prior work before exploring the codebase, and fall back to grep/glob when the tool is not available.
shipper-plan
Explores your codebase, asks clarifying questions, and writes a phased markdown plan to the configured plans directory (default .shipper/plans/open/). Also supports module URLs — install a Shipper module and plan building it into your repo.
e.g. “/shipper-plan https://shipper.is/modules/customer-support”
shipper-loop
Orchestrates an entire open plan in one chat. Spins up a fresh subagent per phase that runs shipper-build, monitors progress, and continues until the plan moves to the configured done folder (default .shipper/plans/done/).
e.g. “/shipper-loop on .shipper/plans/open/my-feature.md”
shipper-build
Implements a single phase of an open plan in one agent session — checks off tasks and writes Completion Notes. Use when you want one phase at a time; prefer shipper-loop to finish the whole plan.
e.g. “use shipper-build on .shipper/plans/open/my-feature.md Phase 2”
shipper-spike
Small one-off feature: plan and build in a single agent session.
e.g. “use shipper-spike to add a copy button to the hero”
shipper-ship
Scaffolds a reviewable pull request from a completed plan — what changed, how to verify, and known risks. Creates the PR via gh.
e.g. “use shipper-ship on .shipper/plans/done/my-feature.md”
shipper-bug
Evidence-first bug catalog and fix workflow. Reproduce before diagnosing, then drive the fix to proof in .shipper/bugs/.
e.g. “use shipper-bug to fix the login redirect loop”
Plans are committed markdown. They default to .shipper/plans/ and can be moved with paths.plans in the repo config. The setup console shows that directory; skills write the files.