ENGINEERING
Figma component deprecation sweep to Linear backlog
Scans your Figma component library on a schedule, finds components marked deprecated or renamed since the last run.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionRead Figma component library metadataFigma
- LogicDiff against last snapshot for deprecated/renamed components
- ActionSearch GitLab for stale component referencesGitLab
- LogicBranch: any references still present?
- OutputCreate grouped Linear migration issueLinear
What it does
Keeps your codebase honest about deprecated design-system components. On a schedule it reads the Figma library, detects components flagged deprecated or renamed since the previous snapshot, cross-references where the old names still appear in the repo, and files a single migration ticket in Linear with a checklist of every offending file.
When to use it
Run this when your design system evolves faster than your code. Teams that deprecate a `Button.v1` or rename `Card/Old` accumulate silent drift; this turns each deprecation into a tracked, actionable backlog item instead of a surprise during the next redesign.
How it works
- 1A weekly schedule fires the workflow.
- 2Pull current component metadata from Figma and compare against the stored snapshot to find newly deprecated or renamed components.
- 3A logic step filters to only components whose old names still exist in the repository.
- 4Search GitLab for code references to each stale component name.
- 5If any references remain, create a grouped Linear issue with a per-file migration checklist; otherwise exit cleanly.
- 6Save the new Figma snapshot for the next comparison.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.