Sharing Pieces of My AI Agent Workflow
Why I stopped writing about it
I had given up on writing about my progress with AI agents for a while.
Not because I stopped experimenting. Quite the opposite.
The problem is that everything changes too fast.
Every time I felt close to describing my workflow, I would improve something, replace a tool, change a prompt, adjust a habit, or discover a better way to interact with the agent. The idea of publishing a “complete workflow” started to feel wrong, because I knew it would become outdated almost immediately.
And I did not want to create an exhausting commitment for myself: writing a post today, then feeling forced to update it every time my process changed.
Why I did not want to sound prescriptive
There was another reason too.
I did not want to sound like I was trying to impose a workflow.
My biggest discoveries with AI agents have been very individual. They did not come from a perfectly synchronized team process. They came from trial and error, from frustration, from curiosity, from small improvements, and from many moments where I had to rethink how I work as a software developer.
So, for some time, I preferred not to write about it.
What changed my mind
But recently, after watching the podcasts from Kent Beck - Still Burning, I felt a strong desire to contribute more openly to this revolution that is happening.
AI agents are changing software development, but not only because of the tools themselves. They are also forcing us to rethink discipline, feedback loops, communication, design, testing, and the way we describe intent.
And I do not want to be only a consumer of this change.
I want to contribute to the conversation.
Maybe by sharing parts of what I am discovering, I can help someone else. And maybe, by making these ideas public, I can also accelerate my own learning through external insights, criticism, and suggestions.
A better format
So I started thinking about a better format.
Instead of trying to publish my entire workflow as if it were a recipe, I decided to share smaller steps from it.
- Pieces.
- Practices.
- Decisions.
Things that can be adapted, improved, questioned, or absorbed into someone else’s workflow.
That feels much more honest to me.
What I want to share
A complete AI agent workflow is too personal and too unstable to be treated as a final answer. But specific ideas can still be useful. A way to prepare context. A way to ask for changes. A way to review generated code. A way to avoid losing control. A way to keep tests and design as the center of the process instead of blindly trusting the agent.
That is what I want to share.
Not a definitive workflow.
Not a universal method.
Not “this is how everyone should work with AI agents.”
Just pieces of my current process, shared while they are still alive, still changing, and still being tested in real work.
I will start doing that soon.