By withqwerty
Think. Build. Ship. A brutally simple workflow that combats your worst instincts and gets code out the door.
npx claudepluginhub withqwerty/plugins --plugin shipUse this skill when the user wants a weekly check-in, retrospective, or recalibration of how they're building. Trigger on "ship debrief", "debrief", "weekly check-in", "how am I doing", "where did my time go", "ship retro", "debrief with dhh", "recalibrate my profile", "update my priorities", or when the user wants to reflect on their recent work and adjust direction. Also trigger when another ship skill nudges that a debrief is overdue. Do NOT trigger for code review (use ship-review), profile setup (use ship-init), or mid-build scope checks (use ship-focus).
Use this skill when the user is mid-build and drifting, scope is creeping, or focus is lost. Trigger on "ship focus", "scope check", "refocus", "what should I cut", "am I scope creeping", "this is getting bigger than expected", "I'm losing focus", "I keep finding things to improve", "should I stop and ship what I have", or "new requirements came in". Also trigger when the user expresses frustration about a task growing beyond its original intent, mentions touching many more files than expected, or asks whether to change direction mid-build. Do NOT trigger for pre-build gut checks (use ship-think) or post-build reviews (use ship-review).
Use this skill when the user wants to set up, configure, or initialize the ship plugin, create or update their ship profile, change their review mode, update their product brief, or edit .claude/ship.local.md. Trigger on "ship init", "set up ship", "configure ship", "create my profile", "update my profile", "change review mode to brutal/kind", or when any other ship skill detects that .claude/ship.local.md does not exist. Also use when the user says they've changed roles, shifted priorities, or moved to a new project stage.
One reviewer. One pass. Everything that matters, nothing that doesn't.
Use this skill when the user is about to start building something and would benefit from hard questions before coding. Trigger on "ship think", "gut check", "sanity check", "should I build this", "before I start", "does this make sense", "is this worth building", "is this overkill", or "thoughts on this approach". Also trigger when the user describes a feature, migration, rewrite, or architectural change they're planning — even if they don't explicitly ask for a gut check. If someone says "I'm thinking of building X" or "I want to add X", this skill should activate to challenge assumptions before they start coding. Do NOT trigger for bug fixes, code explanations, or tasks already in progress.
Think. Build. Ship.
A plugin for AI coding tools that stops you from over-building and helps you actually ship.
/plugin marketplace add withqwerty/plugins
/plugin install ship@withqwerty
/ship:init
Three commands. The init asks you a few questions and writes a small file that all the other commands read. Then just use the commands when you need them — they're not a workflow, they're tools in a drawer.
Five commands that intervene at the moments that matter:
/ship:init — Tell it who you are, what you're building, and what matters. Takes 2 minutes. It remembers./ship:think — Before you build something, it asks the hard questions you're avoiding. Sometimes it just says "go build it."/ship:focus — When you're mid-build and the thing keeps growing, it looks at your git diff and tells you what to cut./ship:review — Before you merge, it reviews your code. Two modes: brutal (high bar) or kind (flags only what'll break)./ship:debrief — Weekly check-in. Looks at what you actually shipped, asks if your priorities still match your behavior, updates your profile.Works with Claude Code, Cursor, GitHub Copilot, OpenCode, and 40+ other agents.
npx skills add withqwerty/ship
git clone https://github.com/withqwerty/ship.git
claude --plugin-dir /path/to/ship
Pull requests welcome. The bar is high — this plugin exists to fight complexity, so any addition needs to earn its place.
Before opening a PR:
references/ directory, it's probably too complex.claude --plugin-dir /path/to/shipGood contributions:
Please don't:
MIT
Opinionated workflow skills. Hard gates, not suggestions. Spec through blueprint, implementation, verification, and shipping -- the skills refuse to let you skip steps.
Share bugs, ideas, or general feedback.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,393 supported skills.
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, Hermes, and 17+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.