Skip to content
OpenPlanr Docs
GitHub (opens in a new tab)

Skill · Plan and specify

/planr:plan

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.

Run it
/planr:plan

in Claude Code

What it does

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

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.

When to use it

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

/planr:plan SPEC-001

What you get

.planr/specs/SPEC-001-<slug>/tasks/T-001-<slug>.md
---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
An excerpt of the file the skill writes.

Prompts and commands

Related CLI commands

Next in the loop

/sprint

Refine every open backlog item against the code and the calendar, refute the picks, and select a sprint that fits capacity and the release cut.

OpenPlanr Docs
Commands for
Theme