PROJECT MANAGEMENT
Incoming-Shift Priority Digest to Microsoft Teams
At the start of a region's shift, builds a prioritized digest of what the incoming team should tackle first — overdue items, fresh blockers, and items explicitly handed to them.
How it runs
The automated pipeline, trigger to output.
- TriggerIncoming region's shift-start schedule fires
- ActionQuery Linear for overdue, flagged, and newly blocked itemsLinear
- LogicScore and order items by urgency and handoff tags
- ActionWrite the prioritized digest with AIOpenAI
- OutputPost the digest to the Microsoft Teams channelMicrosoft Teams
What it does
Greets each incoming shift with a ranked to-do board instead of a raw activity dump. It looks across what the previous regions handed off and what's now urgent, then publishes a clean priority digest so the team knows their first three moves the minute they log on.
When to use it
When your squad runs on Microsoft Teams and you want the start of every shift to begin with focus rather than triage. Pairs well with a separate end-of-shift handoff so both ends of the baton are covered.
How it works
- 1A scheduled trigger fires at the incoming region's shift start.
- 2Queries Linear for overdue issues, items flagged for this team, and blockers raised in the prior window.
- 3A logic step scores and orders items by urgency and explicit handoff tags.
- 4An AI step writes the digest: a top-three priority callout followed by the fuller ordered list.
- 5Posts the digest to the team's Microsoft Teams channel as the shift opens.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.