> For the complete documentation index, see [llms.txt](https://docs.frayme.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frayme.ai/examples/jira-sprint.md).

# Sprint board

A working kanban board whose card moves sync back to the agent, with burndown analytics and a one-click standup summary.

## The ask

> Show me the current sprint board.

The agent reads the sprint — 34 of 55 points done, 3 days left, two blockers gating 10 points — and composes a board you can actually work.

## What comes back

| Piece       | Component                   | Behavior                                             |
| ----------- | --------------------------- | ---------------------------------------------------- |
| Sprint KPIs | `Stat` ×4                   | Points done, days left, blockers, scope              |
| The board   | `KanbanBoard`               | Drag cards between columns; board state is live      |
| Burndown    | `LineChart`                 | Toggles with an activity `Heatmap` via `ToggleGroup` |
| Blockers    | `Callout` + `InlineMessage` | The two gating issues, called out                    |

## The interesting mechanic: `move` is a canonical event

The board binds its column state and wires the `move` verb — one of the catalog's eight canonical event verbs (`commit`, `select`, `change`, `dismiss`, `search`, `sort`, `page`, `move`) — to a declared action:

```json
{"op":"add","path":"/elements/board","value":{"type":"KanbanBoard","props":{
  "board":{"$bindState":"/boardState"},
  "columns":[
    {"title":"Backlog","count":3,"accent":"#94a3b8","cards":[
      {"title":"Rate-limit headers for the public API",
       "labels":[{"text":"stretch","tone":"info"}],
       "assignee":"MK","meta":"PLAT-497 · 5 pts"}
    ]},
    {"title":"In progress","count":3,"accent":"#3b82f6","cards":["…"]}
  ]},
  "on":{"move":{"action":"moveIssue"}}}}
```

*(excerpt — cards trimmed)*

```json
{"op":"add","path":"/actions","value":{"summarizeStandup":{"kind":"agent"},"moveIssue":{"kind":"agent"}}}
```

Drag PLAT-482 from *In progress* to *In review* and two things happen: the renderer updates the bound board state locally, and the `moveIssue` action fires back to the agent so the tracker stays in sync. The Burndown/Activity toggle, by contrast, is purely local — no round-trip.

## The follow-up: a whole second screen

*Summarize standup* is the demo's big swing. The agent reads the sprint's activity, then answers with an entirely new composition: its plan checking off live, a per-person digest timeline, and tomorrow's focus. One declared action, one press, one new interface.

## Compose it yourself

```ts
import Frayme from '@frayme/api';

const frayme = new Frayme({ apiKey: process.env.FRAYME_API_KEY });

const stream = frayme.compose.stream({
  prompt: 'Show me the current sprint board.',
  ui_type: 'board',
  data: { sprint: {/* issues, points, blockers — rendered verbatim */} },
  actions: [
    { name: 'moveIssue', description: 'User moved a card between columns', kind: 'agent' },
    { name: 'summarizeStandup', description: 'Summarize activity since the last standup', kind: 'agent', required: true },
  ],
});
```

## Try it

Open [frayme.ai/examples](https://frayme.ai/examples) and select **Sprint 24 — board**. Drag a card, flip the analytics toggle, then press *Summarize standup*.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.frayme.ai/examples/jira-sprint.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.