AI AGENTS
On-demand epic split triggered from Slack
A teammate pastes a Linear epic link into a Slack command and an agent splits it into estimated child issues on the spot.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command with epic linkSlack
- LogicParse and validate epic ID
- ActionFetch epic from LinearLinear
- ActionOpenAI proposes estimated child issuesOpenAI
- ActionCreate child issues under epicLinear
- OutputReply with breakdown in Slack threadSlack
What it does
A teammate invokes a Slack slash command with a Linear epic URL. The agent fetches the epic, decomposes it into estimated child issues, creates them under the parent, and replies in the same Slack thread with the breakdown so the requester can confirm at a glance.
When to use it
Use when grooming needs to happen interactively during a standup or planning chat, not on a schedule. Anyone can groom a specific epic the moment it comes up, without leaving Slack or opening Linear.
How it works
- 1A Slack slash command fires with the epic link as its argument.
- 2A logic step parses the epic ID from the URL and rejects malformed input.
- 3A Linear action fetches the epic title, description, and existing children.
- 4OpenAI proposes a set of estimated child issues with acceptance criteria.
- 5The child issues are created in Linear under the epic.
- 6A Slack reply posts the proposed breakdown and a link back to the updated epic.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect OpenAIModels, embeddings, files.
- 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
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.
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.
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.
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.
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.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.