Can anybody help me? So I followed a lot of the steps and I got all the way to visual studio code and I’ve started creating agents. However, I’m not sure that I’m doing it correctly because I am hitting my limits with visual studio code maxing out at 99%. However, by following your instructions and chatting with Claude through my terminal. I don’t blow through my Claude limits. Claude within my terminal builds, markdown files and folders underneath my company that I’m building, but I seem to be confused on how they connect and I need guidance if anybody wants to chime in.

Before ICM I called it a "Prompt Modifier". At it's core, a markdown file, instructions to tell AI how to operate with the task at hand. This isn't building agents, it's the how, with a handful of instructions. At a high level, the Orchestrator manages handing off work to subagents. Built to be LLM agnostic, drop in to any chat, point to the file, or wire it into ICM with a trigger when needed. The main chat stops doing all the work and instead organizes, delegates, and manages communication. I've seen this catch a lot of errors, assumptions and hallucinations. Plans are better. Execution is improved. This also allows higher level model usage, without all the token costs. I'm usually using Opus, on high effort. --- An analogy I used when sharing with my brother-in-law, military vet. Think of Claude like a Team Leader. - Claude manages the agents instead of doing the work himself - A "research agent" is sent out to get the information and bring it back - Claude writes up the assignment, then sends a "worker agent" to do it and report when it's done - Then a "verification agent" checks that the worker actually did the job right - If it didn't, Claude keeps working the agents until it passes So if you're not getting what you want, talk to the Team Leader and tell him to fix his sh*t. --- I've used a version of this over the last 3+ months, it has helped cut down on token usage, while getting what I need done quicker. Building this into my ICM system has been a force multiplier. If you use this I would love some feedback to add to my backlog, still iterating on it. *Attached slide with some additional detail.

This comes straight from the ICM method (I asked Claude to explain to me), so none of it is my invention. But seeing the five forms written out as plain shapes made the whole system land for me, and I'm actively building with it right now, so I wanted to share it the way it clicked. Every ICM workspace is one of five shapes, or a mix of them: 1. Pipeline. Same steps, run over and over, new deliverable each time. Think of a recurring 30-page client document: data in, checks run, sections drafted, reviewed, published. One folder per step, numbered in order. 2. Umbrella. Several different workflows that share one brand, voice, and reference layer. One shared folder holds the facts (brand guide, company snapshot, templates) and every workflow points at it instead of keeping its own copy. One home per fact. 3. Record library. The unit is not a run, it is a thing that accumulates: a client, a lead, a property, a patient. One folder per record, growing over time. The trap here is tracking status by moving files between folders. A status log inside the record is cleaner. 4. Knowledge bundle. The product IS the organized knowledge. A wiki, a second brain, course notes. The value is that a person or an agent can walk it and find things. 5. Context map. The subject is a whole organization. Teams, processes, where everything lives, and a small routing file at the top that answers "where does X go" in one read. The part that surprised me: they compose. My real setup is a context map at the top, holding an umbrella of shared facts, containing pipelines, publishing into record libraries. That's not breaking the rules. That's the normal case. One warning from experience: don't build folders for work you might do someday. I once built a beautifully organized workspace for future tasks, and it sat empty forever because nothing real ever flowed through it. Start with what "done" looks like (a phrase I picked up from @Ari Evergreen. If you can name the deliverable that comes out the other end, and you're already producing it the painful way, build the structure around that. That workspace gets used on day one, because the work is already there waiting for it.

I just realized that the way I’ve been organizing files my entire life whether it’s on a thumb drive in my phone or on a computer was always a ICM methodology. I know this sounds crazy because obviously ICM and Jake are new to me. As I looked stress stressed out on how my harness and AI model where organizing all the information I gave them about ICM. I took a break and watched a couple movies and as I was looking through my picture folder and looking at my computer, I had this epiphany. The next step was to re-organize my folders with the terminology of an ICM folder for AI to read and me understand before completely screwing up something and getting lost in the sauce. Next- Add the .md addition to the sub folder system, same concept different media.

I am running a business B2B but curious about adding more brains for each skill. Most of you already good at folder structures and using it, what if you had to build a new business what folder structure you will made? Such as Branding.md, Email Writing, Objections handling etc etc. Would love to see your examples!