Privately nudge owners of stalled Dart tasks in Slack

By General Input

Every weekday morning, an agent finds work that has quietly stopped moving in Dart and sends each owner a private Slack nudge, plus one summary for managers.

Integrations

  • Dart
  • Slack Bot

Type

Agentic Task

Categories

  • Operations
  • Product

Every weekday at 9am, sweep my Dart workspace for work that has stalled and privately nudge the people who own it.

Start with Dart's Get User Space Configuration to learn how my workspace is actually set up: the dartboards, the status names, the priority levels, and the assignees along with their email addresses. Do not assume status names. Names like "In Progress" or "In Review" vary between workspaces, so resolve the real active status names from the configuration and use those for the rest of the run.

Then use Dart List Tasks to pull every task currently sitting in one of those active statuses. Page through the results until you have all of them, not just the first page.

Treat a task as stalled when either of these is true: it has not been updated in five or more working days, counting weekdays only so that work from Friday is not flagged on Monday, or its due date has already passed while the status is still open.

Use judgement before flagging anything. Leave low priority items alone. Leave a task alone if it is blocked and someone recently left a comment explaining why, which you can check with Dart List Comments on candidate tasks. Leave work alone that has clearly been parked intentionally, for example something in a backlog-style status or explicitly marked as waiting on an outside party. When it is genuinely ambiguous, prefer not to nudge. Reminders that feel noisy are the reason people turn this kind of workflow off.

Group the surviving stalled tasks by owner. For each owner with at least one stalled task, find their Slack account using Slack Bot Look Up User by Email with the assignee email you got from the Dart configuration. Then send exactly one Slack Bot Send a Message direct message to that person, never one message per task. List their stalled tasks ranked most urgent first, with the task title, the dartboard it lives on, how many days it has been idle, and its due date. Put the most overdue and longest idle work at the top. Keep the tone friendly, short, and non-accusatory, and invite them to comment on the task if it is parked on purpose. If no Slack user matches that email, skip the direct message for that person but still include them in the manager summary.

On each task you flagged, add a short Dart Create Comment recording that a nudge went out today and who it went to. This keeps the trail visible inside Dart and lets a later run see that the task has already been nudged.

Finally, post one rolled up summary to my managers channel with Slack Bot Send a Message. It should give the total number of stalled tasks, counts broken down by owner and by dartboard, and a short note on anything notable such as tasks that are far past due or a dartboard that is stalling more than the rest. This is one aggregated message with counts, not a message per task and not a list of every individual item. If nothing is stalled, post a single short all clear line instead of staying silent.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them