OpenPlanr overview
What OpenPlanr is, how its plan, design, build, review, and operate loop works, and where to start in Claude Code, Codex, or Cursor.
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. Install the plugin or skills in your coding agent, then add the companion CLI when a workflow needs it.
Plan. Ship and verify. Operate.
What it is
- Skills in your agent. Ordinary skills run in your current coding agent. The optional
delegateworkflow can hand an explicitly requested implementation to another coding agent. - Plans are files. Specifications, user stories, tasks, and provenance live under
.planr/in your repository, reviewed and versioned like code. See Plans are files. - A companion CLI.
openplanrstores and validates planning files, renders diagrams and reports, installs the skills into each agent, diagnoses installations, and syncs with GitHub Issues and Linear. - Open source under MIT. One repository, published as 3 npm packages:
openplanr(the CLI and host packages),planr-pipeline(the delivery pipeline), and@openplanr/protocol(schemas and registries).
OpenPlanr is not a hosted project tracker and does not replace your issue tracker. It closes the loop: your agent reads the plan before it changes code, and what it ships flows back as evidence for the next review.
How it works
Reasoning stays in your agent. Planning validation and diagram rendering are deterministic local operations provided by the companion CLI.
Every step is a skill your agent selects from its description, or one you invoke by name:
| Stage | What you get | Guide |
|---|---|---|
| Plan | A spec with measurable acceptance criteria, then user stories and tasks with exact file scope | Plan a feature |
| Design | One design direction in a review studio, and a design spec that Plan reads | Design before you build |
| Build | One task at a time, verified and small enough to review as one pull request | Build one task at a time |
| Review | A plan review before building, browser QA after it, and a readiness check before merge | Review before it lands |
| Operate | Delivery status from the plan, and leadership reviews that end in decisions | Track delivery and run operating reviews |
Plan and ship stay separate steps that you invoke. The agent never chains them on its own.
Start here
- Install the plugin or skills. Use the Claude Code marketplace, or run
npx skills add openplanr/OpenPlanrin your project to choose skills and a host. - Choose the workflow your request needs: Ship for a clear change, Investigate for a bug, Design for an interface, or Operate for an operating review. Write a spec when the requirements need clarification.
- Read the page for your agent: Claude Code, Codex, or Cursor.
- Copy a prompt from the prompt library, starting with the ones marked Start here.