Ship It
Send it all the way into production and check that it’s healthy.
What it is
Section titled “What it is”Send it all the way into production and check that it’s healthy — promote to prod, then verify/observe live health. Not “merge a PR.” This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.
Why it works
Section titled “Why it works”Continuous delivery keeps software releasable; progressive delivery (canaries, flags) limits blast radius (Google SRE). Promote with evidence and rollback/kill-switch thinking—not hope.
When to use it
Section titled “When to use it”When the situation matches the one-liner above and Orientation (or Deliver / Operate) says this is the fire to touch now.
- Invoke the skill; follow its safety rules
- Keep one write owner; collect evidence before claiming done
- Hand off to the next practice instead of boiling the ocean
- Skip orientation when you’re lost
- Spawn overlapping agents to “go faster”
- Treat the practice as done without evidence
Related concepts
Section titled “Related concepts”07-stop-conditions, 01-this-is-fine-stance
Further reading
Section titled “Further reading”- DORA — Continuous delivery
- Google SRE Workbook — Canarying releases
- Google SRE — Reliable product launches
See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”ship-it