---
title: OpenPlanr Plan Review
description: Review an OpenPlanr plan for product, engineering, design, and developer-experience problems. Use after planning and before implementation to improve the plan.
url: https://openplanr.dev/docs/skills/plan-review
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/skills/plan.md
  - https://openplanr.dev/docs/skills/spec.md
  - https://openplanr.dev/docs/skills/sprint.md
---

# OpenPlanr Plan Review

Skill family: Plan and specify.

Review a plan for product, engineering, design, and developer-experience problems after planning and before anyone builds. You get one verdict and concrete corrections.

Review an OpenPlanr plan for product, engineering, design, and developer-experience problems. Use after planning and before implementation to improve the plan.

## Run it

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

## Use it to

- Review an implementation plan for product, engineering, design, and developer-experience problems
- Challenge a plan before implementation

## Not for

- Implement the plan
- Write a new specification from vague intent

## Example prompt

Claude Code:

```text
/plan-review SPEC-001
```

If /plan-review runs another command, use /planr:plan-review.

Codex:

```text
$plan-review SPEC-001
```

With the OpenPlanr plugin for Codex, use $planr:plan-review.

Cursor:

```text
@planr-plan-review SPEC-001
```

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

The review checks that the outcome is clear and measurable, then looks at scope, sequencing, ownership, architecture, migration, security, operability, testing, and rollback in proportion to the change, plus the first-run and everyday developer experience. It uses only the lenses the work needs.

It leads with one verdict: ready, ready with improvements, or needs revision. Then come the issues that must be fixed, the improvements worth making, the open decisions with a recommended default, and the smallest next step, each finding tied to the plan section it affects. See [Review before it lands](https://openplanr.dev/docs/guides/review.md).