DEVOPS
Quarterly flag-debt report with agent-routed owner actions
Quarterly, an agent inventories every feature flag, scores each for staleness and risk, opens cleanup PRs for clear wins, files Linear tickets for the ambiguous ones.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly schedule launches the agent
- ActionLoad full flag inventory with usage statsHTTP webhook
- LogicAgent scores and classifies each flag
- ActionOpen cleanup PRs for auto-clean flagsGitHub
- ActionFile Linear tickets for needs-decision flagsLinear
- OutputDM each owner their personalized punch listSlack
What it does
Produces a per-quarter feature-flag debt review and acts on it. An agent pulls the full flag inventory, scores each flag on age, rollout state, and evaluation volume, then routes by confidence: clean rollouts get an automatic GitHub cleanup PR, judgment-call flags get a Linear ticket for human decision, and every flag owner receives a Slack DM summarizing exactly which of their flags need attention and why.
When to use it
Use it for a standing quarterly flag-debt ritual where you want triage decisions made, not just a dashboard. Best when flag ownership is spread across many engineers and you need each person handed a short, personalized action list rather than one giant report nobody reads.
How it works
- 1A quarterly schedule launches the agent.
- 2An HTTP call loads the full flag inventory with usage stats.
- 3The agent scores and classifies each flag as auto-clean, needs-decision, or keep.
- 4GitHub opens cleanup PRs for the auto-clean flags.
- 5Linear files tickets for the needs-decision flags.
- 6Slack DMs each owner their personalized flag-debt punch list.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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 DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.