AI AGENTS
Cross-Team Dependency Detector from Standups
Reads each team's Loom standups and commit activity, detects when one team is blocked waiting on another.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily multi-team schedule
- ActionFetch cross-team Loom standupsLoom
- ActionPull commit/PR ownership signalsGitHub
- ActionMap cross-team dependencies with LLMOpenAI
- LogicSkip if no external dependency
- OutputNotify owning team in MS TeamsMicrosoft Teams
What it does
Finds hidden cross-team dependencies buried in async standups. It reads standup transcripts and recent commit activity across multiple teams, identifies statements where one team is waiting on another team's work, and notifies the team that owns the dependency directly in their Microsoft Teams channel, so the blocker reaches the people who can actually unblock it.
When to use it
In orgs with several squads where standup blockers often name another team, but that other team never hears about it until it's escalated. Use this to close the loop automatically.
How it works
- 1A daily schedule fires after all teams' standup windows close.
- 2Fetch the day's Loom standups across the tracked teams.
- 3Pull recent GitHub commit and PR activity to ground who owns what.
- 4An OpenAI step extracts cross-team dependency statements and maps each to the owning team.
- 5A logic step skips when no external dependency is found.
- 6Post a targeted heads-up to the dependency owner's Microsoft Teams channel.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect Microsoft TeamsChannels, chats, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.