PROJECT MANAGEMENT
Mid-Sprint Burndown Drift Alert vs. Forecast
Daily during an active sprint, checks Linear burndown against the velocity-based ideal pace and alerts Slack when actual progress drifts far enough behind to put the commitment…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule during active sprint
- ActionRead remaining points and elapsed days from LinearLinear
- LogicCompute drift vs. velocity-based ideal pace
- OutputPost at-risk drift alert to SlackSlack
What it does
This workflow watches a sprint while it is running. Each day it compares remaining work in Linear against the pace implied by the team's historical velocity, then warns the team when the gap grows large enough that the original commitment is no longer reachable on the current trajectory.
When to use it
Use it mid-sprint when teams discover slippage only at review. A daily drift check surfaces trouble while there is still time to descope or pull in help.
How it works
- 1A daily schedule fires while a cycle is active.
- 2The workflow reads remaining open points and elapsed days for the current Linear cycle.
- 3It computes the ideal remaining line from velocity and sprint length.
- 4A logic step measures drift between actual and ideal and checks it against an at-risk threshold.
- 5When drift breaches the threshold, it posts a Slack alert with projected completion and the shortfall.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
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.
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.
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.