ENGINEERING
File Linear Cleanup Tickets for Aged-Out Feature Flags
On a schedule, identifies flags older than a configurable age threshold and creates a deduplicated Linear issue for each, assigned to the owning team with flag age, rollout…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule triggers the scan
- ActionQuery Postgres for flags older than 60 days with owner teamPostgres
- LogicCheck Linear for existing open issue per flag keyLinear
- ActionEnrich with GitLab code referencesGitLab
- ActionCreate Linear cleanup issue for each new flagLinear
- OutputReport created vs skipped ticket counts
What it does
Scans the flag registry for flags whose creation date exceeds an age threshold (default 60 days) regardless of rollout percentage, then files a Linear issue per flag in the owning team's backlog. It dedupes against existing open tickets so reruns never spam the board.
When to use it
Use this when you want flag cleanup to live in your normal sprint planning rather than as auto-generated MRs. It is ideal for teams that prefer a human to decide whether a flag should be removed, kept, or escalated before any code changes. The age threshold catches both fully-rolled-out flags and abandoned experiments stuck at low percentages.
How it works
- 1A nightly schedule triggers the run.
- 2Query Postgres for flags created more than 60 days ago, joining the owner-team mapping.
- 3For each flag, check Linear for an existing open issue with the flag key to avoid duplicates.
- 4For new flags, look up code references via GitLab search to enrich the ticket.
- 5Create a Linear issue per undocumented flag, set the team, priority by age, and paste rollout state plus file references.
- 6Emit a summary count of tickets created versus skipped.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.