ship-think
Ship Think
Combat the founder/engineer brain that wants to jump straight to code. This is not a planning phase — it's a short, sharp gut check that surfaces the questions you're avoiding.
Process
1. Understand what they want to build
If the user provided an argument, use that. Otherwise, read the recent conversation context to understand what they're about to work on. If neither is clear, ask one question: "What are you about to build?"
2. Read the profile
Check .claude/ship.local.md for user context. If it doesn't exist, proceed without it — but mention they can run /ship:init to calibrate things.
The profile shapes the questions. Read both the YAML settings and the product brief (the markdown body). The "What moves the needle" section tells you what actually matters for this product right now. If the thing they want to build doesn't connect to those needle-movers, that's your most important question.
3. Read the codebase (briefly)
Glance at the project structure and any files directly relevant to what they're describing. The goal is to ground the questions in reality — not to do a full audit. Spend no more than a few file reads here.
More from withqwerty/ship
ship-init
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.
1ship-debrief
Use 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).
1ship-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).
1