Build Your Roadmap Progress Agent

The short version

The Roadmap Progress Tracker agent runs every weekday at 9 AM and cross-references your roadmap against engineering reality. It checks four systems: Jira or Linear (roadmap status), engineering tickets (last activity), GitHub commits (real code activity), and PM updates in Slack. The output is a six-section report with discrepancy alerts ("in progress" with zero commits in 5 days), stale tickets, missing engineering tickets, ETA accuracy trends, ownership gaps, and a daily summary. The point is to stop operating on faith and start operating on data. Roadmaps and engineering work live in separate systems and drift weekly. Run it tomorrow and check how many of your "in progress" items had a commit this week.

Your roadmap says a feature is "in progress." The PM is tracking it. The customer is waiting for it. Engineering status updates say it's on schedule.

Then you check the commit history. Zero commits in 5 days.

This is the moment most PMs realize they have no idea what's actually happening in engineering.

The problem is simple: the roadmap and engineering work exist in separate systems. Your roadmap lives in Jira/Asana. Engineering tickets live in a different Jira board (or Linear, or GitHub). The PM updates the roadmap based on what engineering told them. Engineering is often honest, but sometimes they're just guessing about the timeline too.

So you have two systems of record, and they're frequently out of sync. A feature marked "in progress" on the roadmap has no corresponding engineering activity. A blocking issue appeared in Slack but never made it to the roadmap. An engineering ticket has been "in progress" for 6 weeks with no movement.

What if an agent cross-referenced these systems daily and showed you exactly where reality diverged from the plan?

Why PMs Need to See Engineering Reality

Most PMs operate on trust. Engineering says "we're on track," so you believe it. But that's not visibility, that's hope.

Here's what happened at a company I advised: a feature was scheduled to launch mid-quarter. The PM tracked it. The customer knew about it. The CEO mentioned it in a board update. But the engineering team had actually de-prioritized it in favor of technical debt. The PM didn't know until a week before launch.

Then there was a panic. Hard decision: slip the customer feature or cut technical debt work. Customer was upset either way.

If the PM had a system that cross-referenced roadmap status against actual engineering activity daily, they would have seen the divergence a month earlier. They could have raised the prioritization question with leadership then, instead of in a crisis.

Here's the pattern I see: the PM-engineering gap grows over time. Week 1 of a feature, the roadmap and commits are aligned. Week 3, they're slightly out of sync (roadmap shows "in progress," commits show "no activity"). Week 6, they're completely misaligned (roadmap shows "done," engineering shows "still in progress").

Without a daily cross-check, you don't notice until it's too late.

What a good Roadmap Progress Agent does: it looks at your roadmap, finds the corresponding engineering tickets, checks the commit history, and asks simple questions:

• "Roadmap says this is in progress. But no commits in 5 days. Why is that?"
• "Engineering ticket created 6 weeks ago. Still in progress. Is this a blocker or abandoned work?"
• "Roadmap item has no engineering ticket at all. Should it?"
• "Feature was supposed to be done by now. How accurate are ETAs actually?"

These are hard questions, but the answers keep you grounded in reality.

How It Works: The Cross-Reference System

The Roadmap Progress Tracker Agent monitors four systems and cross-references them:

1. Roadmap/Backlog System

The agent scans your product roadmap (Jira, Linear, Asana) for:

• All items marked "In Progress"
• All items with ETA = this week or next week
• Items that have been "Blocked" for > 7 days
• Items completed in past 7 days (to calculate velocity)

It extracts: feature name, status, ETA, PM owner, and any link to an engineering ticket.

2. Engineering Tickets

For each roadmap item, the agent finds the corresponding engineering ticket and checks:

• Current status (In Progress / Done / Blocked)
• Last activity date (when was code last touched?)
• Estimated completion date
• Open blockers or dependencies

If a roadmap item has no engineering ticket, the agent flags this.

3. Git Commit Activity

