Ship It: Autonomous Build-to-Ready Loop

You name the feature once. This self-drives until the work is provably ready for you to test, and it halts the instant it needs something only you can give.

The loop is the easy part. The VERIFIER is what makes it safe to run unattended. So this skill writes the verifier (machine-checkable success criteria) FIRST, then loops against it. That is why it cannot declare fake victory or spin forever.

When to use / not use

• USE: "build X until it's ready for me to test", any hands-off build.
• NOT: deploying a finished PR (use /ship); looping an existing qa-checklist.yaml (self-loop it here); planning a feature that isn't scoped yet (use /planning-pipeline first, then come here).

What you type

/ship-it <feature description> (optionally: /ship-it <feature> using the plan at <path>)

The autonomous contract (what "hands-off" means here)