AI flow kinda self improvement

I just wrote an ICM workflow: Ai-enhancement.

What does it do? Keep track of my Claude Code sessions - every turn! Plus my tool calls, every one of them. Then I process them with the ICM and finally I get a curated list of 'useful' sessions that can surface new workflows, or confirm the ones that are working just fine to share with my team or all of you. The best ones are the 'one turn' session. Cheff kiss! the dream! the golden standard!

What I learnt from here:

I won't get out of the chat anytime soon - it is my wandering space.
I don't need to 'ship' my products for validation. The fact that day to day those workflows are ran means they either work or need refinement.
Confirm that whenever the output is wrong, fix the harness! Fix your ICM, your rules, prompts, scripts.
Use A LOT of scripts., create manifests, programmatically choose your batches, and use hard deterministic gates.
Clean your data - JSON is not always the way, but also is not always NOT the way.
Have fun!
Ahh - and have a self healing process for 'fixing the harness'. Spoiling alert: evals work

This is kinda meta: is an AI workflow to fix my AI workflow and it feels great. I'm a power user of our CLI tool (built on top of Claude Agent SDK), and still I couldn't find a way to share why I'm finding better and better ways to use AI on a daily bases. This is the answer: read all my sessions, tag them, group them, and surface them. A small weekly post will make the difference and I hope it could help one of my coworkers.

And just how the influencers go: if you find this interesting and want to talk about the full process, let me know in the coments BELOW lololol hope

@Bas Rosario

is not mad at the percentage of AI intervention in this flow - but is a bunch of judge and reasoning. Which I'm kinda glad!

0 comments

AI flow kinda self improvement