AI AGENTS
Split a story on demand from a Slack slash command
A team member runs a Slack command with a Linear issue ID; the agent reads the issue, proposes a split into smaller stories with criteria.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command with issue IDSlack
- ActionFetch issue details and estimateLinear
- ActionPropose child stories with criteriaOpenAI
- ActionPost interactive split preview in threadSlack
- LogicWait for confirm or cancel
- OutputCreate linked child issues in LinearLinear
What it does
This agent puts story splitting one Slack command away. A developer or lead invokes it with a Linear issue ID when a story feels too big to start. The agent reads the issue, proposes a decomposition into smaller stories with draft acceptance criteria, and replies in the thread with a preview. Nothing is written to Linear until the requester confirms.
When to use it
Use it for just-in-time grooming during standup or planning, when someone realizes a story is oversized and wants a fast, reviewable split without leaving Slack. It complements scheduled grooming by handling the ad-hoc cases.
How it works
- 1A Slack slash command fires with a Linear issue ID as its argument.
- 2The agent fetches the issue's description, criteria, and current estimate from Linear.
- 3An LLM proposes 2-4 child stories, each with acceptance criteria and a point estimate.
- 4The agent posts the proposed split as an interactive preview in the Slack thread.
- 5A logic step waits for the requester to confirm or cancel.
- 6On confirm, the agent creates the child issues in Linear linked to the parent and replies with the new issue links.
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
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.