So this one is the ultimate Clief Notes community bringing disparate threads together post. So reader, consider this your warning upfront. @Alyshia Perri and I were talking and she was keen to get feedback on her entry in the coach competition. I tried to do that in DM to begin with, and then realised I was babbling. I asked her permission to fork it and make my edits so I could *show* her what I was trying to describe and she gave me that permission. None of the rest of this happens without her and she also gave me permission to post this. So here’s a brave woman who’s willing to let me link to a repo showing how I messed with her baby because I couldn’t find better words for the teaching. Please tell her how awesome she is, because that is *gutsy*. One of the coaching offerings in this repo was “board mode” which runs an idea past three different perspectives, each with a different agenda and angle of attack to help the user. I’m going to be upfront and say these sorts of mechanics in AI are generally not to my taste for a bunch of reasons. I don’t think they are effective, let’s keep it to that. But on my mind was the recent podcast by @Curtis Hays and @Brooke Hays showing the impact of using Jungian thinking archetypes / Myers-Briggs profiles to genuinely give the way agents approach things different flavours. What I did: - I got the model to do a sub-agent pass first using the roles as written - I took the three roles as stated and identified which profiles applied to these roles from my point of view - the skeptical stakeholder got “ESTJ”, the peer who has been burned got “ISFJ”, future self got “INFJ”. Then we did it again and compared the outputs - I added two new roles that I felt were missing - the logic stress tester (INTP) and the values-holder (INFP) - I felt off the results of these that Amund as the synthesiser was missing a trick. I tried two separate synthesis passes (over the first rounds, the second round, and all five together) - one using an ENFJ synthesiser and another using an INTJ one.

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.