---
title: OpenPlanr Blueprint
description: How OpenPlanr closes the loop - three npm packages, nine role agents, and the getting started steps for Claude Code, Codex and Cursor.
url: https://openplanr.dev/blueprint
updated: 2026-11-19
related: []
---

# How OpenPlanr closes the loop.

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

- `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.
- `planr-pipeline`: the delivery pipeline (PO, design, review, implementation, QA and delivery outputs), an exact optional dependency of `openplanr`, installed by `openplanr setup`.
- `@openplanr/protocol`: public contracts for OpenPlanr local tools and hosted consumers: JSON schemas, canonical registries and browser-safe schema validation.

## Nine role agents. Two skills. One human gate.

Each role agent's manifest lists the only tools it may use.

- `/planr:plan` decomposes a specification with `planr-database` (read-only schema introspection), `planr-designer` (mockups to a design spec) and `planr-specification` (user stories and tasks).
- Human gate: you review the plan, then invoke ship. The agent never chains plan and ship on its own.
- `/ship` implements with `planr-frontend` and `planr-backend` in parallel, then `planr-qa` reviews without editing, and `planr-devops` and `planr-documentation` handle configuration and docs.
- `planr-entity-scaffold` generates ORM entities from the scanned schema.

## From an empty terminal to one shipped task.

In Claude Code, use its marketplace:

```text
/plugin marketplace add openplanr/marketplace
/plugin install planr@openplanr
```

For individual skills, run this from your project in a normal terminal:

```bash
npx skills add openplanr/OpenPlanr
```

Choose skills, destination hosts, and Project or Global scope. Project scope is the default. Restart your host and select the installed skill: plugin names use `planr:ship`, while source skill names use `planr-ship`.

Start with Ship for a clear change or Operate for an operating review. A feature that needs clarification can start with Spec, then Plan and plan review before Ship.

Add `npm install -g openplanr` when a workflow needs diagram rendering, a local studio, planning validation, diagnostics, or integrations. For structured planning, `openplanr init` creates `.planr/config.json` and the artifact directories in your project.

The full guide: https://openplanr.dev/docs/get-started/install.md
