You don't need another workflow. You don't need a six-phase review pipeline. You definitely don't need 22 AI agents arguing about your pull request. What you need is someone to ask "why are you building this?" before you're three days into a refactor nobody asked for. That's Ship. Five commands. Zero ceremony. The hard questions at the moments that matter.
Install
1
/plugin marketplace add withqwerty/plugins
2
/plugin install ship@withqwerty
3
/ship:init
Run each in Claude Code. Copy, paste, enter.
Works with 40+ agents: npx skills add withqwerty/ship
Five commands
/ship:init
Tell it who you are, what you're building, and what would actually move the needle. Two minutes. It writes a profile that every other command reads.
/ship:think
Before you build something, it asks the hard questions you're avoiding. Checks if the thing you want connects to what actually matters. Sometimes it just says "go build it."
/ship:focus
When you're mid-build and the thing keeps growing, it reads your git diff and tells you what to cut. Names the files. Names the scope creep. Gets you back on track in 30 seconds.
/ship:review
Before you merge. One reviewer. One pass. Everything that matters, nothing that doesn't. Every review ends with a verdict: Ship it, Fix these first, or Needs rework.
brutalkind
/ship:debrief
Weekly check-in. Looks at where your time actually went, not where you think it went. Updates your priorities based on evidence. The suggestion might be code, or it might be "go talk to five users."
What this is not
Not a workflow. No six-phase pipelines. No mandatory steps. Use what you need, ignore what you don't.
Not 22 review agents. One reviewer. Two modes. Done.
Not a planning tool. Ship exists to kill ceremony, not create it.
Not a framework. No dependencies. No build step. No config. Five markdown files in a directory.
How it works
Ship is built on agent skills, reusable instruction sets that extend what AI coding tools can do. You can use them three ways:
Slash commands. Type /ship:think or /ship:review kind to invoke a skill directly.
Natural language. Say "gut check this" or "review my changes" and the skill activates automatically.
Implicit triggers. Describe a feature you're planning and the AI recognises that a gut check would help. No command needed.
