AI AGENTS
Weekly sweep that grooms stale epics and posts a Slack digest
On a weekly schedule, an agent finds every oversized or unbroken Linear epic, splits each into estimated child issues.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule before planning
- ActionFetch stale and oversized epics from LinearLinear
- LogicFilter out already-groomed epics
- ActionOpenAI decomposes each epic into estimatesOpenAI
- ActionCreate child issues under each epicLinear
- OutputPost grooming digest to SlackSlack
What it does
Once a week the agent queries Linear for epics that are oversized, childless, or stale. It decomposes each into estimated child issues, files them under their parents, then posts one Slack digest listing every epic it touched and the new ticket count, so the team walks into planning with the backlog already shaped.
When to use it
Use when you run a fixed planning cadence and want the backlog groomed automatically the morning before refinement, rather than reacting to each epic as it lands. Ideal for teams that batch-review work weekly.
How it works
- 1A schedule trigger runs every Monday morning before planning.
- 2A Linear action pulls all open epics matching the stale/oversized filter.
- 3A logic step loops the candidates and drops any already broken down.
- 4OpenAI decomposes each remaining epic into estimated child issues with acceptance criteria.
- 5The child issues are created in Linear under their parent epics.
- 6A Slack message posts a digest of every epic groomed, child counts, and total points added.
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 AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
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.