Skip to main content

Roadmap

Roadmap is the output side of Discover — the prioritized list of features your workspace is going to build, the features in flight, and the signals (errors, customer feedback) feeding the backlog. It's the handoff point between Discover and Ship: a card on the Kanban here is what an agent picks up to do real implementation work. The page lives at /<workspace>/roadmap and has four tabs.

📷 Screenshot: Roadmap with the Kanban tab active, filter bar and view toggle on the right.

Backlog​

The prioritized list of unstarted features, ranked by AI suggestion (impact × customer signal ÷ effort) and overlaid with anything you've manually pinned to the top.

Each card shows the feature title, suggested priority, source signal (e.g. "from meeting with Acme — 2026-04-12", "GA4 attribution shift", "GitHub issue #214"), and an estimate of scope. Click a card to open the feature detail modal and read the full brief, edit scope, link related docs, or promote it.

Promoting a backlog item moves it to Kanban with status Not Started — that's the trigger that makes it eligible to be picked up.

Kanban​

The default tab, and the day-to-day view for in-flight work.

Columns map to feature lifecycle: Not Started → In Progress → Review → Complete. Drag a card across columns to change its status; the agent assigned to the feature reacts (e.g. moving a card to In Progress triggers the Code agent to start implementing on the connected branch).

Controls above the board:

  • Filter bar — narrow by assigned user (you/teammate) and by tag. The "All users" → "Just mine" toggle is the most common use; pin to your own work and the columns simplify.
  • View toggle (Kanban / List) — same data, different layout. List view is a sortable table; Kanban view is the dragable board. Choice is persisted per browser.
  • Add Feature — opens a quick-add for a manually-scoped feature, separate from the AI-suggested backlog flow.

Click any card to open the feature detail modal: brief, scope, agent runs, generated documents, deployment status, and links into the relevant Ship surfaces (Code, Testing, Deployments, Monitoring) so you can audit what's been done without leaving the modal.

Errors​

Production errors that have been triaged into actionable roadmap candidates. Each row links back to the source Monitoring entry, the affected service, the user impact, and (where confidence is high) a suggested fix the Code agent can take on directly. Promote an error to Kanban to assign it for fix-up; archive it if it's noise.

This is the path from "the platform noticed something broke" to "an agent is fixing it on a branch."

Feedback​

Admin-only. The aggregated customer-feedback inbox — support-ticket themes, in-app feedback widgets, social mentions, NPS comments — clustered by topic so you can see the volume behind a complaint before deciding whether it deserves a roadmap slot. Promote a cluster directly into a backlog item; the originating quotes carry along as context for whichever agent ends up implementing.

Editing features from chat​

You don't have to open the Kanban to correct a feature — ask the assistant in Chat and it edits the feature for you. Three tools cover the feature lifecycle, and the assistant picks the right one:

  • updateFeature — change an existing feature's record and its dependency links: title, description, priority, labels, assignees, status/stage, and blocked_by / blocks / related / duplicate links. Use it to fix a wrong priority, rename a title, or wire up a blocked_by link that didn't get set at create time ("mark this feature blocked by FEAT-123", "bump this to Urgent and rename it to …").
  • updateFeatureDocument — edit the contents of a feature's stage documents (requirements, design, implementation, deployment), not the feature record.
  • featureCreate — create a new feature. Use this for new work, not for correcting an existing one.

Partial updates. updateFeature only changes the fields you mention — everything you don't name is left exactly as it was. To clear a field, say so explicitly: an empty description clears it, priority None resets priority, and clearing all labels or assignees empties those lists.

Links. Dependency links come in four kinds — blocked_by, blocks, related, and duplicate — and there is one relationship per pair of features. Adding a link that already exists is a no-op; adding a different relationship to a feature you're already linked to replaces the old one. (Parent/child sub-feature relationships are managed automatically and aren't edited this way.)

Status changes mirror the board. Asking the assistant to move a feature into a workflow stage (Requirements, Design, Implement, Deploy) does the same thing as dragging its card there — it can auto-start that stage's agents. Every edit an agent makes shows up on the feature's timeline the same way a manual edit would, so the change is auditable, and open Kanban cards refresh on their own.

How Roadmap connects the pillars​

  • In — Analytics insight cards, Meeting action items, GitHub issues, and clustered Feedback all flow here as Backlog candidates.
  • Out — moving a card to In Progress on the Kanban kicks off Ship: Code agents start implementing, Testing runs the suite on the agent's branch, Deployments handles the release, Monitoring watches it land.
  • Loop — once a feature ships, the related Analytics movement, customer feedback, and any new errors are linked back to the originating roadmap card so you can tell whether the bet paid off.