---
title: Track delivery and run operating reviews
description: See what is done, blocked, and next from the plan in your repository, and run leadership reviews that end in a decision queue.
url: https://openplanr.dev/docs/guides/operate
updated: 2026-10-06
related: []
---

# Track delivery and run operating reviews

Operating the work means knowing where delivery stands today and stepping back on a regular rhythm to decide what to do next. OpenPlanr reads both from the files in your repository.

## Check delivery status

Invoke `/planr:status` (Claude Code), `$status` (Codex) or `@planr-status` (Cursor) to see what is done, pending, blocked, and next, for the whole project or one feature. Status reads the planning files, task statuses, dependency graph, and current branch, and changes nothing. It reports counts, ready and blocked work, dependency problems, and the most useful next action.

It works from local files and queries GitHub or Linear only when you ask for live remote state. The report says which data it inspected and how fresh it is.

From the terminal, `openplanr status --md` prints the whole-project delivery report as paste-ready Markdown: every spec, backlog item, and quick task by status.

## See the plan on a board

Invoke `/dashboard` (Claude Code), `$dashboard` (Codex) or `@planr-dashboard` (Cursor) to start the local planning dashboard. It binds only to your machine's loopback address, reuses a compatible server that is already running, and opens a browser only when you ask.

## Run an operating review

Invoke `/operate` (Claude Code), `$operate` (Codex) or `@planr-operate` (Cursor) for a periodic leadership review of a product or the business as a whole. It writes one shared brief, then runs 5 advisor lenses:

| Lens | Skill |
| --- | --- |
| Strategy and finance | [ceo-review](https://openplanr.dev/docs/skills/ceo-review.md) |
| Technology and delivery risk | [cto-review](https://openplanr.dev/docs/skills/cto-review.md) |
| Product and activation | [cpo-review](https://openplanr.dev/docs/skills/cpo-review.md) |
| Growth and market | [cmo-review](https://openplanr.dev/docs/skills/cmo-review.md) |
| Operations and customer health | [coo-review](https://openplanr.dev/docs/skills/coo-review.md) |

A challenger then tests only the claims that could change a decision, and a chair turns the notes into one brief. Those are the 7 lenses.

Each review gets its own folder, and a new review never overwrites an earlier one:

```text
.planr/operate/<date>-<slug>/
  cycle.md
  brief.md
  <lens notes>.md
  board-report.md
```

The board report holds the scope, an executive summary, a decision queue of at most 5 decisions, an action plan of at most 7 actions, the risks and dissent, the gaps that could change a decision, and the review coverage. Each decision carries a recommendation, a credible alternative, a confidence level, a first step, and a condition to revisit it.

## Prompts for this stage

- [Ask what is done, blocked, and next](https://openplanr.dev/docs/prompts/status-check.md)
- [Find what is blocked and why](https://openplanr.dev/docs/prompts/find-what-is-blocked.md)
- [See the plan on a local board](https://openplanr.dev/docs/prompts/open-the-dashboard.md)
- [Run a monthly operating review](https://openplanr.dev/docs/prompts/operate-review.md)
- [Stress-test an operating review](https://openplanr.dev/docs/prompts/challenge-the-operating-review.md)
- [Get the technology and delivery-risk view](https://openplanr.dev/docs/prompts/technology-risk-review.md)
- [Turn review findings into decisions](https://openplanr.dev/docs/prompts/turn-findings-into-decisions.md)