Skill · Plan and specify
/sprint$sprint@planr-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. Use before a cut or sprint; not for decomposing one specification or reporting status.
Run it
/sprintin Claude Code. If /sprint runs another command, use /planr:sprint.
$sprintin Codex. With the OpenPlanr plugin for Codex, use $planr:sprint.
@planr-sprintin Cursor. Cursor applies the planr-sprint rule when you mention it in chat.
When to use it
Use it to
- Refine the open backlog and select what fits the next sprint or release cut
- Judge which backlog items are stale, blocked, or ready and fit the sprint to capacity
- Decide which open backlog items move to in progress before the release cut and which are dead
Not for
- Decompose one specification into stories and tasks
- Report delivery status without judging or selecting work
Prompts and commands
Pick the next sprint against the real code
Refine the open backlog and select what fits capacity and the release cut.
Refine the backlog without picking a sprint
Sort open items into stale, blocked, and ready against the current code, with no sprint yet.
Audit the plan for drift
Check that stories, tasks, statuses, and references in the planning folder still agree.