PROJECT MANAGEMENT
Linear Epic Acceptance-Criteria Drift Detector
Snapshots a Linear epic's acceptance criteria at kickoff, then on every edit diffs the live description against the baseline and posts a Slack alert when criteria were silently…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue updated webhookLinear
- LogicFilter to locked epics with changed description
- ActionFetch kickoff baseline criteriaPostgres
- LogicDiff current criteria vs baseline
- OutputPost drift alert to SlackSlack
What it does
This workflow watches a Linear epic after it has been committed to and catches when its acceptance criteria quietly expand. It keeps a frozen baseline of the criteria captured at kickoff, and any time the epic description changes it compares the current criteria against that baseline. If lines were added, removed, or reworded, it posts a clear before/after diff to the squad's Slack channel so the change is seen and acknowledged rather than absorbed.
When to use it
Use it on committed-to epics where scope has been locked for a sprint or release. It is for teams who keep losing predictability because requirements grow inside the same ticket without anyone re-estimating.
How it works
- 1A Linear webhook fires when an issue is updated.
- 2A filter checks the issue is a kickoff-locked epic and that its description body actually changed.
- 3The stored baseline criteria for that epic are fetched from Postgres.
- 4The current acceptance-criteria block is extracted and diffed line-by-line against the baseline.
- 5If meaningful additions or edits are found, a formatted diff is sent to Slack tagging the epic lead and reviewers.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.
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.