openplanr
Stores and validates planning files, renders diagrams and reports, installs the skills into each host, diagnoses installations, and syncs with GitHub Issues and Linear.
Your agent writes the code. OpenPlanr is the open harness around it.Plans as files in your repo, checks before you merge, and a record of what shipped.
Plan. Ship and verify. Operate.
Install the Claude Code plugin → Or choose individual skills below.
npx skills add openplanr/OpenPlanr




Plan: a typed /spec command becomes SPEC-001, which splits into user stories and tasks saved as files under .planr/ in the repo.
Specifications, user stories, tasks, and provenance live under .planr/ in your repository, reviewed and versioned like code. Plan and ship stay separate steps that you invoke.
Every step is a skill the agent selects from its description, or that you invoke by name. The open toolkit needs no account.
Install the plugin or skills in the coding agent you already use. Add the companion CLI when a workflow needs it.
>/plugin marketplace add openplanr/marketplace
/plugin install planr@openplanr$npx skills add openplanr/OpenPlanr$npx skills add openplanr/OpenPlanrOne 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.
The diagrams in OpenPlanr's README are rendered by openplanr diagram render from canonical documents and verified in CI by openplanr diagram check.
Open source. MIT licensed.
Choose skills and destinations in your terminal. Requires Node.js 22.20+. For the plugin, see the getting started guide.
Reply in the beta thread with one feature you'd plan first.
Join the beta (opens GitHub in a new tab)