Kanban board · reads task
Sprints
Iterations with scoped tasks.
Cards in columns, one column per stage.
Done
Module demo content
Release pipeline
In progress
Per-module animation
Carried over
Firestore overlay
How it works
- 1
A single field — status, stage, pipeline — decides the columns.
- 2
Every item becomes a card in the column its value names.
- 3
Dragging a card writes the new value back.
Best for
Anything that moves through stages: leads, orders, applications.
Not the right choice for
Data with no natural stages — you get one very long column.
Questions
What data does the Sprints page use?
It reads task records the agent has collected. Iterations with scoped tasks. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a kanban board the wrong choice?
Data with no natural stages — you get one very long column. It is best for: anything that moves through stages: leads, orders, applications.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Planning & time
Fri 12 Sep — Autumn tasting
Events
Everything the agent schedules — dates, place, attendees.
4 Sep — Tasting — Maison Lauret
Calendar
Month/week view across all dated nodes.
07:30
Load in, unlock the hall
45m
08:15
Floor plan and chairs
1h 30m
09:45
Sound check
30m
10:30
Doors
—
Planning / schedule
A run-of-show / agenda timeline.
Gantt chart
Tasks & phases with dependencies and durations.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free