ENGINEERING
Flag a stalled GitHub PR that is blocking a committed Trello delivery card
When a GitHub pull request linked to a date-committed Trello card sits without review past a threshold, it moves the Trello card to a Blocked list and alerts the dependent team…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scan of PRs linked to Trello cards
- LogicKeep PRs stalled in review past threshold
- ActionMove Trello card to Blocked and commentTrello
- ActionResolve downstream team awaiting the cardTrello
- OutputAlert dependent team in SlackSlack
What it does
This workflow connects code review reality to delivery commitments. When a GitHub pull request that is tied to a Trello delivery card has gone too long without a review, it marks the Trello card as blocked, recording why, and tells the team waiting on that card in Slack that the slip is review-driven.
When to use it
Use it when engineering hand-offs are tracked on a Trello board and a PR languishing in review quietly puts a committed date at risk. It makes the cause of the slip (a stalled review) visible to the people downstream instead of letting the card look 'on track' until the deadline.
How it works
- 1A scheduled check evaluates open GitHub PRs linked to active Trello cards.
- 2A filter keeps PRs that have had no review activity past the stall threshold and whose Trello card has a committed due date.
- 3For each, it moves the Trello card to the Blocked list and adds a comment citing the stalled PR.
- 4It resolves the downstream team waiting on that card.
- 5It posts a Slack alert explaining the card is blocked on review, linking the PR and card.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect TrelloKanban boards for everything.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.