---
title: Plan and ship are separate steps
description: Your agent never chains planning into building on its own, so you can review the plan before any code changes.
url: https://openplanr.dev/docs/tips/plan-and-ship-are-separate
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/plan-a-spec.md
  - https://openplanr.dev/docs/prompts/plan-from-intent.md
  - https://openplanr.dev/docs/prompts/plan-ui-from-design.md
---

# Plan and ship are separate steps

Your agent never chains planning into building on its own, so you can review the plan before any code changes.

`/planr:plan` (Claude Code), `$plan` (Codex) or `@planr-plan` (Cursor) ends with a handoff: it names the next ready task and gives you the exact command to build it. It never starts building on its own, and the router never chains the two on your behalf.

That pause is the point. Read the stories and tasks, fix what is wrong, and commit them. Then start the build with `/ship` (Claude Code), `$ship` (Codex) or `@planr-ship` (Cursor) and one task ID.