OpenPlanr

Close the loop from intent to delivery.

OpenPlanr is the shared delivery loop for product teams and their AI agents.
Plan, design, build, review, and operate from durable context in your repository:
27 skills for Claude Code, Codex, and Cursor, plus the deterministic planr CLI.

Getting started · Skills · CLI reference · Architecture · Support

What it is

• Skills, not a second model. Every skill runs inside the coding agent you already use.
  OpenPlanr adds no model calls, API keys, or telemetry.
• Plans are files. Specifications, user stories, tasks, and provenance live under .planr/
  in your repository, reviewed and versioned like code.
• A deterministic CLI. planr stores and validates planning files, renders diagrams and
  reports, installs the skills into each host, diagnoses installations, and syncs with GitHub
  Issues and Linear.
• One repository, MIT licensed. Three 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: the agent reads the plan before it changes code, and what it ships flows back as evidence
for the next review.

Quick start

npm install -g openplanr

planr setup --runtime claude --scope user
# Codex:  planr setup --runtime codex --scope user --skill-mode unified-plugin
# Cursor: planr setup --runtime cursor --scope project
cd your-project
planr init

Restart the coding agent so it loads the new skills, then start with a specification:

/planr:spec "Add passwordless sign-in for existing accounts"     # Claude Code
$planr:spec "Add passwordless sign-in for existing accounts"     # Codex

In Cursor, mention the planr-spec rule in Composer. Follow with plan to decompose the
specification into stories and tasks, and ship to implement one task. Plan and ship stay
separate steps that you invoke.

Alternatives: npx openplanr@latest setup without a global install, or
curl -fsSL https://openplanr.dev/install.sh | sh (irm https://openplanr.dev/install.ps1 | iex
on Windows). OpenPlanr requires Node.js 20 or later. The
getting started guide covers scopes, what setup writes, and how to
undo it.

How it works

%%{init: {"theme":"base","themeVariables":{"fontFamily":"DM Sans, ui-sans-serif, system-ui, sans-serif","fontSize":"14px","primaryColor":"#5EEAD4","primaryTextColor":"#08080C","primaryBorderColor":"#237A72","secondaryColor":"#F5F7F7","secondaryTextColor":"#08080C","secondaryBorderColor":"#237A72","tertiaryColor":"#F5F7F7","tertiaryTextColor":"#08080C","tertiaryBorderColor":"#237A72","lineColor":"#237A72","textColor":"#08080C","edgeLabelBackground":"#F5F7F7","clusterBkg":"#F5F7F7","clusterBorder":"#237A72","noteBkgColor":"#F5F7F7","noteTextColor":"#08080C","noteBorderColor":"#237A72"}}}%%
flowchart LR
    request["Request<br/><i>a feature, bug, or question</i>"]
    subgraph host["Your coding agent · Claude Code, Codex, Cursor"]
        direction LR
        spec["planr-spec<br/>specification"] --> plan["planr-plan<br/>stories and tasks"] --> ship["planr-ship<br/>implementation"]
    end
    subgraph repo["Your repository"]
        direction LR
        files[".planr/<br/>specs · stories · tasks<br/>provenance log"]
        code["Source code<br/>and tests"]
    end
    cli["planr CLI<br/>validate · render<br/>sync · doctor"]
    trackers["GitHub Issues · Linear<br/><i>optional</i>"]
    request --> spec
    spec --> files
    plan --> files
    files --> ship
    ship --> code
    files <--> cli
    cli <--> trackers

Reasoning stays in the host agent. The CLI never calls a model; it validates what the agent
wrote, renders it, and keeps trackers in step.

Capabilities

Plan. Design. Build. Review. Operate. Every step is a skill the agent selects from its
description, or that you invoke by name.

Invoke a skill as /planr:<skill> in Claude Code or $planr:<skill> in Codex; in Cursor,
mention the planr-<skill> rule. The skill catalog is generated from
the registry and lists every trigger, deferral, and packaged reference.

Diagram engine

_{Rendered by planr diagram render from a canonical document; verified in CI by planr diagram check. The engine ships one light theme today.}

planr-diagram turns intent into a canonical semantic document, and the offline engine lays
it out deterministically across 39 grammars (architecture, sequence, ER, Gantt, story map,
Wardley, and more). Every render produces SVG, PNG, accessible HTML, quality and fidelity
reports, and a manifest that binds the set.

planr diagram gallery                                          # list grammars
planr diagram render ./architecture.planr-diagram.json --json  # render a set
planr diagram check ./diagrams/architecture/architecture.manifest.json --json

See authoring and verifying diagrams.

Hosts

planr rules generate adds an ## OpenPlanr capabilities section to CLAUDE.md or AGENTS.md
so the agent knows every skill and when to reach for it. See the
host matrix for what each projection may and may not change.

Architecture

%%{init: {"theme":"base","themeVariables":{"fontFamily":"DM Sans, ui-sans-serif, system-ui, sans-serif","fontSize":"14px","primaryColor":"#5EEAD4","primaryTextColor":"#08080C","primaryBorderColor":"#237A72","secondaryColor":"#F5F7F7","secondaryTextColor":"#08080C","secondaryBorderColor":"#237A72","tertiaryColor":"#F5F7F7","tertiaryTextColor":"#08080C","tertiaryBorderColor":"#237A72","lineColor":"#237A72","textColor":"#08080C","edgeLabelBackground":"#F5F7F7","clusterBkg":"#F5F7F7","clusterBorder":"#237A72","noteBkgColor":"#F5F7F7","noteTextColor":"#08080C","noteBorderColor":"#237A72"}}}%%
flowchart LR
    subgraph sources["Canonical sources"]
        direction TB
        skills["skills/ · agents/"]
        protocol["@openplanr/protocol<br/>schemas · registries"]
    end
    generate(["npm run generate"])
    subgraph packages["Published packages"]
        direction TB
        cli["openplanr<br/>planr CLI + host packages"]
        pipeline["planr-pipeline<br/>delivery pipeline"]
    end
    subgraph hosts["Installed into hosts"]
        direction TB
        claude["Claude Code plugin"]
        codex["Codex plugin"]
        cursor["Cursor rules"]
    end
    skills --> generate
    protocol --> generate
    generate --> cli
    generate --> pipeline
    protocol --> pipeline
    pipeline -. exact optional dependency .-> cli
    cli --> claude
    cli --> codex
    cli --> cursor

One canonical skill graph is generated into host-native projections; generated files are
outputs, never sources. The CLI composes five command groups (foundation, planning, delivery,
operations, intelligence) over the Protocol contracts, and internal workspaces (operate,
artifact, design, skill-runtime, the dashboard) are projected into the public packages at
generation time. See the architecture guide.

Documentation

Use
Getting started ·
Skill catalog ·
CLI reference ·
Troubleshooting ·
Diagrams

Contribute
Contributing ·
Architecture ·
Working from a checkout ·
Skill authoring ·
Releasing

Integrate
Protocol package ·
Pipeline package ·
Host matrix ·
Skill versioning ·
Verifying a release

Community and license

Ask questions and share what you built in
Discussions; report bugs through the
issue forms. SUPPORT.md
explains what to include. Security reports follow SECURITY.md; participation
follows the code of conduct.

OpenPlanr is MIT licensed. The name and logo are covered by the
trademark policy; the boundary between this repository and the hosted service
is described in COMMERCIAL.md. Maintained by
Asem Abdo and contributors.