Agile browser prototype
Table of Contents
| Item | Where |
|---|---|
| Prototype | the prototype |
| Gemini review | none |
| Group | Testing prototypes |
| Journey | none yet |
1. Summary
The agile tree is org docs that compass creates. The prototype shows a sprint as a kanban board and the agile tree with its charts in the Development area, beside the Tests tab: a Board tab, a Backlog tab and a Charts tab. Any agile doc opens by its link inside the tab.
It is throwaway. It is not production code, it reads no service, and every value on it is mock data.
Open the prototype.
2. Detail
2.1. The verdict
Accepted on 2026-10-11: variant A, the columns. The list stays in the prototype, switchable from the bar at the foot of the page, as the layout for a narrow window if the build wants one.
2.2. The board
One sprint, as columns of stories: Backlog, Started, Blocked, Done and Abandoned. The five columns are always there, so the board does not rearrange itself as cards move. Above the columns sit the sprint line (the work tree, its branch, the sprint, the day), a strip of the work trees and the work item each one is on, four tiles (stories, in flight, blocked, tasks done), and a search box with one chip for each epic. A card shows the title, the environment, the epic, a task progress bar and the age. The story the work tree is on carries an outline and a current marker. A click opens a detail panel with the id, the state, the branches, the pull requests, the description and every task. A task row expands to show what it is blocked on and its dates.
2.3. The two layouts
| Variant | Shape | What it settles | What it gives up |
|---|---|---|---|
| A · Columns | Five columns of cards, with the detail panel on the right | It is the board the old plugin drew, so the team reads it at once | It needs a wide window, and a long Done column pushes the page down |
| B · List | One table, ordered by state, with the same detail panel | It fits a narrow window and sorts and scans well | It loses the column shape that shows flow at a glance |
2.4. The backlog and the charts
The Backlog tab lists the four buckets, inbox, next, deferred and discarded, each with its count and its captures. A capture opens in the tab. The Charts tab shows velocity, the stories done in each sprint, and a burn-up of the current sprint against its scope. These are the series a sprint review reads.
2.5. What the screens cannot do, and say
- Nothing reads the agile tree. The BFF has no agile store. It must read the work tree it runs in, behind an interface, and never call compass.
- Nothing writes. Starting, closing and moving a story stay in compass.
- One sprint. The build lists the sprints and opens the newest.
- The work trees strip needs git on the server. It runs
git worktree listand reads no other work tree's files. - Links. A doc opens by id. The browser never sends a path.
3. See also
- Testing prototypes — the group page.
- Browse the agile tree in ores.web — the story this answers.