---
title: Break a spec into stories and tasks
description: Get user stories and tasks with acceptance criteria and file-level changes.
url: https://openplanr.dev/docs/prompts/plan-a-spec
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/plan-from-intent.md
  - https://openplanr.dev/docs/prompts/plan-ui-from-design.md
  - https://openplanr.dev/docs/prompts/audit-plan-drift.md
---

# Break a spec into stories and tasks

Get user stories and tasks with acceptance criteria and file-level changes.

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

Parts to fill in, shown with their example text:

- The spec to plan: SPEC-001

## Why this works

Plan reads the saved spec, so every story keeps its acceptance criteria and every task names its files, its dependencies, and the checks that prove it is done. It stops after the plan and never starts building on its own.

## Make it stick

[Plan a feature](https://openplanr.dev/docs/guides/plan.md)