SenseiSoloDev
Back to projects

Development tool

Personal tool · EvolvingUpdated

trello-sync

A CLI that turns Trello into an operational part of agent-assisted development. Tasks do not merely sit on a board: they follow the work from planning through validation and completion.

A real session
$ trello-sync move-card --key web-projects-tools-section --list doingWEB - Add a Tools subsection to projectsCard moved to DOING · Local state updated

The origin

Organisation needed to become part of pair programming too.

I have used Trello for some time to organise tasks across my different projects. Even so, there were plenty of situations where I ended up not updating it: from completing a quick unplanned change to discovering that one card needed to become several smaller tasks.

Since I already use AI as a pair-programming partner, I thought project organisation and documentation should become part of that same flow; in my case, mainly Trello and Obsidian.

I first reviewed the existing MCPs, but quickly saw a good opportunity to build something completely tailored to me. The result is a CLI that uses almost the entire Trello REST API while adding custom workflows that run several steps from a single instruction, board setups built around my preferences, an activity log, and a synchronised local copy that also lets me work offline.

And, of course, it means I no longer forget to update or comment on each thing I do.

The creation process

From testing the API to designing a workflow for agents.

The tool grew as I tried to use it for real rather than by following a fixed roadmap from the beginning.

  1. 01

    Start with the API

    The first step was simply making calls to the Trello API and confirming that the basic operations worked correctly.

  2. 02

    Think in workflows

    As soon as I started using it through agents, I saw that exposing individual commands was not enough: I needed workflows that grouped several steps and streamlined common tasks.

  3. 03

    Design for every new context

    Help and setup commands written with agents in mind became essential. I continue improving how they receive their initial context, although this part still does not work exactly as I would like.

  4. 04

    Experiment and know when to stop

    I also implemented things out of pure curiosity that I have not ended up using, such as sticker management. That exploration helped me pause development of the tool and return my focus to my games.

The workflow

One task, from the board to the repository and back.

The tool does not try to replace project work. It makes sure every step leaves a clear, verifiable signal.

  1. 01

    Understand

    Inspect lists, cards, descriptions, and context before touching the code.

  2. 02

    Start

    Move the card into its working state and keep a stable key between Trello and the local project.

  3. 03

    Build

    Development continues in the repository, with Trello acting as a visible source of intent and progress.

  4. 04

    Close

    After validation, record the result, complete the card, and leave traceability for the next context.

What it already does

An operational layer around Trello.

Its scope has grown from real day-to-day needs rather than from an abstract feature list.

01

Cards with stable identities

Relates tasks through keys that remain recognisable even when their list or title changes.

02

End-to-end workflow

Create, update, move, comment on, complete, and close cards without leaving the development context.

03

Diagnostics and reconciliation

Checks configuration, authentication, and differences between local state and what actually exists in Trello.

04

Plans that become work

Can synchronise Markdown structures and turn them into actionable cards on the board.

Project status

Useful today, with no decision yet about tomorrow.

I still do not know what I will do with the tool. For now, I use it every day across all my development projects, and it has gone several days without failing at anything I have asked it to do.

What it is today

  • A local tool integrated into the daily workflow of all my projects.
  • A project closely tailored to my conventions, boards, and way of collaborating with agents.
  • Software that already provides value even though it is not a public product yet.

What it could become

  • A more generic and configurable version for other teams or developers.
  • A public repository showing the project exactly as I use it.
  • A foundation for exploring stronger workflows between agents and project management tools.

Build to learn

First, it had to solve my problem.

This page documents the project as it evolves. If it eventually becomes a public tool, the path towards that point will be part of the story too.

View all projects