ENGINEERING
Stale Flag to Linear Tech-Debt Ticket
Scans GitHub for feature-flag definitions older than a threshold whose flag-service config shows a settled state, then files one Linear ticket per stale flag with owner, age…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts run
- ActionScan repo for flag definitions, ages, and refsGitHub
- ActionFetch flag state and last-changed from PostgresPostgres
- LogicKeep only old, settled, still-referenced flags
- OutputCreate tech-debt ticket per stale flagLinear
What it does
Turns lingering feature flags into tracked work instead of silent debt. It pairs flag definitions found in code with their live state from your flag service and creates a Linear issue for each flag that has clearly outlived its experiment.
When to use it
Use it weekly when you want flag cleanup to show up in sprint planning rather than relying on memory. Good fit for teams that already triage tech debt in Linear.
How it works
- 1A weekly schedule starts the run.
- 2Scan the GitHub repo for flag definitions and capture each flag's creation date from git blame and its reference count.
- 3Fetch each flag's current state and last-changed timestamp from the flag-config Postgres store.
- 4A logic step keeps only flags that are old, fully settled, and still referenced in code.
- 5Resolve the likely owner from the file's most frequent committer.
- 6Create a Linear ticket per stale flag tagged tech-debt, with age, owner, and call-site count in the description.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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 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.