Following along here, I have just secured a very large project. "Turn our messy internal documents into an ICM system allowing us to automate large swathes of manual admin". Before I met with the prospect, I'd been re-watching and reading everything that's going on in this community. I wouldn't have had the confidence or baseline knowledge to approach a project like this without this group! I wanted to pass on a huge thanks to Jake and the team. I'll share what I am building (as much as I can) and no doubt I will have a ton of questions!

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.

Post your results! My daily ICM puzzle game. Test your foundations knowledge by fixing a new broken workflow every day! http://donsbookshelf.com/icmadness/

If you’ve been quietly struggling with learning how to build or what to build, you’re not alone. I’ve seen the posts, and I know how frustrating it can feel when things don’t click. I wanted to try to do something about it. I built a custom AI Tutor that has the complete knowledge and teaching style of @Jake Van Clief and @Matthew Creamer’s Foundations courses. Think of Jake as the professor. This agent is your dedicated Teacher’s Assistant who sits with you one-on-one. See the new V2 Foundations Tutor here! https://www.skool.com/cliefnotes/new-v2-foundations-tutor?p=979dbf61 Here’s why it’s different: • It walks you through every concept step by step, exactly as Jake outlines them • You’re not just chatting or watching videos. You’re actually building files and folders together in Claude • It checks your work in real time and won’t let you move forward until you truly understand • It speaks in their voice and follows their exact methodology This is the hands-on practice and patient guidance a lot of us have been missing. How to try it: 1. Grab the repo 2. Follow the README 3. Open the folder in Claude and let the tutor take over I’m very proud of how it turned out and I want this to help as many people as possible. We just crossed 30,000 members! Let’s make sure every single one of us has the support they need to actually master this stuff. If you try it, please drop a comment and let me know: • Did it help you understand a concept that was confusing before? • What worked well? • What could be better? I want your honest feedback so we can keep improving it together. I’d love it if this could turn into a proper community teaching tool we all build and evolve. Link in comments 👇

You just saw how the folder structure adapts to different use cases. Vote below, then drop your customized setup in the comments. What did you name your workspaces and why?