shipkit-shiplisted

# shipkit-ship — Build to Done **Purpose**: The consumer-facing **BUILD** entry point. Takes a plan (`.shipkit/plans/`) and drives it to a confirmed, ground-truth completion bar. **shipkit-ship is a thin caller.** It does **not** implement its own build loop — it states the *what* (steps + bar) and hands off to the engine, which owns the *how* (partition → fan-out → reconcile → integrate → stop-at-bar). This is Shipkit-native **drive-to-done**: one engine, one completion contract. **Read first**: `install/shared/references/core-automation.md` — the contract the engine runs. This skill only assembles the call. --- ## What it does Invoke **`shipkit-orchestrate` in `autonomous` mode** over the plan. Nothing more — the engine runs inline in the main session, launches the parallel build, reconciles against ground truth, integrates serially, and stops at the bar. Pass the engine the four inputs (calling interface in `install/skills/shipkit-orchestrate/SKILL.md`): | Input | For a build | |-------|-------------| | **steps** | the plan's phases / file-ownership clusters, in dependency order — the units to build (from `.shipkit/plans/<feature>.json`) | | **bar** | the **ground-truth** completion criteria (below) — stated explicitly; the engine advances only when they are true on disk / in git | | **mode** | `autonomous` (build runs unattended to the bar) — add the **scale toggle** for very large / long builds | | **elicitive** | normally **none** — a build should run with the s