---
title: Pick the next sprint against the real code
description: Refine the open backlog and select what fits capacity and the release cut.
url: https://openplanr.dev/docs/prompts/pick-the-sprint
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/refine-the-backlog.md
  - https://openplanr.dev/docs/prompts/audit-plan-drift.md
  - https://openplanr.dev/docs/prompts/clarify-acceptance-criteria.md
---

# Pick the next sprint against the real code

Refine the open backlog and select what fits capacity and the release cut.

## Prompt

Claude Code:

```text
/sprint two weeks, two engineers, release cut on the 23rd
```

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

Codex:

```text
$sprint two weeks, two engineers, release cut on the 23rd
```

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

Cursor:

```text
@planr-sprint two weeks, two engineers, release cut on the 23rd
```

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

Parts to fill in, shown with their example text:

- Capacity and the release cut: two weeks, two engineers, release cut on the 23rd

## Why this works

Sprint reads every open item against the code and the calendar, tests its picks, and fits the survivors to your capacity and the next cut. Putting capacity in the prompt saves a question: the skill asks only for what the repository cannot answer.

## Make it stick

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