ship-readylisted

# ship-ready Turn a unit of work into code you'd actually merge — correct, tested, reviewed, idiomatic, and complete against its acceptance criteria — without a human babysitting the middle, and **without the loop burning tokens re-checking work that's already clean.** This skill is a **universal orchestrator**: it detects the project it's running in and adapts, instead of assuming any stack, shape, or toolchain. The headline idea: **resolve all ambiguity up front with an interview, then run an autonomous build that converges on correctness behind a machine gate — and treats code-cleanliness as advice, not a gate.** A human is in the loop in exactly two places: the grilling at the start, and a confirm before anything outward (commit / PR / ticket write) at the end. Everything between is autonomous and structurally gated. ## The shape (three stages) ``` INLINE ── Intake → GRILL (grill-me) → PRD (WHAT) + ProjectProfile (detected here) → save .prd/ ──┐ (the only human-facing stage) ▼ author Workflow (CONFIG inlined) WORKFLOW ── Plan → Research → Implement → ⟲ A: converge(correctness+completeness) → B: polish×1 (advisory) → Ship-gate ──┐ (one Workflow, autonomous, machine-gated) ▼ INLINE ── present ShipVerdict (+ simplifications ledger) → confirm-first commit / PR / ticket write-back ``` Two things changed from the obvious des