OpenPlanr is not a hosted project tracker and does not replace your issue tracker. It closes the loop: the agent reads the plan before it changes code, and what it ships flows back as evidence for the next review.
One canonical skill graph is generated into host-native projections for Claude Code, Codex, and Cursor. Generated files are outputs, never sources.
Stores and validates planning files, renders diagrams and reports, installs the skills into each host, diagnoses installations, and syncs with GitHub Issues and Linear.
The delivery pipeline: PO, design, review, implementation, QA, and delivery outputs, plus self-contained projections of the Protocol, Operate runtime, artifact review, and design contracts.
Public contracts for OpenPlanr local tools and hosted consumers: JSON schemas, canonical registries, and browser-safe schema validation.
Each role agent's manifest lists the only tools it may use. planr-database can run psql, mysql, sqlite3, and mongosh but not git; planr-designer reads, finds, and writes files, with no shell at all.
/planr:plan/shipThe getting started guide in six steps. Plans land under .planr/ in your repository, and you invoke plan and ship as separate steps.
OpenPlanr requires Node.js 20.19+, 22.13+, or 23.5+. The package installs the openplanr command and its short form opr.
$ npm install -g openplanr
$ openplanr --versionopenplanr setup shows exactly what it will write, then installs the skills for the host and scope you choose. Existing files are backed up under ~/.planr/backups/.
$ openplanr setup --runtime claude --scope user --dry-run
$ openplanr setup --runtime claude --scope useropenplanr init creates .planr/config.json and the artifact directories. Commit .planr/ with your code.
$ cd your-project
$ openplanr initRestart the coding agent so it loads the skills. The spec skill reads the repository, asks only the questions that change the outcome, and writes the specification.
> /spec "Add passwordless sign-in for existing accounts"Plan writes user stories and tasks under the specification, with acceptance criteria and file-level change lists. Plan review adds product, engineering, design, and developer-experience findings.
> /planr:plan
> /plan-reviewShip implements one task in the repository, verifies it, and records it in the provenance log. Plan and ship are separate steps; the agent never chains them on its own.
> /ship