Open source · Claude Code, Codex, Cursor

Close the loop from intent to delivery.

Turn an idea or a PRD into specs, user stories and agent-ready tasks with exact file scope and a testable Definition of Done.

Plan. Design. Build. Review. Operate.

Set up OpenPlanr in this repo: https://openplanr.dev/setup.md

Plan: a typed /spec command becomes SPEC-001, which splits into user stories and tasks saved as files under .planr/ in the repo.

// How it works

Plans are files.
The agent reads them first.

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.

  1. Specify
    Shape a request into a clear, measurable specification grounded in the current repository.
    /spec
  2. Plan
    Write user stories and tasks under the specification, with acceptance criteria and file-level change lists.
    /planr:plan
  3. Ship
    Implement one task in the repository, verify it, and record it in the provenance log.
    /ship
  4. Validate and sync
    The deterministic OpenPlanr CLI validates what the agent wrote, renders it, and keeps GitHub Issues or Linear in step.
    openplanr sync · openplanr status
// Capabilities

Plan. Design. Build.
Review. Operate.

Every step is a skill the agent selects from its description, or that you invoke by name. The open toolkit needs no account.

  • Plan and specify
    Shape intent into a measurable specification, decompose it into stories and tasks, review the plan, and refine the backlog into a sprint.
    spec · plan · plan-review · sprint
  • Implement
    Implement a plan, specification, or task end to end in the current repository, with frontend, backend, database, QA, DevOps, and documentation roles.
    ship
  • Review and QA
    Run browser-backed QA against real routes, forms, viewports, accessibility, console, and network behavior.
    browser-qa
  • Design
    Design an interface in a shared canvas, prototype, and walkthrough studio, compare three directions, and review with stable board pins.
    design · design-loop · design-review
  • Diagrams
    Create, inspect, verify, or rerender offline diagrams across 39 grammars, from architecture and sequence to ER, Gantt, and Wardley.
    $openplanr diagram render
  • Artifact reviews
    Open, share, import, or export an HTML artifact review, so feedback moves between a local artifact and its review board.
    artifact
  • Land and release
    Assess release readiness before merge, then choose a versioning scheme, classify shipped changes, and write release notes.
    land · release
  • Setup and diagnostics
    Diagnose CLI, pipeline, and installation health, and investigate a bug to its root cause with an optional bounded fix.
    $openplanr doctor
  • Status, routing, and sync
    See what is done, pending, or blocked, audit planning files for drift, open the local dashboard, and route a request to the best skill.
    $openplanr status · openplanr sync
  • Operate
    Run an operating review across seven executive lenses (CEO, CTO, CPO, CMO, COO, challenger, and chair) and produce a decision and action brief.
    $openplanr operate

Browse all 25+ skills in the catalog →

// Hosts

Works with the agents
you already use

Every skill runs inside the coding agent you already use. One command installs them for each host.

Claude Code
/<skill>
The OpenPlanr plugin, with 9 role agents. Plan, design, status, and doctor keep the /planr: prefix.
$openplanr setup --runtime claude --scope user
Codex
$<skill>
Bare-named skills, or the unified plugin ($planr:<skill>) with --skill-mode unified-plugin.
$openplanr setup --runtime codex --scope user
Cursor
planr-<skill> rule
One project rule per skill under .cursor/rules/, mentioned in Composer.
$openplanr setup --runtime cursor --scope project
// Two layers

Open-source local workflows.
Governed collaboration for companies.

MIT licensed

Open-source local workflows

The planr CLI, the Protocol contracts, the host-native skills, deterministic validation and rendering, and the local dashboard and review studios.

The open toolkit needs no account.

Under validation · not generally available

Governed collaboration for companies

Company workspaces are a separately operated service for teams that want shared artifact revisions, review workflows, and organization and project access around the same planning files.

Company workspaces are deployed and under validation; they are not generally available.

How the open source and the hosted service relate →
Packages

One repository. Three npm packages.

One canonical skill graph is generated into host-native projections for Claude Code, Codex, and Cursor. Generated files are outputs, never sources.

CLI and host packagesv2.2641.2

openplanr

binary: 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.

openplanr setupopenplanr initopenplanr diagramopenplanr doctor
Runs as · Terminalnpm install -g openplanr
Delivery pipelinev0.57.0

planr-pipeline

exact optional dependency of openplanr

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.

ProtocolOperate runtimeartifact review
Runs as · Skillsinstalled by openplanr setup
Schemas and registriesv0.10.3

@openplanr/protocol

MIT-licensed contracts

Public contracts for OpenPlanr local tools and hosted consumers: JSON schemas, canonical registries, and browser-safe schema validation.

schemas/registries/schema validation
Runs as · Integrationsnpm i @openplanr/protocol

Continue exploring OpenPlanr

Read the full blueprint →Read the docs →

Built with itself.

The diagrams in OpenPlanr's README are rendered by openplanr diagram render from canonical documents and verified in CI by openplanr diagram check.

Give your AI agent
the full picture.

Open source. MIT licensed.

$ npm install -g openplanr

Requires Node.js 20.19+, 22.13+, or 23.5+. Then follow 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)
TypeScriptNode.jsCommander.jsHandlebarsZodBiome