> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oktolabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sprint

> How Pulse groups spec-derived work into an executable sprint.

# Sprint

You can use a sprint to group validated spec work into a bounded delivery slice. In Pulse, the sprint is the bridge between a spec and the cards an implementation agent will pick up.

## What is a sprint

A sprint contains cards, assignment context, coverage settings, qualitative evaluation, and lifecycle status. It does not replace a spec; it selects a portion of spec work and makes it executable.

## States

| State       | Meaning                                          |
| ----------- | ------------------------------------------------ |
| `draft`     | The sprint exists but has not started.           |
| `active`    | Cards can be assigned and worked.                |
| `review`    | The sprint is ready for evaluation and closeout. |
| `closed`    | Sprint delivery is complete.                     |
| `cancelled` | Sprint should stop.                              |

## Sprint evaluation gate

Sprint evaluation is a retrospective checkpoint, not the same as spec validation or task validation. It captures delivery quality, coverage, and lessons before closeout.

```text theme={null}
okto_pulse_get_sprint_evaluation
okto_pulse_submit_sprint_evaluation
```

## Suggesting sprints from a spec

`okto_pulse_suggest_sprints` groups spec work into sprint-sized chunks. Use it after the spec is mature enough that cards can be estimated and grouped.

## Assigning cards to a sprint

Cards can be assigned to a sprint after the sprint is created. Keep a sprint focused: a broad catch-all sprint makes validation and status reporting harder.

```text theme={null}
okto_pulse_assign_tasks_to_sprint
```

## Related pages

* [Spec](/concepts/spec)
* [Cards](/concepts/card)
* [Sprints and cards tools](/reference/mcp/sprints-cards)
* [Sprint flags](/permissions/sprint)