Roadmap Flow Check

Roadmap Flow Check is the browser companion for Roadmap Flow, the local-first roadmap tool for product managers. It helps you pull planning content from the web into your roadmap cleanly — without copying, pasting, or reformatting by hand. WHAT PROBLEM DOES IT SOLVE? Your planning content is scattered. Jira backlogs. Azure DevOps boards. Linear issues. Notion docs. Confluence pages. Slack threads. When it is time to build or update your roadmap, you are toggling between tabs and manually re-entering work that is already described somewhere. Roadmap Flow Check bridges that gap. It reads what is on the page you are already viewing, shows you everything it found so you can correct it, checks each item for roadmap readiness, and hands the result to Roadmap Flow in one move. HOW IT WORKS 1. Open the page Navigate to any planning source — a Jira board, an Azure DevOps backlog, a Linear project, a Notion page, a Confluence doc, a Slack thread, or any web page with planning text. 2. Open the extension popup Click the Roadmap Flow Check icon in your browser toolbar. Nothing has been read yet — the extension waits for you to act. 3. Choose a capture action Check this whole page, Check the selected text, paste planning notes, or import a CSV. The extension reads only what you asked for, only at that moment. 4. Review what it found Every item it read, with the words on the page it came from, an editable title, and a plain label for anything missing. Untick what does not belong. This happens while the source page is still open behind the popup, so you can tell a real initiative from a menu entry without leaving. 5. Check readiness locally Each item is scored for roadmap readiness on your device, judged on its own words. You see what is missing before you import anything. 6. Send it to Roadmap Flow Copy what you kept and paste it straight into Roadmap Flow's import screen, or save a .roadmapflow-check.json package or a compatible CSV. You choose what crosses over. READS THE WHOLE LIST, NOT JUST 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 discard the rest, so anything that reads the page once captures a fraction of what is really there. Check this whole page scrolls the list for you, reads it as it goes, and puts your scroll position back where it was. Rows are matched on the tracker's own identifier, so a row seen on two passes becomes one item, not two. Then it tells you how far it got — "Read the whole list: 6 screens, nothing below", or "Read 12 screens and stopped before the end". A count you cannot trust is not worth having. If it stopped early, Read more of this page continues from wherever you have scrolled and folds the new rows into the same list. REVIEW BEFORE ANYTHING LEAVES The review list shows, for every item: the source text it was read from, an editable title, its status and identifier, whether it carries a link back to the exact issue or page, and short labels for what is missing — No owner, No outcome, No target. Anything that is clearly part of the page rather than the plan — a menu entry, a sidebar label, a comment count — is left out, counted, and listed under Ignored page elements so you can see exactly what was set aside and why. Your review survives the popup closing. Chrome closes a popup the moment it loses focus; click back on the page to check something and your work is still there when you reopen. SUPPORTED SOURCES Dedicated readers, built for the tools product managers use most: • Jira — boards, backlogs and single issues: issue key, summary, status, and each issue's own link, so an imported item points at that issue rather than at the board • Azure DevOps — backlog and board grids, read by column name, so hiding or moving a column changes nothing • Confluence — the page body only; the space sidebar, breadcrumb trail and comment thread are left out • Slack — each message as an item, with the person who wrote it as its owner Everything else — Notion, Linear, and any other web page — is read by the general page reader, which follows the page's own headings, lists and tables. Pasted text and CSV files work anywhere. Google Docs is the exception, and it is worth being straight about it: a Google Doc draws its text as a picture rather than as text, so no extension can read it directly. Roadmap Flow Check tells you so when you open it there and points you at the paste box, which works perfectly. You do not need API keys or service integrations. Roadmap Flow Check reads the page as it appears in your browser, the same way you do. PRIVATE BY DESIGN Roadmap Flow Check was built to handle planning content that often cannot leave your organization. It takes that seriously. • No account required. No sign-in, no profile, no cloud sync. • No data leaves your computer. Page content, captured text, and check results are processed entirely on your device. Nothing is sent to our servers or to any third party. • No background access. The extension reads a page only when you open the popup and choose a capture action. It does not run in the background or monitor your browsing. • No analytics or tracking. No usage telemetry, no session recording, no third-party analytics. • No remote code. The extension runs only the code included in the installed package. • Minimal permissions. activeTab (read the current tab on demand), scripting (inject the capture script after you ask), downloads (save the file you explicitly requested), and storage (hold the capture you are reviewing). No access to all websites, browsing history, or cookies. What is kept, and for how long: the capture you are reviewing is held in your browser's session memory, so that closing the popup does not throw away your work. It is never written to disk, never leaves your device, and is gone when you close your browser. One thing the extension does change on a page: when you ask …