Skill · Status, routing and sync
/planr:status$status@planr-status
See what is done, pending, blocked, and next from the plan in your repository, without changing anything.
/planr:statusin Claude Code
$statusin Codex. With the OpenPlanr plugin for Codex, use $planr:status.
@planr-statusin Cursor. Cursor applies the planr-status rule when you mention it in chat.
What it does
Inspect project delivery or one feature's pipeline status without changing state. Use when the user asks what is done, pending, blocked, or next.
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.
When to use it
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
/planr:status$status@planr-statusPrompts and commands
Find what is blocked and why
List blocked work, the dependency behind each block, and the most useful next step.
Ask what is done, blocked, and next
Read delivery status from the plan in your repo without changing anything.
Stress-test an operating review
Have the challenger test the review's claims, alternatives, downside, and confidence.