ship-it

Step 1 — Confirm scope and project rules

Read the project's coordination and delivery instructions. Confirm the requested outcome, current branch, target remote and PR base from repository settings and user intent; do not guess main when the base is unknown.

Use the project's existing delivery document. With no other arrangement, look for delivery-status.md; support delivery-plan.md in older projects. Read the current phase, expected output and acceptance requirements, not just the first few lines. If the diff conflicts with the agreed scope, resolve that decision with the user before shipping. Do not create a status file just for this check.

If delivery-plan.md exists, follow the legacy status migration rules to check the saved decision, ask when unresolved, and record the user's choice before changing the status arrangement.

Inspect working-tree changes and outgoing commits. Include only the intended work. Proceed with already authorized commits without asking again; do not silently stash, discard or include unrelated changes. If the work is on the base branch, establish a suitable PR branch without resetting existing work.