Beta: try OpenPlanr on one real feature and tell us where it broke

[AsemDevs]

OpenPlanr closes the loop from intent to delivery. Plans are files: specifications, user stories and tasks live under .planr/ in your repository, reviewed and versioned like code. Every skill runs inside the coding agent you already use, and the agent reads the plan before it changes code.

It's 25+ skills for Claude Code, Codex and Cursor, plus the deterministic planr CLI. MIT licensed.

Start here: reply below with one feature you'd plan first. One line is enough.

This thread is the beta: try it on one real feature and tell us where it broke. Overview and install: openplanr.dev

Who this is for

You hand work to Claude Code, Codex or Cursor on a real codebase, and you're a technical founder, an engineering lead, or a design or product person working next to them.

What to try first

The getting started guide takes about five minutes to a first specification.

1. Install the CLI and the skills for your agent:

   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

2. Restart the agent, then in your project:

   planr init

3. Pick a feature you were going to build anyway, and write the specification:

   /planr:spec "<your feature>"     # Claude Code
   $planr:spec "<your feature>"     # Codex
   

   In Cursor, mention the planr-spec rule in Composer.

4. Run plan to turn the specification into stories and tasks, then ship to implement one task. Plan and ship stay separate steps that you invoke.

What feedback helps

Reply here, or start a thread in Beta feedback, with:

• Host: Claude Code, Codex or Cursor, and its version
• planr --version
• Did the first plan work? Yes, partly, or no
• Where it broke: the command or skill you ran, what you expected, and what happened
• Files: which files under .planr/ it wrote or changed
• planr doctor --json if setup or a skill failed. It redacts secrets, but check it before you paste.
• What's missing before you'd use it on your next feature

A bug with a clear reproduction can also go through the issue forms. Security reports never go here: follow SECURITY.md.

What you get

• Reports with a reproduction and planr doctor output are triaged first.

Please keep it public-safe

This thread is public. Don't paste private code, secrets or customer data. We keep a list of beta participants by public handle only.

What this isn't

This beta covers the open local toolkit. The hosted company workspace is deployed and under validation; it isn't generally available.

Asem