Skip to content

Roadmap Slippage Alerter

Example prompt: "Once a day, check our Linear roadmap for any initiative whose target date has passed without it being Done, and post an alert in #product with what's left on it, what's blocked, and a draft line I can use to tell stakeholders why it's late."

The Problem

Roadmap items slip quietly. The target date passes, the Linear status stays where it was, and nobody mentions it until the next stakeholder review when someone asks why the thing that was meant to ship last month hasn't. By then the PM is reconstructing what happened from memory and Slack scrollback, and the explanation lands worse than it would have if the slip had been flagged the day it happened.

How GloriaMundo Solves It

We build a daily workflow that scans Linear roadmap initiatives whose target date is in the past and whose status is not Done. For each slipped item, integration steps gather the child issues still open, the most recent update or comment, and any blockers explicitly flagged. An LLM step drafts the alert — what was meant to ship, what's left, what appears to be blocking it, and a one-line draft of what to tell stakeholders. A conditional step skips items that were already alerted on within the last seven days so the channel doesn't get the same message every morning. An integration step posts the alert to the #product Slack channel with the Linear link, and a state step records the alert so the dedupe holds across runs. Glass Box preview shows the slipped items and the draft messages before anything posts.

Example Workflow Steps

  1. Trigger (schedule): Runs once a day.
  2. Step 1 (integration): Pull Linear roadmap initiatives whose target date is in the past and status is not Done.
  3. Step 2 (integration): For each slipped item, list the open child issues and the most recent update or comment.
  4. Step 3 (state): Check whether this item was already alerted on within the last seven days.
  5. Step 4 (conditional): Skip items that were recently alerted on; continue with the rest.
  6. Step 5 (llm): Draft the alert — what's left, what's blocking, a one-line stakeholder explanation.
  7. Step 6 (integration): Post the alerts as a single threaded message in #product Slack with the Linear links.
  8. Step 7 (state): Record the alerted items so the next run won't repeat them.

Integrations Used

  • Linear — source of the roadmap initiatives, child issues, and update history
  • Slack — where the slippage alert is posted to the product channel

Who This Is For

Product managers running a roadmap with more than ten in-flight initiatives where individually checking target dates each morning isn't realistic, and where leadership reviews the roadmap on a regular cadence and notices slips. Especially useful where the cost of a surprise slip in front of stakeholders is high.

Time & Cost Saved

A PM doing this properly would check the roadmap every morning, look at each initiative whose target date is close, and chase the blockers — call it 20-30 minutes a day, and most days it doesn't get done. This workflow makes the check consistent and pre-drafts the stakeholder line, so the PM intervenes only on the items that actually slipped and has the explanation half-written when they do.