The agent checks GitHub/GitLab for:

• Recent commits to branches related to roadmap items
• Pull request status (are PRs open and waiting for review?)
• Commit frequency (is engineering actively working on this?)
• Stale branches (not touched in 3+ weeks)

For each feature marked "in progress," it asks: "Is there actual code activity?"

4. PM Status Updates & Notes

The agent scans PM communication (Slack, Notion, email) for:

• Items flagged as "at risk" or "slow"
• ETA adjustments (did we slip the timeline?)
• Scope changes (did the feature get smaller or bigger?)
• Engineering blockers mentioned

It connects PM narrative to engineering reality: "PM said 'slowed down,' but is engineering blocked or re-prioritized?"

What the Daily Report Looks Like

Every weekday at 9:00 AM, you get a cross-reference report with six sections:

Section 1: Discrepancy Alerts

🚨 CRITICAL DISCREPANCIES:

🔴 "In Progress" But No Engineering Activity:
1. "Bulk Export" - Roadmap says: "In Progress, ETA Feb 28"
   Reality: Eng ticket #2834 has 0 commits in 5 days, no PR activity
   Status: Work stalled or not started
   Recommended action: Engineering lead check-in TODAY

2. "SAML Auth" - Roadmap says: "Blocked, ETA Mar 1"
   Reality: No engineering ticket created yet, waiting on BE refactor
   Status: Can't start until blocker clears
   Recommended action: Get ETA on blocker, communicate risk to customer

🟡 MISALIGNMENT:
3. "Webhook Redesign" - Roadmap says: "In Progress, ETA Feb 20"
   Reality: 3 commits/week (active), but 1 PR waiting on code review
   Status: Work happening but code review backing up
   Recommended action: Accelerate PR review

This is your reality check. You see which roadmap items diverge from engineering reality.

Section 2: Stale Tickets

⏱️ STALE WORK (No activity in 14+ days):

🔴 CRITICAL (>21 days):
- Eng ticket #2878 "Refactor authentication module"
  In Progress since Jan 20, last commit Dec 28
  → Orphaned work. Recommend: assign owner, resume, or remove.

🟡 WARNING (14-21 days):
- Eng ticket #2834 "Bulk Export Feature"
  Last commit 5 days ago, velocity slowing down
  → Check in with engineer (blocked? re-prioritized? bandwidth?)

This is your abandoned work detection. You see tickets that have been sitting for weeks.

Section 3: Missing Engineering Tickets

🔲 ROADMAP ITEMS WITH NO ENGINEERING TICKETS:

- "Advanced Permissions System" - Roadmap: "Planned for Q2"
  No eng ticket created yet
  → Action: Create epic + break into tickets

