shiplisted

# Ship `/ship` takes the spec `/to-spec` published and builds it, unattended, until a final adversary says it can go — then pushes it. It is the lean pipeline. Where `goals` councils, gates, and stops at every milestone, `/ship` runs one contributor and one reviewer per item, checks the gate before spending either, and stops only for trouble. `goals` remains available for work that earns the ceremony. The whole flow: **`/grill-with-docs` → `/to-spec` → `/ship`.** The handoff and push happen inside `/ship`. ## Input Read `docs/agents/issue-tracker.md` to learn where `/to-spec` published — GitHub Issues, GitLab, or `.scratch/`. Fetch the spec from there. `/ship <reference>` takes an issue number, URL, or path; with no argument, find the most recent spec carrying the `ready-for-agent` label. Derive a stable `<slug>` from the spec's identifier (issue number + title slug, or the filename). The slug is the resume key — pin it in `goal.md` and never recompute it from a different source. ## State `/ship` is the sole writer of everything under `CONTEXT/ship/<slug>/`. Reviewers report findings; they never edit state. ```text CONTEXT/ship/<slug>/ goal.md plan, locked gates, success criteria backlog.jsonl runtime state handoff.md resume cursor lock.d/owner.json reviews/M<n>.json milestone verdicts reviews/T3.json final adversary verdict CONTEXT/worktrees/<slug>/ results.json <id>.digest.json *.log ``` Every backlog line has at most