Trello makes it easy to add a card and hard to make anyone think about it. The board fills up because adding is frictionless, and it stays full because analysing is not.
What it does
- Drag a card into your analyze list, and the AI posts a repo-grounded analysis as a comment.
- Discuss it right there in the card comments, and it replies and tightens the scope.
- Drag it into your build list, and it opens a pull request.
- The relay picks up every board action, so nothing you do on the board is invisible to it.
What it will not do
It never drags cards between lists, archives them, or merges what it opened. Lists are moved by people — which keeps the board an honest record of what humans decided rather than a log of what a bot did overnight.
Where the state lives
There is no database behind this. Per-card state is JSON on an orphan git branch, so it is fully inspectable, versioned for free, and travels with the repository. If you ever want to know why the agent did something on a card three weeks ago, it is a git log away.
Setup takes about five minutes
Clone the repo, run ./setup.sh, pick Trello, and answer a few questions — your IDs, your tokens, your conventions. The installer copies the recipe into your repository, sets your secrets, and prints whatever manual steps are left with your real values already filled in. No server to host, no database to run, nothing to pay for beyond the AI you already use.
Honest status: beta. It is built and smoke-tested, and it carries a live-fire checklist in its README that I am working through one tool at a time. It is waiting on real boards to prove it. If you hit an edge, open an issue — that is exactly what the beta label is asking for.
The recipe is MIT-licensed and open source: ai-automations. It is one of 35 — see the series overview for the full list and the rules every recipe follows. If your tool is not on the list, name it and I will build the automation for it, free.
FAQ
Can it drag cards between lists?
No. It never moves cards, archives them, or merges what it opened. Lists stay an honest record of what people decided.
Does it need a database?
No. Per-card state is JSON on an orphan git branch — inspectable, versioned for free, and it travels with the repository.
Does it see everything on the board?
The relay picks up every board action, so nothing you do on the board is invisible to it.
More in this series: Slack · ClickUp · all 35 automations
Working on something similar?
If you are wiring AI into the tools your team already uses, I am happy to look at it with you. Thirty minutes, no deck — bring the workflow that costs your team the most time and we will work out whether it is automatable. Get in touch.