ship

Runs one build slice through build, signoff, fix, and recheck stations with a hard lap limit.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/line7works/tony-skills --skill ship-line7works
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/line7works/tony-skills/tree/main/plugins/ship/skills/ship
Command: npx skills add https://github.com/line7works/tony-skills --skill ship-line7works

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a feature slice normally means manually chaining four separate review stations — build, signoff, fix, recheck — and remembering when to stop. This Skill runs that entire loop from a single command while enforcing hard stop conditions so a run never grinds past its retry limit. ## Core Features & Use Cases - One-command loop: Finds the build doc, invokes /build on the named slice, runs /signoff, fixes every BLOCKER and MAJOR, then runs /recheck — all without typing the chain by hand. - Hard lap limit and stop conditions: Allows at most one extra fix-and-recheck lap, and stops immediately if a fix would change the spec, touch files outside slice scope, or if /build stops mid-slice. - Station composition: Each station (/build, /signoff, /recheck) runs under its own rules; /ship only schedules the visits and reports the roll-up SHIP block. - Use Case: After drafting a build doc with /blueprint, type "/ship A" to execute slice A end-to-end and receive an honest ALL CLEAR or STOPPED report with fixed and remaining findings. ## Quick Start Ask the assistant to run "/ship A" to execute slice A of the current build doc through the full build, signoff, fix, and recheck loop.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full build and review loop on one slice?

Invoke /ship with the slice name, such as "/ship A" or "ship slice B of docs/plan.md". The skill finds the build doc, runs /build, /signoff, fixes BLOCKER and MAJOR findings, then runs /recheck, and reports the result.

How many retry laps does the ship loop allow?

The loop allows one initial pass plus at most one extra fix-and-recheck lap. If the slice is still not ALL CLEAR after the second lap, the run stops with an honest report; a third lap only happens if the user explicitly orders it.

What stop conditions end a ship run early?

Four conditions end the run: the extra lap is exhausted without ALL CLEAR, a fix would require changing the spec, /build stops mid-slice, or a fix wants to touch files outside the slice scope. Each produces a stop-and-report, never silent continuation.

Does the ship skill modify the build doc or git history?

No. Stations own their own ledger lines and status cards; /ship only records a user's mid-run waiver or reopening as a dated ledger line. It never pushes, opens a PR, or merges — those git gates remain the user's alone.

What happens when a station needs a decision from the user mid-run?

That is a pause, not a stop. The skill relays the station's question verbatim and waits for the user's answer, then resumes where it paused. Pauses never emit the final SHIP block and are noted in the report's bottom line.