---
title: Find what is blocked and why
description: List blocked work, the dependency behind each block, and the most useful next step.
url: https://openplanr.dev/docs/prompts/find-what-is-blocked
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/status-check.md
  - https://openplanr.dev/docs/prompts/open-the-dashboard.md
  - https://openplanr.dev/docs/prompts/route-a-mixed-request.md
---

# Find what is blocked and why

List blocked work, the dependency behind each block, and the most useful next step.

## Prompt

Claude Code:

```text
/planr:status SPEC-001. What is blocked, what is it waiting on, and what should happen next?
```

Codex:

```text
$status SPEC-001. What is blocked, what is it waiting on, and what should happen next?
```

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

Cursor:

```text
@planr-status SPEC-001. What is blocked, what is it waiting on, and what should happen next?
```

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

Parts to fill in, shown with their example text:

- The spec or feature: SPEC-001

## Why this works

Status reports counts, ready and blocked work, dependency problems, and the most useful next action, for the whole project or one feature. It reads local files by default and queries GitHub or Linear only when you ask for live remote state.

## Make it stick

[Plans are files](https://openplanr.dev/docs/get-started/plans-are-files.md)