Last week, I tried out Jake's icm-architect skill, which he also posted here. There were a few legitimate issues the skill found that needed fixing, and I quickly patched those in my infrastructure. What surprised me, though, was that the structural part itself (which I built before I joined here and started learning about Jake's ICM methodology) was not only completely fine, but when applied to my use case, it was even better than what the skill suggested. Jake's skill is set up for fairly general use cases, as well as for people who don't know how to organize a specific idea or project in a way that works well for agents. After I patched the holes the icm-architect skill found, I gave it some thought and created my own version. I named it Agency ICM Builder. https://github.com/krsnczky/agency-icm-builder The difference is in what it assumes. One folder per client, and keeping them apart is rule two, not an afterthought: any learning whose client is ambiguous goes to a quarantine inbox instead of getting guessed into the wrong folder. In an agency, cross-client bleed isn't untidy, it's a liability. Expertise and state are split the same way, by construction. Departments hold what's true for a service across every client, client folders hold per-client state, and the two never mix. A few weeks ago, I posted here about my memory system, for which I created a public plugin, and this new skill complements it perfectly. You could say the memory kit is the soul/brain of my infrastructure, and this skill helps you build the body around it. Once you plug the memory kit in, you'll have a very strong foundation for your infrastructure. https://github.com/krsnczky/agency-memory-kit It won't fit everyone. If you're not doing client work at all, the client separation is dead weight and Jake's icm-architect is the better starting point. And if you want a framework with a database and orchestration code, this isn't that either. It's markdown files in folders, and that's the whole design.

First session done. Vote below, then drop your OS and any issues you hit in the comments. If you got stuck, someone here has probably solved it already.