The backlog is decided,the roadmap is still unwritten
You already know what the squad is building next quarter. What you do not have is the page that says it in themes, in plain language, with a reason under every line. Khint reads the epic list you select, groups it, writes the rationale from your own quarter of work, and publishes the roadmap where stakeholders will actually look.
Deciding took a month,
writing it up takes a Friday
The hard part is behind you: the candidates were scored, the squad committed, the epics are in the tracker. Then somebody asks for the roadmap, and what they mean is a page: five themes instead of forty tickets, an outcome per theme, and a defensible reason each one sits where it sits. That page is a retyping job, and it goes stale the week after you write it. Khint runs it as a saved agent on the list you already have, with your quarter of context riding along.
The real palette running a saved workflow: the writing steps run first, then the last step files the result in the tool your stakeholders read.
From an epic list to a roadmap page
Writing the Q4 roadmap for a payments squad, between two meetings.
Open a session for the quarter
Start a Memorysession called “Q4 roadmap” before you open the tracker. Every action you run and every write you make is logged to it, and Khint keeps a compact working state beside it: the objective, the open threads, the decisions already taken. That summary is attached to your later runs, so the agent that writes the rationale already knows the constraint the architects raised in October without you restating it. Sessions live in a local database on your machine and are never synced.
Put the committed work in front of you
The input is whatever list you already trust: the epics on the board, a prioritisation spreadsheet, the notes from the planning session. Connect Atlassian and the palette can pull your issues in first, and the JQL row will write the query for you when the filter is fiddlier than a saved one. However the list gets on screen, select it and press Cmd+Shift+K: an agent reads exactly what you highlighted, and nothing else from the screen.
Group forty tickets into five themes
In Agents, save an action like “Group into roadmap themes”. No prompt yet? Type a one-line description and press Generate: Khint drafts one that returns now, next, and later, a theme name a non-engineer would recognise, the outcome each theme buys, and the epics folded underneath it. Run it and the grouped roadmap is pasted back where you were working. Press Improve later to bend the shape to your house template, and it is bent for every quarter after this one.
Attach a reason to every line
A roadmap without reasons gets relitigated in the meeting. A second agent writes one rationale line per theme, and if you tick Search Knowledge on it, each run also searches your own indexed Jira, Confluence, Notion, and Linear content and attaches the most relevant excerpts. The customer ticket that started the payment-retry work and the page where the compliance date was agreed come back into the write-up instead of being things you half remember. The index is local to your machine and off until you switch it on.
Publish it, then keep it alive
Connect Atlassian and the palette adds a Confluence Create page row: the roadmap lands as one page in the space stakeholders already read, and the URL comes back as the result. Next month, when two themes move, the append row adds the update under what is already there rather than replacing a page other people have been commenting on. See how integrations work.
One shortcut, epic list to published roadmap
Up to five steps in series, starting from the selection, a document, or your voice.
Each step's result becomes the next step's input: the first agent returns the themes, the second adds the reasoning under each one, and the write step turns that into a page. Swap the last step for a fan-out and the same run also posts the summary to the squad channel and opens the review ticket, dispatched at the same instant rather than one after another. Build it once in the workflow editor, or describe it in a sentence and let Khint draft the steps for you.
What it will not do for you
A roadmap is a promise other people plan against, so it is worth being exact about where the machine stops.
It does not decide the order
Khint writes up the decision you already made. An agent reads the list you selected, plus your session context and the excerpts the local index returned, and nothing else: it has no view of your capacity, your revenue, or your delivery data, so it cannot rank the work for you. Score the candidates first, then hand the result to the write-up.
Dates are yours, not the model's
If the epics you select carry target quarters, the roadmap keeps them. If they do not, an agent has no way to know when anything ships, and a prompt asking for dates will invent plausible ones. Put the commitments in the input, or write the roadmap in now, next, and later, which is the honest shape when the second half of the year is not committed.
The local index is a copy on a schedule
Your connected Jira, Confluence, Notion, and Linear content syncs into the local index shortly after launch and then every half hour, rather than being queried live. A ticket someone reprioritised two minutes ago may not be in it yet. Sync now forces a pass, and switching a source off deletes its local copy straight away.
One write per run, on purpose
A write step creates one page, one ticket, or one post, and a fan-out is two to four destinations rather than a batch. You pick the space or the channel before the model runs, so cancelling costs nothing, and a roadmap page is published only when you chose to publish it.
Prioritisation decides, this is the write-up
These are two different jobs and it is worth keeping them apart. Choosing what to build is a judgement call made with people: structuring value against effort and turning the quarter's intent into objectives and key results are covered on their own pages. What is left afterwards is communication: the same decision written five ways for five audiences, refreshed every time something moves. That is the part worth saving as an action, because you will run it again in January, and again in April, on a list that has changed but a format that has not. If the roadmap also has to be a slide, Khint's PowerPoint companion turns the selected theme list into an editable timeline built from real PowerPoint shapes, on macOS.
Common questions
Can Khint build my product roadmap for me?
It writes the roadmap, it does not decide it. Khint is a desktop app that runs saved AI actions on the text you select, so it can take the epic list you have already committed to and return it as themes with an outcome and a rationale under each one, in the format your stakeholders expect. What it cannot do is choose between two features: an agent sees the selection you gave it, your active session summary, and the excerpts your local index returned, so it has no view of capacity, cost, or revenue. The judgement stays with you and the write-up stops being a Friday afternoon.
What does the roadmap agent actually read?
Three things, and only when you allow them. The text you selected before pressing the shortcut, which is always the main input. The compacted working state of your active Memory session if the agent has session context switched on, which is what lets it write a rationale referring to a decision taken weeks earlier. And a handful of excerpts from your local Knowledge index if you ticked Search Knowledge on that agent, which is off by default. Nothing else from your screen, your drive, or your other windows reaches the model.
How do I keep the roadmap page up to date next quarter?
Run the same saved action on the new list. Because the action holds the format, the January roadmap comes back in the same shape as the October one without you re-explaining the template. For the page itself, the Confluence append row adds the update under the existing content rather than rewriting it, which matters when people have been commenting on the page: Khint reads the current version, appends, and refuses to write if someone edited it while you were drafting, so a concurrent edit is never silently overwritten.
Does it work if our roadmap does not live in Confluence?
Yes. The write step is optional and the result is always pasted back where you were working, so a roadmap that lives in a slide, a doc, or a wiki Khint has no integration for still gets written. Beyond Confluence, the palette can create a Notion page, post to a Slack channel, open a Jira or Linear issue, and a workflow can fan out to two to four of those at once. If your roadmap has to be a slide, the PowerPoint companion turns the theme list into an editable timeline diagram on macOS.
Where does my unreleased roadmap go?
The text of a run goes to the model for that run and comes back. Memory sessions and their entries are stored in a local database on your Mac or PC and are never synced to Khint's servers, and the Knowledge index of your Jira and Confluence content is built and searched on your own machine. Your history keeps the metadata of a run in the cloud so it follows your account, but the input and output text stay local. If a line carries personal data, an agent can be set to replace emails and phone numbers with placeholders before the text leaves, and on the Lifetime plan you can point Khint at your own API key.
Write the next roadmap in one pass
Free with 300 credits a month, about 10 AI actions a day. No credit card. Save the action once and every quarter after this one comes back in the same shape.