---
title: OpenPlanr Spec
description: Shape vague product or engineering intent into a clear, measurable Protocol-compatible specification grounded in the current repository.
url: https://openplanr.dev/docs/skills/spec
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/skills/plan.md
  - https://openplanr.dev/docs/skills/plan-review.md
  - https://openplanr.dev/docs/skills/sprint.md
---

# OpenPlanr Spec

Skill family: Plan and specify.

Turn a vague product or engineering idea into a clear, measurable specification grounded in your repository, before anyone plans or builds.

Shape vague product or engineering intent into a clear, measurable Protocol-compatible specification grounded in the current repository. Use when requirements need clarification before planning or implementation.

## Run it

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

## Use it to

- Turn vague product or engineering intent into a precise specification
- Clarify requirements and acceptance criteria before planning

## Not for

- Implement an existing specification
- Return project status

## Example prompt

Claude Code:

```text
/spec add passwordless sign-in for existing accounts. Users drop off at the password step.
```

If /spec runs another command, use /planr:spec.

Codex:

```text
$spec add passwordless sign-in for existing accounts. Users drop off at the password step.
```

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

Cursor:

```text
@planr-spec add passwordless sign-in for existing accounts. Users drop off at the password step.
```

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

## Output

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

```text
---
id: "SPEC-001"
title: "<title>"
slug: "<slug>"
schemaVersion: "1.7.0"
---

## Context & Goal
## Audience
## Outcome & Measurement
## Functional Requirements
## Business Rules
## Constraints
## Evidence Expectations
## Failure Modes
## Rollback
## Scope Boundaries
## Acceptance Criteria
## Declared Risk Specialists
## Notes for Decomposition
```

The skill reads your request, the repository instructions, existing plans, and the relevant code and tests. When a missing decision would change the scope or the behavior, it asks you, at most 3 short questions at a time, with the recommended option first. Then it writes one specification whose requirements and acceptance criteria are observable, each criterion with a stable ID.

The sections follow the specification contract the skill ships with. The reply links the saved file and ends with the exact command to plan the spec next. Walk through it in [Write your first spec](https://openplanr.dev/docs/get-started/first-spec.md).