Prompt · Plan
Pick the next sprint against the real code
Refine the open backlog and select what fits capacity and the release cut.
/sprint two weeks, two engineers, release cut on the 23rd$sprint two weeks, two engineers, release cut on the 23rd@planr-sprint two weeks, two engineers, release cut on the 23rdIf /sprint runs another command, use /planr:sprint.
With the OpenPlanr plugin for Codex, use $planr:sprint.
Cursor applies the planr-sprint rule when you mention it in chat.
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.
Related prompts
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.
Pin down acceptance criteria before planning
Turn loose requirements into observable criteria with stable IDs before anyone plans the work.