- "SAML Auth" - Roadmap: "Blocked, waiting on BE refactor"
  No auth feature ticket yet (blocked on #2845)
  → Action: Create ticket once blocker clears

This is your scope tracking. You see items that are "planned" but haven't made it to engineering yet.

Section 4: ETA Accuracy & Velocity Trends

📊 ETA ACCURACY:

RECENT COMPLETIONS (this week):
- "OAuth Integration": Roadmap ETA Feb 8, Actual: Feb 7 ✅
- "API Versioning": Roadmap ETA Feb 10, Actual: Feb 12 (↑2 days late)

ACCURACY TREND (past 30 days):
- On time or early: 6 items (55%)
- 1-3 days late: 3 items (27%)
- 4+ days late: 2 items (18%)
- Average variance: +1.8 days

VELOCITY TREND:
- This week: 2 items completed
- Last week: 3 items completed
- 4-week average: 2.25 items/week
- Note: Velocity declining (was 2.8/week in January)

IMPLICATIONS FOR CURRENT ROADMAP:
- 3 items with ETA this week: expect 2 on time, 1 slips by 1-2 days
- 5 items with ETA next week: expect 3-4 on time

This is your historical accuracy. You see how good PM ETAs actually are and adjust future estimates.

Section 5: PM Ownership & Engagement

👤 OWNERSHIP STATUS:

Clear ownership & recent engagement:
- "Custom Fields API" - PM: Alex (last update: today) ✅
- "Webhook Redesign" - PM: Casey (last update: 3 days ago) ✅

Stale or unclear ownership:
- "SAML Auth" - PM: Unassigned 🔴
  → Action: Assign PM immediately

- "Bulk Export" - PM: Jamie (last update: 5 days ago, no activity)
  → Check in on status

This is your engagement check. You see which roadmap items have active PM involvement.

Section 6: Weekly Summary

One paragraph with roadmap-to-reality alignment and immediate actions:

SUMMARY:
Most roadmap items are aligned with engineering reality. 8 of 11 are progressing actively.
However, 3 items need attention: (1) "Bulk Export" stalled (0 commits in 5 days - check blockers),
(2) "SAML Auth" needs PM owner and clear scope, (3) "Webhook Redesign" ETA may slip if PR reviews
don't accelerate.

ETA accuracy is decent (average +1.8 days variance) but slightly declining. Velocity at 2.25 items/week
(down from 2.8 in January). Current roadmap assumes 2.5 items/week - slightly optimistic.

IMMEDIATE ACTIONS:
1. Engineering lead check-in on "Bulk Export" status (0 commits in 5 days)
2. Assign PM owner to "SAML Auth" by EOD today
3. Accelerate PR review cycle for "Webhook Redesign"

Data sources and setup

Prerequisites: Complete the Claude setup guide first. This agent needs the following MCP connections active:

• Jira - reads roadmap items, engineering tickets, and status
• GitHub - reads commit history and PR activity
• Slack - reads PM status updates and engineering discussions
• Salesforce - reads customer escalations and account context (optional)
• Gong - reads call transcripts for context on feature requests (optional)

Schedule: Runs weekdays at 9:00 AM via cron. Output posts to Slack and emails product leadership.

Quick test: Open Claude and ask: "Show me all roadmap items that are behind schedule or have unresolved dependency risks."

For the full agent fleet and scheduling details, see Your AI Agent Fleet.

What Changes When You Have This Agent

Before: You're operating on faith that the roadmap matches reality.

• Your roadmap says everything is on track
• Engineers say "we're busy"
• Customer asks "when will my feature ship?"
• You give your best guess

After: You're operating on data about what's actually happening.

• Your roadmap is cross-checked against actual engineering activity daily
• You know which items are at risk weeks in advance
• You can tell the customer "we're on track" or "we need to rescope" with confidence
• You make decisions based on reality, not hope

The difference is alignment. The roadmap becomes a shared reality between product and engineering, not a aspirational document that diverges from execution.

Most days, the discrepancies are minor ("one feature is moving a bit slower than expected"). But 2-3 times a month, the agent catches a major issue (feature that stalled, ETA that needs to slip, engineering work that got orphaned). That's worth checking daily.

Getting Started This Week

The full agent setup - with all the cross-reference rules, ETA accuracy calculations, velocity tracking, and copy-paste ready prompt - is in the artifact file linked below.

Download it. Create a Claude Project. Paste the prompt. Connect your data sources. Set it for weekday mornings at 9:00 AM.

By next week, you'll have your first report. You'll see exactly where your roadmap matches engineering reality and where it diverges. You'll know your actual ETA accuracy. You'll see your team's real velocity.

Then you'll make better commitments.

Download the Complete Agent Setup

Download the full agent instruction file

This includes:

• Complete agent prompt (copy-paste ready)
• All data sources with cross-reference rules
• Full report structure with examples
• ETA accuracy calculation framework
• Velocity tracking methodology
• Setup instructions for Claude Projects
• Customization guide for your workflow

Use this to set up your own Roadmap Progress Tracker Agent. Takes about 30 minutes to configure data sources, then it runs automatically every weekday morning.