---
title: OpenPlanr Ship
description: Implement an OpenPlanr plan, specification, task, or clearly stated request end to end in the current repository.
url: https://openplanr.dev/docs/skills/ship
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/skills/delegate.md
---

# OpenPlanr Ship

Skill family: Implement.

Build one task, or a clearly stated change, end to end in your repository, then run the checks the repository defines. Ship keeps the work local and does not publish or deploy it.

Implement an OpenPlanr plan, specification, task, or clearly stated request end to end in the current repository. Use when the user asks to build, implement, fix, finish, or ship local work.

## Run it

- Claude Code: `/ship`. If /ship runs another command, use /planr:ship.
- Codex: `$ship`. With the OpenPlanr plugin for Codex, use $planr:ship.
- Cursor: `@planr-ship`. Cursor applies the planr-ship rule when you mention it in chat.

## Use it to

- Implement a plan, specification, task, fix, or clearly stated local request
- Build and verify the requested repository change
- Ship this
- Ship task
- Implement this task
- Implement this plan with parallel coding agents
- Use native parallel agents to implement this task
- Fix the delegate runner in the active agent

## Not for

- Only plan the work
- Prepare a release without changing code
- Have Codex implement this task
- Use Codex to implement this
- Have Claude Code implement this task
- Ask another coding agent to implement this task
- Use another coding agent to build this change

## Use instead

- [OpenPlanr Land](https://openplanr.dev/docs/skills/land.md)

## Example prompt

Claude Code:

```text
/ship T-001
```

If /ship runs another command, use /planr:ship.

Codex:

```text
$ship T-001
```

With the OpenPlanr plugin for Codex, use $planr:ship.

Cursor:

```text
@planr-ship T-001
```

Cursor applies the planr-ship rule when you mention it in chat.

Ship reads the task completely, then its story, the acceptance criteria, the Gherkin file when there is one, and the spec. It treats the task's Create and Modify lists as the expected surface, adds companion files when correctness needs them, and leaves the Preserve list unchanged.

It finds checks in the task's test requirements, the repository instructions, the package scripts, and the CI configuration, runs them, and fixes failures its own change caused. The reply gives the outcome (completed, partial, or blocked), the task, the files changed, each check with its result, and any open issue. See [Build one task at a time](https://openplanr.dev/docs/guides/build.md).