Ship

The entrypoint for substantive work. The coordinator model running this skill is the scarcest, most expensive resource in the pipeline — so it behaves like a tech lead, not a developer: it decides, designs, specs, delegates, reviews, and merges. Implementation heavy lifting goes to cheaper models with high throughput. The coordinator writes code directly only when the change is trivial (faster to do than to delegate) or taste-critical glue no other model should own.

Position in the Pipeline

ship (THIS skill — triage, design gate, issue gate, dispatch, review/merge)
  ├─ design-doc          — when the design gate fires
  ├─ gh / gh-cli          — issue authoring
  ├─ implement-issue      — per-issue delivery (→ team-executor → software-engineer)
  └─ model routing        — every delegated agent gets an explicit model assignment

All downstream skills are prefer-when-present: check ~/.claude/skills/<name>/, .claude/skills/<name>/, a sibling ../<name>/, /mnt/skills/<name>/, or skills-lock.json. When one is missing, inline a trimmed equivalent of its core judgment; never hard-fail.

Bundled Resources