Ship a validated change to production - sequences observability and a staged rollout, then gates the outward-facing deploy behind a final go/no-go. Usage /groundwork:ship.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Ship
Orchestrator for the **ship phase** — the last leg of the lifecycle, after the change is built, validated, and reviewed. It sequences the ship disciplines and stops at a human go/no-go before anything reaches users.
<!--
Design note: this is a USER-ONLY LEAF (disable-model-invocation: true). It must be
started deliberately by the user — the router and other skills cannot auto-fire it.
That flag only blocks OTHER skills from calling THIS skill; it does NOT stop this skill
from calling dual skills. So Step 2 dispatches instrument-observability / staged-rollout
(both dual) via the Skill tool without issue.
-->
## Step 1: Confirm Validation and Review Passed
Shipping presupposes a clean change. Confirm both gates already cleared:
- **Validation** passed — see [[validate]].
- **Review** passed — see [[review-pr]].
Check for evidence (a green validation run, an approved PR). If you cannot confirm either, **stop** and ask the user to run [[validate]] / [[review-pr]] first. Do not re-run them here; this skill assumes they are done.
## Step 2: Sequence the Ship Disciplines
…
The line at the top of this page pins the label git:20260622.3609064, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3638 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
etr/groundwork · 45 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iztoae35kpkcw7g4
GET https://markdownregistry.com/api/v1/resolve?ref=etr/groundwork/ship
GET https://markdownregistry.com/api/v1/blob/6d077f7666152e527c071f7f7fb4b5c48a8030eafa7ee5170f030aaa6f6c79a0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
etr/groundwork · skills/build-unplanned/SKILL.md · Build a feature from description with worktree isolation and TDD. Usage /groundwork:build-unplanned "Add user login"
etr/groundwork · skills/debug/SKILL.md · This skill should be used when investigating bugs, unexpected behavior, test failures, or any code that does not work…
etr/groundwork · skills/design-architecture/SKILL.md · This skill should be used when the user asks to design system architecture, make architectural decisions, or translate…
etr/groundwork · skills/design-it-twice/SKILL.md · Use before committing to a non-trivial module, service boundary, or public API - generate 2-3 divergent interface…
etr/groundwork · skills/domain-modeling/SKILL.md · Use when designing a product or feature and the project lacks shared, agreed terminology - builds and maintains a pure…
etr/groundwork · skills/doubt-driven-development/SKILL.md · Use when building a high-stakes or hard-to-reverse change - schema/data migrations, auth, payments, public API surface…
etr/groundwork · skills/finalize-task/SKILL.md · Use when a task worktree has passed validation - manually commits, merges, and cleans up, or prepares runner-owned…
nightly-labs/openbot · .agents/skills/ship/SKILL.md · Ship the current branch to main. Review the diff, fix findings, open the pull request, babysit the NorbiAI review and…
plugin87/ux-ui-agent-skills · .claude/skills/ship/SKILL.md · Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README…
suboss87/fdeops · skills/ship/SKILL.md · Prepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a…
snowflake-labs/cocoplus · .cortex/skills/cocobrew/ship/SKILL.md · Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag…
tobihagemann/turbo · claude/skills/ship/SKILL.md · Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship"…
tobihagemann/turbo · codex/skills/ship/SKILL.md · Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship"…
