PROJECT MANAGEMENT
Daily Slack digest of points added to the sprint, ranked by requesting stakeholder
Each weekday morning, sums the story points added to the active sprint since commit, groups them by the stakeholder who requested each item.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday 8am schedule
- ActionQuery issues added after cycle startLinear
- LogicGroup and rank points by stakeholder
- LogicSkip if no new scope since yesterday
- ActionPost ranked digest to SlackSlack
- OutputDaily scope-growth leaderboard deliveredSlack
What it does
On a daily schedule, this workflow tallies every point added to the current sprint after the commit date, attributes each addition to its requesting stakeholder, and posts a leaderboard-style digest to a Slack channel.
When to use it
Use it when scope creep is a recurring problem and you want gentle, visible accountability without a meeting. A daily "added points by stakeholder" post makes the trend impossible to ignore.
How it works
- 1A schedule trigger runs every weekday at 8am.
- 2An action queries the Linear cycle for all issues whose added-to-cycle date is after the cycle start.
- 3A logic step groups the added points by requesting stakeholder and sorts descending, computing the running sprint total.
- 4A logic step checks whether any new points were added since yesterday and exits quietly if scope is unchanged.
- 5An action formats the ranked list with deltas and posts it to the team Slack channel.
- 6The Slack message is the daily output that surfaces accountability to the whole team.
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.