I've been working on this and have something that somewhat works, but I keep running into pieces that get messy and don't hold up well in practice. My current approach: the image I've attached lives in my AGENTS.md at the root of the project, so any time I build, the AI has the structure to reference. What I'm really after is the best way to implement the ICM system so that anything I build, Claude/AI already knows the way to build and stays inside that structure. Is anyone else doing this? Would love to hear how you've set it up.

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.

We run a startup and we've been using Obsidian as our company knowledge base. Great tool but there's one big gap, no security. Everyone with vault access sees everything. API keys, strategy docs, client info, all wide open. And when you connect AI tools they burn through tokens reading raw markdown with all the noise. We ended up building a plugin called VaultGuard that adds encryption and access control to Obsidian. Built it for ourselves first, now we are testing it. If anyone else ran into this, how do you handle sensitive info when sharing an Obsidian vault with your team? And if you're interested in VaultGuard let us know, we'd love to hear your feedback.