planr plugin
planr keeps agent-driven development tasks in Git Markdown files and shows what is ready, blocked and waiting on you
- 74 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Reads and writes the plan's Markdown files in Git and runs no shell commands or network calls of its own
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/planrDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Reads and writes the plan's Markdown files in Git and runs no shell commands or network calls of its own
This is third-party code. Review the repository files before installing.
What it does
planr is a planning layer for products built by several coding agents. Tasks and dependencies live in a separate planning repository, often private, as Markdown files under Git. There is no database, daemon or MCP server: the tool reads the files and says what comes next. The `planr` CLI checks the files, finds ready tasks and updates their status. The board shows progress and history: what is ready, what is blocked, what waits on you and what changed. planr does not run builds; the project orchestrator does that, for example split-orchestrator. You can start by pasting a prompt into your agent, "Set up planr for this project. Follow https://planr.so/docs/setup.md". It checks Node.js and Git, asks where to keep the plan and sets up the files and the plugin. In Claude Code the skill runs as `/planr:planr`, in Codex as `$planr:planr`, and with the bb plugin the board appears beside your threads. Other agents install the skill with `npx skills add instructa/planr`.
Who it is for. Developers who have several agents working on one product and need a shared plan with dependencies instead of a chat recap.
Good fit when
- Several agents pick tasks from one plan and you need to know which is ready and which waits for another
- The plan should not go through a database and a service: Markdown in Git, visible in diffs, is enough
- Some tasks need your approval and you want the pending decisions listed in one place
- Planning should be separate from code: a private plan repository beside the public project repository
Not a fit when
- You need a tracker for people with statuses, comments and notifications: planr plans agent work and notifies nobody
- You need automatic building and task dispatch to agents: an orchestrator does that and planr only says what is next
- The machine has no Node.js 20 or newer and cannot get it
Example request
Set up planr for this project, create a plan of three tasks with dependencies and show which one is readyLimitations
- It needs Node.js 20 or newer and Git, and the CLI has no runtime dependencies.
- planr does not run tasks or build the project; it says what is next, and a project orchestrator does the running.
- The plan sits in a separate repository and is kept as files, with the structure and format described in `docs/contract.md` and `skills/planr/references/format.md`.
- The detailed treatment of tasks, goals and approvers is in `docs/concepts.md` and not in the README.
How to disable. For Claude Code remove the plugin with claude plugin uninstall, then remove the CLI with npm uninstall -g planr. The plan repository remains a set of Markdown files that you can keep or delete like any folder.
FAQ
How do I install planr in Claude Code?
Paste the prompt "Set up planr for this project. Follow https://planr.so/docs/setup.md" or follow the quick start in `docs/quickstart.md`. The skill runs as `/planr:planr`.
Does it need a database or server?
No. Tasks are Markdown files in Git, and there is no daemon or MCP server. The CLI needs Node.js 20 or newer and Git.
How do I install the CLI?
Globally with `npm install -g planr`, or run it without installing through `npx planr`. The commands check files, find ready tasks and update status.
Does planr launch agents itself?
No. planr shows what is ready, blocked and waiting on you. A project orchestrator such as split-orchestrator handles building and dispatch.
Which agents are supported?
There are plugins for Claude Code and Codex, a bb plugin with the board beside threads, and a skill install for other agents through `npx skills add instructa/planr`.
Discussion
No questions or reviews yet.
Related
PluginsA planning extension for the Pi coding agent: reviewed Markdown plans first, and code changes only after your approval
A local browser UI to annotate agent plans and review diffs, then send the feedback back to the agent
Writ turns workflow rules into checks at tool-call time: Claude Code writes no code until you approve the plan and tests
Python runtime for agent work: task boundaries, independent verification of results and a saved handoff between sessions
A Claude Code skill that drives a hard task through explore, plan, execute and reflect, writing every decision to disk.
A Claude Code plugin links planning, implementation and task checks, retains progress and controls how independently agents work.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| planr (this card) | no | 74 | ||
| Planning with Files | no | 28,037 | a skill that keeps a plan in files for one agent with no board, dependencies or approvers | |
| Taskmaster | no | not required | 28,354 | a task MCP server with its own storage, while planr stores everything in Git files |
README in short
The README briefly states the purpose: planning for agent-built products using Markdown in Git. The get-started section gives a prompt for the agent and a link to the quick start. Plugins for Claude Code and Codex, the bb plugin, the skill install through npx and the CLI follow. Links to documents on concepts, the board and the file format come next, then the MIT license with fonts under OFL 1.1.