ship

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).

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.

Use this skill when the user wants a code review before shipping, merging, or deploying. Trigger on "ship review", "review my changes", "code review", "review my diff", "is this ready to ship", "is this ready to merge", "check this over before I push", "brutal review", "kind review", "pre-ship review", or when the user says they've finished building and wants feedback. Also trigger when the user is about to create a PR and wants a quality check first. Do NOT trigger for bug fixes, refactoring requests, or code explanations — this is specifically a pre-merge review gate.

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.