PROJECT MANAGEMENT
End-of-Shift Handoff Baton from Linear Activity
At the end of a squad's working window, gathers everything that moved in Linear that day and posts a structured handoff baton note to the next region's Slack channel…
How it runs
The automated pipeline, trigger to output.
- TriggerShift-end schedule fires for outgoing region
- ActionFetch team's Linear issues updated today, grouped by statusLinear
- LogicSeparate blocked and urgent items into a priority bucket
- ActionDraft the baton note with an AI summary stepOpenAI
- OutputPost structured handoff to next region's Slack channelSlack
What it does
Generates a written handoff baton at the close of one timezone's shift. It reads the day's Linear activity for your team — issues moved, blocked, or commented — and turns it into a clear, scannable note in the next region's Slack handoff channel: what's done, what's in flight, and what needs eyes first thing.
When to use it
For follow-the-sun squads where APAC hands off to EMEA hands off to Americas. Run it on a schedule timed to each region's shift end so the incoming team starts with full context instead of digging through ticket history.
How it works
- 1A scheduled trigger fires at the configured shift-end time for the outgoing region.
- 2Queries Linear for the team's issues updated today, grouped by status (in progress, blocked, in review, done).
- 3Splits out a "needs attention" bucket: anything blocked or flagged urgent.
- 4An AI step drafts a tight baton note — a one-line summary plus the grouped lists and the priority items called out at top.
- 5Posts the formatted note to the next region's Slack handoff channel, tagging the incoming on-call.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.
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.