ship-itlisted

# ship-it Drive one goal end to end — research → plan → **review the plan** → implement → test for real → PR → **review the PR** — and **loop each review checkpoint until done**, not until first pass. This is the build chain you already type from memory, made durable, portable, and gate-disciplined. Optimize for *verified completion against a pinned spec*, not for sounding finished. ## Operating principle: pin a spec, gate the chain, loop until the gate is clean The value here is the gates, not the verbs. Externalize the discipline the freehand prompt trusts you to hold in your head: review the PLAN adversarially **before** a line is built (when fixing it is a doc edit, not a rebuild), block edits behind operator approval, exercise the real app, and gate "done" on the global `/review-loop`'s explicit `<promise>review-clean</promise>` marker plus an in-scope audit. Compose only capabilities that resolve in **any** project on **any** machine — the GLOBAL `/review-loop`, native plan mode + `ExitPlanMode`, native `Agent` subagents, `AskUserQuestion`, `session-end`. Everything project-local (its own test/lint/build, visual-QA, PR status) is **discovered or described generically**. **Operates on the CURRENT repo (cwd) only** — it builds and ships the checked-out project, never another. This skill is global, so it also loads in a Command operator session, where the delegate-the-WHAT rule still binds: if the goal's work belongs in a *different* repo, file it there as a requiremen