PROJECT MANAGEMENT
Weekly scope-creep digest across all epics to Confluence and Slack
Every Monday, ranks all active Linear epics by percentage point growth since kickoff, publishes a portfolio scope-creep digest page in Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule fires
- ActionFetch all active epics and points from LinearLinear
- LogicCompute growth percentage per epic and rank
- ActionGenerate digest narrative and table with OpenAIOpenAI
- ActionPublish dated digest page to ConfluenceConfluence
- OutputPost top offenders to program Slack channelSlack
What it does
Builds a portfolio-level view of scope drift. Each Monday it pulls every active Linear epic, compares current points to the stored kickoff baseline, ranks epics by growth percentage, and publishes a single Confluence digest page. It then posts the worst three offenders to your program channel so leadership sees the trend without opening Linear.
When to use it
Use it when you manage many epics across squads and need one weekly artifact for staff or steering reviews, rather than per-epic pings. Pairs naturally with the baseline-capture workflow.
How it works
- 1A weekly Monday schedule triggers the digest.
- 2Linear returns all active epics and their child-issue points.
- 3Each epic is matched to its kickoff baseline and a growth percentage is calculated.
- 4Epics are sorted descending by growth and OpenAI writes a short narrative plus a ranked table.
- 5Confluence publishes the full digest as a dated page.
- 6Slack posts the top three offenders with a link to the Confluence page.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.