Sprints
{"content":"Sprints group tasks into time-boxed delivery cycles. Use them to scope work, track completion, and close out phases with a clear record of what shipped and who did it.\n\n## Sprint list\n\n{{\u003c thumbcard src=\"/images/ui/sprints/sprints-list.png\" alt=\"Sprint list showing status filters, story points, and task counts\" caption=\"Sprint list with status summary bar and sortable table\" \u003e}}\n\nThe sprint list gives you the full inventory at a glance:\n\n- **Status summary bar:** Planned, Active, In Review, and Closed counts across all sprints. Click a status to filter the table to just that group.\n- **Health indicators:** completion percentage, total story points, and at-risk count at the top left.\n- **Sortable columns:** Name, Status, Timeline, Project, Story Points, and Tasks. Click any header to sort.\n- **Search:** filter by sprint name, project, or status using the search box.\n\n{{% steps %}}\n\n### Step 1 — Filter by status\n\nUse the status buttons (Planned, Active, In Review, Closed) at the top to narrow the table. This is the fastest way to find what's in flight or recently closed.\n\n### Step 2 — Open a sprint\n\nClick any row to open the sprint detail view. You'll see the full task backlog, completion metrics, and team info.\n\n### Step 3 — Add a sprint\n\nClick the **+** button to create a new sprint. Sprints are linked to a project and get a timeline, goal, and task list.\n\n{{% /steps %}}\n\n\u003e [!TIP]\n\u003e Sprints can also be created via MCP or through the [Orchestrator](../orchestrator/) — Skadi creates sprints automatically as part of plan execution.\n\n## Sprint detail\n\n{{\u003c thumbcard src=\"/images/ui/sprints/sprint-detail.png\" alt=\"Sprint detail showing header, story points, task completion, and status badge\" caption=\"Sprint detail — header with story points, completion bar, and status\" \u003e}}\n\nOpening a sprint shows the delivery state for that cycle:\n\n- **Header:** sprint name, description, timeline with duration, completion status, and task count.\n- **Status badge:** current lifecycle state (Planned → Active → In Review → Closed). Click to transition.\n- **Story points card:** total points and a completion progress bar with percentage.\n\n### Task backlog and status distribution\n\n{{\u003c thumbcard src=\"/images/ui/sprints/sprint-overview.png\" alt=\"Sprint overview showing task backlog table alongside donut chart with status breakdown\" caption=\"Task backlog with status distribution — all four tasks Done (100%)\" \u003e}}\n\nThe overview tab centers on the sprint's task table alongside a live status distribution chart:\n\n- **Key:** task identifier that links to the task detail view.\n- **Title:** what the task covers.\n- **Status:** individual task status (Backlog, To Do, In Progress, In Review, Verified, Done).\n- **Points:** story point estimate for the task.\n- **Assignee:** the agent or person assigned to the task.\n- **Actions:** remove a task from the sprint without deleting it.\n\nThe **donut chart** on the right breaks down task status across six categories. Use it to quickly see how much is done vs. still in progress. Each status label is clickable — it filters the task table to that status.\n\nUse the **+** button above the table to add existing tasks to the sprint, or the filter box to search within the backlog.\n\n### Metadata tab\n\nThe Metadata tab holds supporting context — notes, team owners, reference links, and a danger zone for deletion. Tasks linked to a deleted sprint are preserved and become unscheduled.\n\n## Sprint lifecycle\n\nSprints move through four states:\n\n| Status | Meaning |\n|--------|---------|\n| **Planned** | Sprint is defined with a goal and timeline but work hasn't started. |\n| **Active** | Work is underway. Tasks are being assigned and completed. |\n| **In Review** | The sprint is being reviewed before closing. Inspect its tasks to confirm what remains. |\n| **Closed** | The sprint has been marked complete. Its record remains editable. |\n\nChange status by clicking the status badge in the sprint detail header. The status summary bar on the list view updates immediately.\n\nBefore changing the status to **Closed**, check that the sprint’s tasks are complete. To make that check part of the process, use the included sprint-closeout workflow, which requires its expected tasks to be done.\n\n## Navigation tips\n\n- Use the breadcrumb (`SPRINTS`) to return to the list from any detail view.\n- The sprint list respects URL parameters (e.g., `?status=closed`) so you can bookmark filtered views.\n- From the [Dashboard](/valdr/docs/ui/dashboard/), the Sprint Health perspective links directly into the sprint list filtered by recent closes.\n\n## Next steps\n\n- Use [Tasks](/valdr/docs/ui/tasks/) to create and estimate work before adding it to a sprint.\n- Use the [Planner](/valdr/docs/ui/planner/) to generate tasks from a plan, then group them into sprints.\n- See [Build Your Own Workflow](/valdr/docs/getting-started/workflows/) to understand how orchestrators like Skadi automate sprint creation and task routing.","description":"Plan, track, and close time-boxed delivery cycles with full task visibility.","title":"Sprints"}
Sprints group tasks into time-boxed delivery cycles. Use them to scope work, track completion, and close out phases with a clear record of what shipped and who did it.
Sprint list
Sprint list with status summary bar and sortable table
The sprint list gives you the full inventory at a glance:
- Status summary bar: Planned, Active, In Review, and Closed counts across all sprints. Click a status to filter the table to just that group.
- Health indicators: completion percentage, total story points, and at-risk count at the top left.
- Sortable columns: Name, Status, Timeline, Project, Story Points, and Tasks. Click any header to sort.
- Search: filter by sprint name, project, or status using the search box.
Step 1 — Filter by status
Use the status buttons (Planned, Active, In Review, Closed) at the top to narrow the table. This is the fastest way to find what’s in flight or recently closed.
Step 2 — Open a sprint
Click any row to open the sprint detail view. You’ll see the full task backlog, completion metrics, and team info.
Step 3 — Add a sprint
Click the + button to create a new sprint. Sprints are linked to a project and get a timeline, goal, and task list.
Tip
Sprints can also be created via MCP or through the Orchestrator — Skadi creates sprints automatically as part of plan execution.
Sprint detail
Sprint detail — header with story points, completion bar, and status
Opening a sprint shows the delivery state for that cycle:
- Header: sprint name, description, timeline with duration, completion status, and task count.
- Status badge: current lifecycle state (Planned → Active → In Review → Closed). Click to transition.
- Story points card: total points and a completion progress bar with percentage.
Task backlog and status distribution
Task backlog with status distribution — all four tasks Done (100%)
The overview tab centers on the sprint’s task table alongside a live status distribution chart:
- Key: task identifier that links to the task detail view.
- Title: what the task covers.
- Status: individual task status (Backlog, To Do, In Progress, In Review, Verified, Done).
- Points: story point estimate for the task.
- Assignee: the agent or person assigned to the task.
- Actions: remove a task from the sprint without deleting it.
The donut chart on the right breaks down task status across six categories. Use it to quickly see how much is done vs. still in progress. Each status label is clickable — it filters the task table to that status.
Use the + button above the table to add existing tasks to the sprint, or the filter box to search within the backlog.
Metadata tab
The Metadata tab holds supporting context — notes, team owners, reference links, and a danger zone for deletion. Tasks linked to a deleted sprint are preserved and become unscheduled.
Sprint lifecycle
Sprints move through four states:
| Status | Meaning |
|---|---|
| Planned | Sprint is defined with a goal and timeline but work hasn’t started. |
| Active | Work is underway. Tasks are being assigned and completed. |
| In Review | The sprint is being reviewed before closing. Inspect its tasks to confirm what remains. |
| Closed | The sprint has been marked complete. Its record remains editable. |
Change status by clicking the status badge in the sprint detail header. The status summary bar on the list view updates immediately.
Before changing the status to Closed, check that the sprint’s tasks are complete. To make that check part of the process, use the included sprint-closeout workflow, which requires its expected tasks to be done.
Navigation tips
- Use the breadcrumb (
SPRINTS) to return to the list from any detail view. - The sprint list respects URL parameters (e.g.,
?status=closed) so you can bookmark filtered views. - From the Dashboard, the Sprint Health perspective links directly into the sprint list filtered by recent closes.
Next steps
- Use Tasks to create and estimate work before adding it to a sprint.
- Use the Planner to generate tasks from a plan, then group them into sprints.
- See Build Your Own Workflow to understand how orchestrators like Skadi automate sprint creation and task routing.