---
title: OpenPlanr Status
description: Inspect project delivery or one feature's pipeline status without changing state. Use when the user asks what is done, pending, blocked, or next.
url: https://openplanr.dev/docs/skills/status
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/skills/dashboard.md
  - https://openplanr.dev/docs/skills/openplanr.md
  - https://openplanr.dev/docs/skills/sync.md
---

# OpenPlanr Status

Skill family: Status, routing and sync.

See what is done, pending, blocked, and next from the plan in your repository, without changing anything.

Inspect project delivery or one feature's pipeline status without changing state. Use when the user asks what is done, pending, blocked, or next.

## Run it

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

## Use it to

- Report current OpenPlanr delivery status or outstanding work
- Show progress for one feature or the whole project

## Not for

- Open the visual dashboard
- Modify planning state

## Example prompt

Claude Code:

```text
/planr:status
```

Codex:

```text
$status
```

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

Cursor:

```text
@planr-status
```

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

Status reads the planning files, task statuses, dependency graph, current branch, and runtime markers directly. It reports counts, ready and blocked work, dependency problems, and the most useful next action, for the whole project or one feature.

It never repairs files, starts Plan or Ship, or changes a status. It works from local files, queries GitHub or Linear only when you ask for live remote state, and says which data it inspected and how fresh it is. See [Track delivery and run operating reviews](https://openplanr.dev/docs/guides/operate.md).