ship

name	ship
description	Use when asked to ship, build, implement, fix, or deliver a change end-to-end — "ship X", "get it out", "build this", a tracker ID plus a fix request, or any feature/bugfix meant to land in main.

Ship

Overview

Take a request from message to merged-and-documented. The deliverable of a ship is a squash-merged PR that passed review and green CI with the merge authority's explicit approval in this conversation, followed by a documentation sync. "Ship it" grants urgency, not merge authority.

Operator config

If config.md exists in this skill directory, read it first — it sets the parameters below. Without it, use the defaults.

Parameter	Meaning	Default
merge_authority	Who approves merges. Agents never merge on their own.	The human operator in the conversation
dispatch_model	Model policy for every dispatched agent, reviewer, and workflow agent() call	Inherit the session model
tracker	Issue tracker for tickets, verified-close, and follow-ups	Whatever the repo uses; skip tracker steps if none
spec_paths	Where written specs/plans live	docs/superpowers/specs/, docs/superpowers/plans/
sensitive_paths	Diff areas that escalate review effort to xhigh	Payments, auth/credentials, data migrations
build_check	The build that matches CI's strictness