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.