Skip to content

Sprint Planner

Plan the next sprint from your backlog in one pass. Pick a project and a capacity, and the agent proposes a coherent set of tasks; you confirm the selection and it becomes a cycle you can track and close.

Velocity · cycle timePreview
Cycle time
38%
over last 8 cycles
Lead time
4.2d2.6d
median, issue → merge

Every cycle produces a burndown and velocity signal, so the next plan is grounded in how much your team actually shipped.

How it works

  1. Plan. Choose a project and a capacity. The agent reads the backlog and proposes a sprint that fits — no more scrolling the backlog by hand.
  2. Review & confirm. The proposal is a suggestion, not a commitment. Drop tasks you don't want, then create the cycle from your final selection.
  3. Run. The selected tasks are stamped into a cycle with start and end dates, and tracked on the board.
  4. Close. Complete the cycle at the end of the sprint — incomplete work rolls forward cleanly.

Capacity

Tell the planner how much the team can take on. It fits the proposal to whichever limit you give it:

By hours

Give a total capacity in hours and the planner packs the sprint against your tasks' estimates.

By task count

Prefer a simpler cap? Ask for a target number of tasks and the planner proposes that many.

Cycle summary

Each cycle carries a live summary — burndown (work remaining over time) and velocity (what the team completed). Use it in a retro, and to size the next sprint honestly instead of by gut feel.

Closing a cycle

Closing a cycle completes it and handles the leftovers for you. By default, incomplete tasks return to the backlog; or you can roll them straight into the next cycle so nothing gets dropped between sprints.

Team-scoped by design

The planner only ever sees projects that belong to your team. Every project you reference is membership-checked, so a sprint can never pull work from another team's board.

Find it

Open the Sprint Planner at Dashboard → Sprints, or install it from the Agents gallery.

Plan requirement

Sprint planning runs on Lithora AI, so it requires an active Pro or Scaleplan and draws from your team's daily AI message pool (500/day on Pro, 3,000/day on Scale). The check is enforced server-side and resolves from the team owner's plan, so every member of a paid team can use it. Hour-based capacity is only as good as your estimates — see Task management for where estimates live, and Timeline view for whether the cycle is on track once it is running.