Capturing planning notes with Roadmap Flow Check

This playbook turns scattered planning content in your browser into a small, checked set of roadmap items — without retyping and without uploading anything. It uses the free Roadmap Flow Check extension for Chrome and Edge.

Available on every plan. The extension is separate from the desktop app and runs entirely on your machine.

Use this when

  • You are reading a strategy doc, a Confluence page, a Notion page, or a Slack thread and a few items clearly belong on the roadmap.
  • You want a quick readiness check on rough notes before you start a roadmap.
  • The source is a tool Roadmap Flow does not import directly.

What you need before starting

  • Roadmap Flow Check installed in Chrome or Edge (Developer-mode unpacked build, or the store listing once published).
  • A Roadmap Flow workspace open on the desktop, with at least one roadmap and a workstream to import into.
  • A clear sense of which few things matter — capture a focused selection, not a whole page.

---

Step-by-step flow

1. Capture

  1. Open the planning page in your browser.
  2. Select the specific text you care about. A tight selection beats scanning the whole page.
  3. Click the Roadmap Flow Check icon, then Check selected text.
    • No selection? Use Scan visible page, Paste planning notes, or Import a CSV instead.

2. Read the readiness check

Roadmap Flow Check scores the capture 0–100 and grades it Strong (80+), Partial (50–79), or Weak (under 50). It lists the top gaps it found — missing outcome, owner, status, target date, priority, risk, unresolved decisions or dependencies, and weak titles.

  • A low score is not a verdict on your strategy. It means the capture is thin — usually the fix is to select a richer piece of text.
  • Use Copy summary if you want the full readiness notes for a doc or message.

3. Export

Click Export to Roadmap Flow to download a .roadmapflow-check.json package. Use Download CSV only if you specifically need a spreadsheet — the JSON package carries the readiness score, source link, and capture context that the importer preserves.

4. Import into Roadmap Flow

  1. In the desktop app, open the roadmap you want and go to Share.
  2. Find Import a checked companion package and choose the .roadmapflow-check.json file.
  3. Review the candidates. Tick only the ones you want — nothing is selected by default.
  4. Choose the destination roadmap, workstream, and default owner team.
  5. Click Append [N] selected candidates. Items are added; nothing existing is overwritten.

---

What good looks like

  • Three to six well-titled candidates land on the right roadmap and workstream.
  • Each imported item carries a working source link back to where it came from.
  • You spend the next few minutes setting horizon, priority, and target — not retyping titles.

Common traps

  • Importing a whole backlog. Over 25 candidates triggers a confirmation for a reason. For a real bulk migration, use the Team Import CSV from Jira or Azure DevOps path instead.
  • Expecting sync. This is a one-time capture — it does not connect to or write back to the source tool.
  • Skipping the review step. Untitled candidates are skipped automatically, but you still choose which titled ones to keep.

Related guide pages

Free Updated in 0.1.8

← Back to the Field Guide