PROJECT MANAGEMENT
Mid-Sprint At-Risk Digest to Email and Discord
Mid-sprint, scans Linear for issues that are behind schedule or have stalled, ranks them by risk, and sends a prioritized at-risk digest to the team via email and Discord.
How it runs
The automated pipeline, trigger to output.
- TriggerSprint-midpoint schedule
- ActionFetch open active-sprint issues from LinearLinear
- LogicScore each issue by delivery risk
- ActionWrite ranked at-risk digestOpenAI
- OutputEmail digest to teamGmail
- OutputPost digest to Discord channelDiscord
What it does
Gives a mid-sprint reality check on what won't land. Halfway through the sprint it pulls Linear issues that are still open with little recent movement, past their target date, or carrying too many points for the days remaining, ranks them by delivery risk, and broadcasts a prioritized digest so the team can rescope before it's too late.
When to use it
Use it when sprints routinely slip and you want an early warning instead of a Friday surprise. Good for leads who want a ranked 'these are in trouble' list without combing the board themselves.
How it works
- 1A schedule fires on the sprint midpoint, typically Wednesday morning.
- 2The flow pulls open Linear issues for the active sprint with last-update time, estimate, and target date.
- 3A logic step scores each issue's risk from staleness, remaining estimate, and days left.
- 4An LLM step writes a ranked at-risk digest with a short reason per issue and suggested action.
- 5The digest goes out by email to the team and is posted to the sprint Discord channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GmailRead, draft, send, label.
- 4Connect DiscordCommunity channels + voice + bots.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.