---
title: Pin down acceptance criteria before planning
description: Turn loose requirements into observable criteria with stable IDs before anyone plans the work.
url: https://openplanr.dev/docs/prompts/clarify-acceptance-criteria
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/spec-from-idea.md
  - https://openplanr.dev/docs/prompts/audit-plan-drift.md
  - https://openplanr.dev/docs/prompts/pick-the-sprint.md
---

# Pin down acceptance criteria before planning

Turn loose requirements into observable criteria with stable IDs before anyone plans the work.

## Prompt

Claude Code:

```text
/spec Clarify the requirements and acceptance criteria for team invitations by email before we plan it.
```

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

Codex:

```text
$spec Clarify the requirements and acceptance criteria for team invitations by email before we plan it.
```

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

Cursor:

```text
@planr-spec Clarify the requirements and acceptance criteria for team invitations by email before we plan it.
```

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

Parts to fill in, shown with their example text:

- The feature: team invitations by email

## Why this works

Spec writes requirements and acceptance criteria that can be observed, each criterion with a stable AC-NNN ID. Plan later maps every ID to a task and to a check in that task's test requirements.

## Make it stick

[Write your first spec](https://openplanr.dev/docs/get-started/first-spec.md)