---
title: OpenPlanr Plan
description: Turn a Protocol-compatible specification or product intent into schema-compatible OpenPlanr stories and implementation tasks.
url: https://openplanr.dev/docs/skills/plan
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/skills/plan-review.md
  - https://openplanr.dev/docs/skills/spec.md
  - https://openplanr.dev/docs/skills/sprint.md
---

# OpenPlanr Plan

Skill family: Plan and specify.

Break a specification or a clear request into user stories and tasks, each task with its files, its dependencies, and the checks that prove it is done. Plan stops at the handoff and never starts building.

Turn a Protocol-compatible specification or product intent into schema-compatible OpenPlanr stories and implementation tasks. Use for planning and decomposition, not implementation.

## Run it

- Claude Code: `/planr:plan`
- Codex: `$plan`. With the OpenPlanr plugin for Codex, use $planr:plan.
- Cursor: `@planr-plan`. Cursor applies the planr-plan rule when you mention it in chat.

## Use it to

- Decompose a specification into user stories and implementation tasks
- Create an implementation plan from product intent

## Not for

- Implement the plan
- Review an already written plan

## Example prompt

Claude Code:

```text
/planr:plan SPEC-001
```

Codex:

```text
$plan SPEC-001
```

With the OpenPlanr plugin for Codex, use $planr:plan.

Cursor:

```text
@planr-plan SPEC-001
```

Cursor applies the planr-plan rule when you mention it in chat.

## Output

`.planr/specs/SPEC-001-<slug>/tasks/T-001-<slug>.md`:

```text
---
id: "T-001"
storyId: "US-001"
specId: "SPEC-001"
schemaVersion: "1.7.0"
type: "Tech"
rationale: "<why this task exists>"
dependsOn: []
preserve: []
reviewRisks: []
browserSurfaces: []
acceptanceRefs: ["AC-001"]
---

## Objective
## Files
### Create
### Modify
### Preserve (do not touch)
## Technical Spec
## Test Requirements
## Definition of Done
```

Plan reads the spec, the repository instructions, the relevant code and tests, and any approved design, then writes stories and tasks next to the spec. Every story gets acceptance criteria with stable IDs, and every criterion maps to a task that names it again in its test requirements. A story never gets more than 2 tasks: one Tech task, or one UI task and one Tech task when it has a design surface.

It validates the frontmatter and the acceptance coverage, then hands you the next ready task and the exact command to build it. See [Plan a feature](https://openplanr.dev/docs/guides/plan.md).