This has been one question i have always asked and kept trying to understand until recently. I've seen it asked and discussed multiple times here... So i decided to combine, study and comprehend the various perspective of those who have shared how they are using it @Curtis Hays and many others, to come up with a simple way for me to implement. Here is my personal understanding: Say we are four people in the marketing department, and i am the only one who has built an content pipeline using the ICM framework, now i want onboard the other 3 coworkers and you're one of them... lol 😀 We have one master system, the original pipeline i'm using is now hosted on GitHub (with the same agent.md and context.md, rules and stages). Step 1: Getting the System on Your Computer You copy/clone the entire workspace from the internet (GitHub) to your PC. This gives you the same folders I have: 01-ideas 02-drafts 03-formats etc Step 2: Creating Content Open your copy of the workspace. Talk to ai agent while in the folder normally. Example conversations: “Give me ideas for LinkedIn posts about productivity” “Turn idea number 4 into a full draft” “Format this draft for Instagram carousel and Substack” The agent uses the shared system I built, so all our content has the same style and quality. Step 3: Sharing Improvements If you create a better prompt or improve one of the stages: Tell the agent: “I improved the carousel format, make a Pull Request” I (or the content lead) will check it. Once approved, everyone gets the improvement automatically. Step 4: Where Files Live Your ideas and drafts: Stay on your computer (or save final versions to the department Google Drive, which we all have access to). The framework (how we create content): Lives in the shared system (Github). - What You Need to Do Install Git (one time, easy). Clone (copy) the workspace. Use AI agent within the folder workspace.

What do you wish you understood better? 👇 I want to hear from everyone. Every level. Day one or day one thousand. There's no question too small, too basic, or too "I feel like I should already know this." If you've ever wondered how something works, what something means, or how to do it, that's exactly what I want. Two quick things 👇 1️⃣ Vote in the poll for the big topics you want more of. 2️⃣ Drop your specific question in the comments. The more specific, the better. The comments can serve as building a list from your answers. The creators in this group are incredible, and once we know what you're asking for, we can make the content that answers it. (This is a post aimed at helping all of us make more engaging content) Even if you mostly read and rarely post, this is an opportunity to have someone write about something you may not have an answer for. One question from you might be the exact thing ten other people were too shy to ask. 😊 We learn together, we grow together, we win together! 🤓💪🏆Bas Question: What do you want us to make more content on?

Quick recap, because this is "part 3" following @Bas Rosario 'cake' post and my first follow up. Thank you @Brendan Tucek. Your post is what got me thinking about this 3rd part. Bas taught us to break the cake into ordered steps, one instruction per folder. My follow up post zoomed in on the step that checks the cake — the toothpick, the gate. This one is about the part nobody warns you about until it shows up on the bill: cost. Here's the symptom. Someone in here recently posted a folder system that genuinely works, doing real work in their business, and then admitted the part most people don't: it burns a lot of tokens just figuring out where to look. 🪙 If you've built anything past a toy, you've felt this. The structure is fine. It's getting slow and expensive anyway. 💸 Here's where it comes from. In most ICM setups there's one file the AI reads before every single task. The map. The "you are here" file. Every word in it gets paid for on every interaction, whether the task needed it or not. And that file has a way of growing. You add a rule, then a note, then the whole folder tree, then some history, and one day your always-open page is a 3,000-word document. Now the model re-reads a small book before it cracks the first egg. Every time. 🥚 The fix is the oldest trick in any real kitchen: 'mise en place'. 🧑‍🍳 You don'tdrag the whole pantry onto the counter to make one cake. You bring out what this step needs, and everything else stays in the cupboard until it's called. For your folders, that means the always-loaded file is an index, not the recipe. It points. "Buyers live here. Follow-ups here. Voice guide here." 📇 One glance, then jump. The actual detail lives down in the step folder that only opens when the AI is standing in it. Whoever needs the frosting technique walks to the frosting folder. They don't carry the frosting instructions around all day in case it comes up. So the through-line of all three posts is one discipline pointed at three different things.