Sprint Board
Prov1.0.0A four-column sprint board with WIP limits, card moves, progress and quick task entry.
Build for your project
Code/install build
Usage
Import it and pass your content. The props that matter most are listed next.
Example
import { SprintBoard, type SprintTask } from "@/components/ui/notchset/blocks/sprint-board";
export function Board({ tasks }: { tasks: SprintTask[] }) {
return (
<SprintBoard
label="SPRINT 41"
title="Ship v15"
tasks={tasks}
people={{ MK: { name: "Maya Kerr", me: true } }}
onMove={(task, to) => fetch(`/api/tasks/${task.id}`, { method: "PATCH", body: JSON.stringify({ column: to }) })}
/>
);
}Props
tasks–{ id, area, title, due, assignee, comments, column, description }[]column is "planned", "progress", "review" or "done"; due "TODAY" shows in signal.
people–Record<initials, { name, me? }>The team; `me` adds ALL / MY WORK.
label / title / daysLeft–stringThe header and the time left.
wipLimit–numberCards allowed in IN PROGRESS (default 3).
onMove / onAdd–(task, to) => void / (title) => Promise<task>Persist moves; create tasks on your server (defaults to a local task).
Anatomy
- Moves apply at once; onMove persists them.
- MY WORK filters to the person marked me.
- The WIP limit counts every card in IN PROGRESS, whoever owns it.
SprintBoarddata-slot="sprint-board"Header, progress, the four columns and the status line.
Source
components/ui/notchset/blocks/sprint-board.tsx
This component is included with Pro.
Try the live preview above. Get Pro to install the source.
Build for your project
Code/install build
Installation
pnpm dlx shadcn@latest add @beautiful-ui-pro/sprint-boardNeeds your registry key. Your components.json style picks the Base UI or Radix build: radix-*, new-york and default get Radix, base-* gets Base UI.
Styles didn't apply?
The CLI adds the styles to the CSS file named in components.json (tailwind.css). Check that it points at your global stylesheet, that the project uses Tailwind CSS v4, and that the file is imported in your root layout. Installed by hand: paste styles.css into that file.
For coding agents
Give your coding assistant the Markdown guide instead of screenshots.
Use it for
- A team's sprint or project board
- Boards where a work-in-progress limit should be enforced
Use something else when
- Hundreds of cards: use a table with filters
- Free-form drag and drop across many lanes: use a dedicated board library
Mistakes to avoid
- Enforce the WIP limit on the server too
- Keep areas short; they truncate before the due date does
Agents find it by
- kanban, sprint board, task board, scrum board, wip limit, project board, todo board, Notchset
Where agents read it
- Guide for this component: https://beautiful-ui.dev/md/sprint-board.md
- Every component, for tools without MCP: /llms.txt
- MCP server:
https://beautiful-ui.dev/api/mcp(setup)
Behaviour
Keyboard
- Tab then Enter
- Open a card, move it back or forward
- Enter / Esc
- Add or cancel in the add-task field
- ← →
- ALL / MY WORK
Accessibility
- Columns are labelled groups with their counts; the WIP limit is an image labelled with how full it is
- Card titles are buttons with aria-expanded; move buttons are named with the task and aria-disabled at the ends
- Every move, refusal and addition is announced in the status line
Motion
- Move
- A card enters its new column from the side it came from (460ms settle)
- Done
- A strikethrough draws across each line of the title (420ms)
- WIP limit
- The full column shakes and outlines in signal
- Progress
- Ruler cells fill 40ms apart
Responsive
- Under 760px (container width) the columns scroll sideways with snap, one and a bit in view.
Performance
- Plain cards and CSS transitions; nothing runs while idle.
Changelog
v1.0.0 · 2026-10-04
First release
Part of
Included with Pro
Pro is in early access.
