AI AGENTS

Split oversized Linear epics into estimated child issues

An agent scans newly created Linear epics, breaks each one above a size threshold into discrete child issues with point estimates and acceptance criteria.

CategoryAI Agents
Enginepaperclip
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLinear epic created or updatedLinearLinear
  • LogicSkip if epic already groomed
  • ActionOpenAI decomposes epic into child issuesOpenAI
  • LogicValidate breakdown and estimates
  • ActionCreate estimated child issues under epicLinearLinear

What it does

When a Linear epic crosses a size threshold (too many points, no children, or a long description), an agent decomposes it into 4-8 concrete child issues. Each child gets a title, a short scope, acceptance criteria, and a story-point estimate, and is linked under the original epic so the team can plan immediately.

When to use it

Use when product or engineering leads keep filing large "do the whole feature" epics that sit ungroomed until sprint planning. This does the first-pass breakdown so refinement meetings start from real, estimated tickets instead of a blank epic.

How it works

  1. 1A Linear webhook fires whenever an issue labeled `epic` is created or updated.
  2. 2A logic step checks the epic against thresholds (estimate, child count, description length) and exits if it is already groomed.
  3. 3The epic title and description are sent to an OpenAI model that returns a structured list of child issues with estimates and acceptance criteria.
  4. 4A logic step validates the breakdown (no duplicates, total points sane).
  5. 5Each child issue is created in Linear, parented to the epic, with labels and estimates applied.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.