PROJECT MANAGEMENT
Weekly Scope-Drift Digest Across Active Epics
On a weekly schedule, scans every active Linear epic, compares current acceptance criteria against stored baselines, and emails a single ranked digest of which epics grew.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionList active epics from LinearLinear
- ActionBatch-load baselines from PostgresPostgres
- LogicDiff each epic and rank by growth
- OutputEmail ranked drift digestGmail
What it does
Instead of per-edit pings, this workflow gives leads a calm weekly readout of where scope has crept across the whole portfolio. Every active epic is compared against its kickoff baseline, the additions are quantified, and the results are ranked so the biggest silent expansions surface at the top. The output is one digest email a program manager can act on in their Monday review.
When to use it
Use it when per-change alerts are too noisy and you want a manageable cadence. It suits PMs and EMs running several squads who need a portfolio-level view of requirement growth rather than ticket-by-ticket notifications.
How it works
- 1A weekly schedule triggers the run.
- 2All epics in active states are pulled from Linear.
- 3Their stored baselines are loaded from Postgres in one batch.
- 4Each epic's current criteria are diffed against its baseline and an added-lines delta is computed.
- 5A branch keeps only epics that grew beyond a configured threshold and ranks them.
- 6A formatted digest is emailed to the leads distribution list.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GmailRead, draft, send, label.
- 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
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.
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.
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.
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…
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.