Tips
Short tips for getting more out of OpenPlanr in Claude Code, Codex and Cursor.
Commit the planning folder with your code
Keep specs, stories, and tasks in the same commits as the code they describe, so every session and teammate reads the same plan.
Plan
Keep the CLI installed next to the plugin
Several skills call the openplanr CLI for deterministic work, so keep it installed even when your agent's plugin is in place.
Build
Let your agent see every skill
Generate the OpenPlanr capabilities guidance so your agent knows every skill and when to reach for it.
Understand
Name the files a task must not touch
Put protected files on a task's Preserve list, and Ship leaves them unchanged while it builds the task.
Plan · Build
Skills add no model calls or telemetry
Every skill runs inside the coding agent you already use, and the CLI never calls a model.
Understand
Plan and ship are separate steps
Your agent never chains planning into building on its own, so you can review the plan before any code changes.
Plan · Build
Restart your agent after setup
Your coding agent loads its skills when it starts, so restart it after setup or a plugin update before you look for a skill.
Debug
Start with doctor when a skill misbehaves
The doctor command shows every managed installation and what is unhealthy, and previews repairs before it changes anything.
Debug
Ask for status as often as you like
Status reads the plan and changes nothing, so it is safe to run before every standup or handoff.
/planr:status$status@planr-statusWith the OpenPlanr plugin for Codex, use
$planr:status.Cursor applies the
planr-statusrule when you mention it in chat.Understand
You can undo setup
Roll back to the state before setup, or remove one agent's OpenPlanr files, without losing files you changed.
Debug