PROJECT MANAGEMENT
Linear epic scope-creep detector with re-baseline draft to lead
Daily check that compares each active Linear epic's current child-issue point total against the baseline captured at kickoff.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the scope check
- ActionFetch active epics and child issues from LinearLinear
- LogicSum current points and compare to kickoff baseline
- LogicKeep only epics that grew past the threshold
- ActionDraft re-baseline summary with OpenAIOpenAI
- OutputDM the draft to the epic lead in SlackSlack
What it does
Scans your active Linear epics once a day, sums the story points of every child issue, and compares that total to the baseline point count stored from kickoff. When an epic has grown beyond your configured percentage (for example 20%), it drafts a plain-language re-baseline summary and sends it to the epic's lead in Slack so a conversation happens before the slip becomes a surprise.
When to use it
Use it when teams quietly add issues to epics mid-flight and the original commitment date silently becomes fiction. Good for delivery leads and EMs who want an early signal instead of a retro post-mortem.
How it works
- 1A daily schedule fires the workflow.
- 2Linear is queried for all epics in active states and their child issues.
- 3Each epic's current point total is summed and compared to its stored kickoff baseline.
- 4A filter keeps only epics whose growth exceeds the threshold.
- 5OpenAI drafts a short re-baseline summary: original vs current points, top added issues, and a suggested new target.
- 6Slack delivers the draft as a direct message to the epic lead.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.