Skip to content
Skills Library
Programming · Automation

ship

/ship

Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix something non-trivial with the crew, or invokes /crew:ship.

Licence
MIT
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix something non-trivial with the crew, or invokes /crew:ship.

Original author description

Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix something non-trivial with the crew, or invokes /crew:ship.

How it works

  1. 0. Triage
  2. 1. Plan (crew:planner, for non-trivial work)
  3. 1b. Challenge (crew:skeptic, whenever the planner ran)
  4. 2. Implement
  5. 3. Test (crew:tester)
  6. 4. Review (crew:reviewer)
  7. 5. Docs (crew:docs-writer, only when the user-facing surface changed)
  8. 6. Hand back to the user
Original SKILL.md headings · 74 lines, 580 words
SKILL.md preview
---
name: ship
description: Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix something non-trivial with the crew, or invokes /crew:ship.
---

# Ship with the crew

You, the main session, orchestrate. **Subagents don't see this conversation.** Every brief you send must be self-contained: the repo path, the goal, the exact files or packages, the acceptance criteria and the constraints.

Task: $ARGUMENTS

## 0. Triage

- **Pick the coder by repo type:**
  - TypeScript web (Next.js, NestJS, Prisma, Expo) → `crew:web-coder`
  - Visual or UI-heavy work → `crew:ui-builder`, which can pair with `web-coder` for the data and API side
  - Any other stack (Python, PHP, Go, Rust, Ruby, Java/Kotlin, .NET, native mobile, CLIs, scripts) → `crew:coder`
- **Tiny, clear change** (1–2 files) → skip the planner.
- **Unclear requirement** → ask the user with AskUserQuestion before spending agent time.

## 1. Plan (`crew:planner`, for non-trivial work)

- Brief the planner with the task as the user stated it, the repo path and any constraints.
- Read the plan critically. Put product-level open questions to the user before any code is written.
- Carry assumptions the user didn't confirm into the final summary.

## 1b. Challenge (`crew:skeptic`, whenever the planner ran)

- Brief the skeptic with the user's task verbatim, the repo path and the full plan.
- **GO:** continue.
- **GO WITH CHANGES:** fold the 🔴 and 🟠 objections into the plan.
- **RETHINK:** stop and show the user the plan and the objections before writing code.
- Show the user the plan with the skeptic's verdict in 5–10 lines and wait for an OK before implementing. This is the checkpoint: no long unattended runs.

## 2. Implement

- Brief each coder with:
  - the goal
  - its plan steps
  - the exact files and packages
  - the acceptance criteria
  - the constraint: no commits, no deploys
- **Parallelize only disjoint work.** Example: `web-coder` on `apps/api` while `ui-builder` builds `apps/web` against an agreed contract or types. Work in the same files stays sequential.

## 3. Test (`crew:tester`)

- Brief the tester with the changed files (from the coder reports or `git diff --name-only`) and the acceptance criteria.
- If the tester reports production bugs:
  1. Send its findings verbatim to the coder.
  2. After the fix, re-run the tester on the affected area.

## 4. Review (`crew:reviewer`)

- Save the diff inside the repo's git directory, where it is never committed: `git diff HEAD > "$(git rev-parse --git-dir)/crew-review.diff"`. List new untracked files with `git ls-files --others --exclude-standard`: a diff doesn't contain them. The reviewer has no shell.
- Brief the reviewer with the repo path, the diff file path, the changed and new files, a 3-line plan summary and the tester's results (tests, typecheck, lint).
- On **CHANGES REQUIRED**:
  1. The coder fixes the 🔴 and 🟠 findings.
  2. The tester re-runs the affected tests.
  3. The reviewer re-checks only the fixes.
- Run at most **2 loops**. After that, stop and put the remaining items to the user.

## 5. Docs (`crew:docs-writer`, only when the user-facing surface changed)

Use the docs-writer for new or changed:
- commands and permissions
- config, messages or GUI keys
- placeholders
- API, env or setup steps
- architecture worth a `CLAUDE.md` update

## 6. Hand back to the user

- What was built (2–4 lines) and the files changed.
- Test results and the review verdict.
- Assumptions made and follow-ups.
- Proposed Conventional Commit message(s), matching the repo's `git log` style and language. Use one commit per logical change.
- **Do not commit, push or deploy until the user approves.** Keep commits meaningful.

Versions

RepositoryScoreLicence
This page · kavicka/claude-crews100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
namedtoaster/the-last-mile100MIT
rjmurillo/ai-agents100MIT
ericrisco/rsc-harness100MIT
zahidakhyar/skills100MIT
NolwennD/gabier100Apache-2.0
mgiovani/cc-arsenal100MIT

Database snapshot: 13.11.2026 · package version 744d12bf6358 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100crew-ship
    Ships a scoped change through native phux missions, isolated worktrees, independent review and authorized publication. Use when the Crew lead dispatches implementation work.
  • 86check
    Verifies the current uncommitted changes, or a branch or PR, with the crew. The tester extends and runs the tests, the reviewer reviews, and the result is a go/no-go. Use when the user asks to check, verify or review changes before committing, or invokes /crew:check.
  • 86check
    Verifies the current uncommitted changes, or a branch or PR, with the crew. The tester extends and runs the tests, the reviewer reviews, and the result is a go/no-go. Use when the user asks to check, verify or review changes before committing, or invokes /crew:check.
  • 100workflow-build-feature
    Build a feature end to end: spec and TDD, implement, unit tests, Playwright check, PR. Use when "build a feature" or "implement this end-to-end". Spec/TDD loop only → workflow-spec-tdd. One bug → workflow-fix-and-ship.
  • 82import
    Guided import of a crew export onto this machine — asks where the bundle file is, walks the plan and decides each project (clone, adopt a checkout already here, replace) and workspace with the user. Use when the user mentions a crew export/bundle/JSON from another machine, wants…
  • 95crew
    Complete CLI reference for crew — projects, workspaces, worktrees, dev servers on stable per-worktree ports, env bindings, launching Claude and editors, crew's server (the web page: Set up and Voice OS, its keys, remote machines), moving to another machine, disk housekeeping.…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.