Roadmap Flow Check — the browser companion

Roadmap Flow Check is a small Chrome and Edge extension that helps you turn planning content you already have open in the browser — a Jira board, a Confluence page, a Notion doc, a Slack thread, an Azure DevOps backlog — into a checked, import-ready starting point for a roadmap. It runs entirely on your machine and never uploads what it reads.

What it does

Roadmap Flow Check captures planning text only when you ask it to, works out which parts of the page are initiatives, shows you what it found so you can correct it, and hands the result to Roadmap Flow.

What the review shows you

Each item carries a short label for anything a roadmap reviewer would ask about, so you can see at a glance what will arrive incomplete.

Lists longer than the screen

A backlog of 100 rows does not exist in the page all at once — Jira, Azure DevOps and most list views only draw the rows near where you are scrolled, and throw away the ones you have scrolled past. A single reading would capture only what happened to be on screen.

So Check this whole page scrolls the list itself, reading as it goes and recognising rows it has already seen, then puts your scroll position back. It then tells you how far it got:

• "Read the whole list — 6 screens, nothing below." Everything is captured.
• "Read 12 screens and stopped before the end." The list was longer than the time it allows itself, or it keeps loading more. Read more of this page continues from where you are now and folds the new rows into the same list.

Either way nothing is captured twice: rows are matched on the tracker's own identifier where there is one, so reading the same row on two passes adds one item, not two.

It also scores the capture from 0–100 — Strong (80+), Partial (50–79) or Weak (under 50) — and tells you how many of the items need attention. The score reflects gaps a roadmap reviewer would ask about: missing outcome, owner, status, target, priority, risk, unresolved decisions and dependencies, and weak titles. Each item is judged on its own words, not on the rest of the page. It only reports gaps; it never invents content.

Anything that is clearly part of the page rather than a plan — a menu entry, a sidebar label, a comment count — is left out and counted, and you can open Ignored page elements to see exactly what was set aside and why.

Which tools it reads

For example, for teams using GoodDay to manage product roadmaps, backlogs, and development projects, Roadmap Flow Check can help capture selected planning information when it is accessible as readable browser text. Teams can then review and import this information into Roadmap Flow to prepare stakeholder presentations.

A Google Doc draws its text as a picture rather than as text, so there is nothing on the page for any extension to read. Roadmap Flow Check says so when you open it there, and points you at the paste box, which works perfectly.

When to use it

• You are reading a planning doc and spot a handful of things that belong on the roadmap.
• You want a quick, honest read on whether some notes are roadmap-ready before you start typing items.
• You want to capture from a tool Roadmap Flow does not import directly (Notion, Confluence, Slack, Google Docs).

When not to use it

• To migrate a whole backlog. For a structured bulk import with column mapping, use Items → Import → Jira or Azure DevOps (Team). Roadmap Flow Check deliberately warns you when a single capture exceeds 25 items.
• To keep a roadmap in sync with the source tool. It is a one-time capture, not a connection — there is no sync, no write-back, and no account.

3-minute flow

1. Install Roadmap Flow Check from the Chrome Web Store and pin it. In Edge, open the same listing and allow extensions from other stores when prompted.
2. Open the planning page. Select the part you care about if the page is long.
3. Click the extension → Check the selected text, or Check this whole page.
4. Read the list. Untick anything that does not belong, fix a title if it needs it, and look at the labels to see what will arrive incomplete.
5. Click Copy for Roadmap Flow.
6. In Roadmap Flow: Items → Import → Roadmap Flow Check, paste, pick the roadmap, workstream and owner team, then add.

Closing the popup does not lose your review — reopen the extension and it is still there.

Best use cases

• Pulling three or four initiatives out of a long strategy doc.
• A fast readiness check on rough planning notes before a drafting session.
• Capturing from Notion or Confluence, which have no direct importer.

Common mistakes

• Scanning a whole backlog page and adding everything — untick down to what is really going on the roadmap.
• Treating the readiness score as a grade on your strategy. It scores how complete the capture is, not whether the plan is good.
• Expecting it to update the source — it is one-way capture by design.

Related guide pages

• Capture planning notes with Roadmap Flow Check
• Share — exports and transfer
• Importing items from Jira or Azure DevOps