A product roadmap needs fields that track theme, status, priority, owner, and dates, plus at least three ways to see the same items: a table, a status board, and a timeline. You can build the structure in Probe with one typed request, then add example items with a second. The whole run below cost 66 credits.
Key takeaways
What a product roadmap is for
A product roadmap is the plan that shows what a team is building and in what order, grouped by theme and tracked by status so stakeholders can see priorities without asking. Atlassian notes (opens another site) that different teams, from engineering to sales, often need their own view of the same roadmap, which is why having a database with several views over the same records, rather than separate documents, matters: a change in one view shows in all of them.
Step 1: Describe what you need
In Work Studio, click New Paper, choose Doc, and type a title such as "Product roadmap." Click Build with AI under the title. A box appears asking "What is it for?" Type your request and press Enter.
The request used here, word for word:
"A product roadmap. Each item has a theme (growth, quality, platform), a status (idea, planned, in progress, shipped), a priority (now, next, later), an owner, a start date and a target date. I want a timeline by start and target date called Timeline, a board by status called By status, and a table of every item called All items."

The card was ready 12 seconds after sending, for 26 credits across two charges. Grouping fields into themes like this, rather than tracking every feature as a flat list, is one of the standard ways to organize a roadmap, as Creately explains (opens another site).

Why nothing changes until you approve
Before anything is created, Probe shows a Review required card. It lists exactly what will happen: here, a new database Paper named "Product roadmap," separate from the Doc you started in, with fields for Item, Theme, Growth/Quality/Platform, Status (Idea → Planned → In progress → Shipped), Priority (Now/Next/Later), Owner, Start date, and Target date. The card also lists the three views: All items (table, sorted by priority), By status (kanban board), and Timeline (by start/target date), with "Roadmap item" set as the default row type and no seed records yet.
Nothing changes until you click Apply. Click it, and the screen confirms the Paper was created.

Step 2: Add example roadmap items
An empty roadmap doesn't tell you much, so ask the agent to populate it. The request used here:
"Add six example roadmap items for December 2026 to March 2027 across the themes and statuses, each with a start and target date. Start each title with "Example:"."
The card was ready 15 seconds after sending, for 40 credits across three charges.

The card lists each item with its theme, status, priority, and dates, spread across December 2026 through March 2027 and across all three themes and four statuses.
Click Apply, and the screen confirms the items were added.

Total cost for the run, both steps combined: 66 credits.
The All items table
Click the All items tab at the top of the Paper. This is the view to scan when you want the full list without filtering by stage or time.

The By status board
Open the status board and the same six items appear as cards in columns for Idea, Planned, In progress, and Shipped. Dragging a card to another column moves it to that stage automatically, since all three views share the same underlying records: moving a card here updates its status everywhere else it appears, including the table and the timeline.
The button under the board for adding a new card is named for the row type, so here it reads "New Roadmap item."

The Timeline view
Open the timeline and the same items are laid out by start and target date, so you can see at a glance what's running in December, January, February, and March. The Timeline view has previous and next arrows plus a Today button to jump back to the current date.

What you end up with
A database Paper named "Product roadmap," separate from the Doc you started in, with six example items and three views: a table, a status board, and a timeline, all reading from the same set of records. Each row also opens as its own page the first time you click into it, for notes, files, or anything else you want attached to that item.
Keeping it current
Because all three views read from the same records, you don't rebuild anything when priorities shift. Each change goes through the same proposal card and Apply step, so you can review it before it's applied. As real items replace the examples, delete the "Example:" rows or ask the agent to remove them in one request.
Questions people ask
What fields should a product roadmap have?
A roadmap item typically needs a theme, a status, a priority, an owner, and start and target dates, which is the set used in the database built above.
How do I keep a product roadmap updated without rebuilding it?
Because the timeline, status board, and table views all read from the same records, editing or dragging an item in one view updates it everywhere, so you edit items directly rather than rebuilding the roadmap.
Can I track a product roadmap by theme and status at once?
Yes. Each item carries both a theme field (growth, quality, platform) and a status field (idea, planned, in progress, shipped), and the status board groups by status while the table can be scanned by theme.
Do I need a template to create a roadmap?
No separate template file is needed: describing the fields and views you want to the Paper Agent, as shown in Step 1, creates the structure directly.
Do it on Probe
Open Work Studio, start a new Doc, and click Build with AI to describe the roadmap fields and views you need.
