Regulatory Change Watch

skill

Monitor regulator sites for tracked topics on a schedule and produce cited change digests.

Download .md

Regulatory Change Watch

Monitor regulator websites for topics you track on a recurring schedule and produce cited digests that summarize what changed.

When to use

  • You need to know when a specific regulator (e.g. a data-protection authority, financial regulator, or health agency) publishes new guidance, rules, or enforcement actions on a tracked topic.
  • Stakeholders want a recurring digest instead of manually re-checking regulator sites.
  • You need a first-pass, cited summary of a regulatory change that a licensed human (counsel) will review before anyone acts on it.

Tools

  • browser-search — find recent pages or announcements on a regulator's site for a tracked topic.
  • browser-navigate — open a specific regulator page, notice, or bulletin.
  • browser-extract — pull the text of the notice or page for summarizing.
  • schedule-task — set up the recurring check (e.g. weekly) for a tracked topic/regulator pair.
  • send-email — deliver the digest, or the "not legal advice" notice, to the assigned recipient.

Playbook

  1. On each scheduled run (set up via schedule-task), start from the list of tracked topics and regulator sites you are watching.
  2. For each tracked topic, use browser-search to look for new items since the last run (e.g. search site:sec.gov or site:ftc.gov plus the topic keyword).
  3. Use browser-navigate to open each candidate result, such as a regulator bulletin or press release page.
  4. Use browser-extract to pull the visible text of the notice, guidance, or rule change.
  5. Compare the extracted content against what you tracked previously; identify only genuinely new or updated items, and note the exact source URL and publication date for each.
  6. Draft a change digest: one entry per new item, each with a one- to two-sentence plain-language summary and its cited source URL. Do not add interpretation of legal obligations or recommend actions — state only what changed and where it was published.
  7. Prepend the digest with: "Not legal advice — attorney review required." This note must appear on every digest, with no exceptions.
  8. Route the digest for approval via create-task, assigned to counsel (a licensed attorney), before it is sent to any other recipient. Do not send the digest onward until that review task is marked complete.
  9. Once counsel approves, use send-email to deliver the digest to the intended recipient list. Never use send-email to contact the regulator or any external counterparty directly — outbound contact stays internal only.

Failure modes

  • A regulator page requires a login, CAPTCHA (automated human-check), or paywall to view the full notice — stop and hand off to a human rather than guessing at the content.
  • The extracted text is ambiguous about whether a change is final guidance versus a draft/proposal — flag this explicitly in the digest rather than presenting it as settled.
  • Two tracked sources describe the same change with conflicting dates or scope — include both citations and flag the discrepancy instead of picking one.
  • The scheduled run finds no changes — send a short "no updates" digest rather than skipping the run silently, so recipients know monitoring is active.

Done when

  • A digest with dated, cited entries (or an explicit "no updates" note) has been produced for the run.
  • The digest carries the "not legal advice — attorney review required" note and has passed the create-task approval gate to counsel before delivery.
  • The approved digest has been delivered via send-email to the correct recipient, with no direct contact made to any regulator or counterparty.