DEVOPS
File Linear cleanup tickets for stale 100% flags with owners
Detects flags pinned at 100% for 30+ days and creates a Linear issue per flag, auto-assigned to the team that last touched it, with a removal checklist.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the run
- ActionRead flag rollout state from DatadogDatadog
- LogicFilter to flags at 100% for 30+ days
- ActionInfer owning team from GitHub commit historyGitHub
- LogicSkip flags that already have an open issue
- OutputCreate assigned Linear cleanup issueLinear
What it does
This workflow turns stale feature flags into owned, trackable cleanup work. It finds every flag that has been serving 100% for at least 30 days, figures out which team owns it from recent commit history, and files a Linear issue with a standard removal checklist so the debt lands on a real backlog with an accountable owner.
When to use it
Use it when flag cleanup keeps slipping because nobody owns it. Instead of opening code changes directly, this routes the work into your existing planning flow, letting teams schedule removals into a sprint and attach context.
How it works
A weekly schedule triggers the run. The workflow reads flag rollout state and last-change timestamps from Datadog, then filters to flags at 100% for 30+ days. For each stale flag it queries GitHub for the most recent author and team on the flag's references to infer an owner. It creates a Linear issue titled for the flag, assigns it to the inferred team, attaches a removal checklist and the metrics snapshot, and labels it flag-debt. Finally it skips any flag that already has an open Linear issue so reruns never duplicate tickets.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
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.