Let me preface with, I am fairly new here and really appreciate this community! The organization of ICM is what finally helped me start to grasp AI. Before that, I was working with PARA (projects, areas, resources, archive) as my way of organizing files for AI. For those familiar with PARA, how would you compare/contrast it with ICM? How do I use them together? Or is that not a thing?

Over the past few days, I’ve had some fascinating conversations here in this community, including a private chat with @Bryson Bossley . Those conversations got me thinking. And last night, I couldn’t stop thinking. One thought led to another. Ideas connected. Questions became bigger. And somehow, I ended up writing a speech and turning it into a video. So please, WATCH THE VIDEO FIRST. And if you recognize yourself in what I’m saying, if something in that message resonates with you… Come back and read this. ——— What Can We Build Together? 50,000 minds. Thousands of skills. Countless ideas. And yet… most of us are still trying to succeed alone. Think about that for a moment. What if the greatest opportunity in this community isn’t the next AI tool, another course, or another business? What if it’s the person reading this right now? Someone here might have exactly the knowledge you’re missing. Someone else might need exactly what you already know. And the strange thing is… Neither of you even knows the other exists. Isn’t that a tremendous waste of potential? I made this video because I believe we’re overlooking something extraordinary. It’s not another tutorial. It’s not a sales pitch. It’s a question we should all be asking ourselves. What could we achieve if we stopped trying to do everything alone and started combining what we’re already good at? Maybe we don’t need another thousand ideas. Maybe we need to connect the people who can bring them to life. And maybe it starts right here. Not with another complicated system. Not with another promise of success. But with people discovering each other. So let me ask you three simple questions. 1. What are you genuinely good at? 2. What do you need help with? 3. What would you build with others? Don’t overthink your answers. You don’t need to impress anyone. You don’t need to sell yourself. Just be yourself. Because somewhere among the people reading this, someone might have exactly the missing piece you’ve been searching for.

Where do I keep my reference files if I need to run a scheduled task during the night where that task needs access to those reference files? Claude is telling me my computer must be on. So I need another solution. Do you keep them in Notion or GitHub or some place else? If I have the on my terminal, I think that is the same as "on my computer", yes? These are files about my business and I'd like them kept private. Probably a very basic question for this crowd, so thanks for understanding!

I've been in this community for about a month now and wanted to share where things stand with one of my builds. This isn't polished by any stretch. I do have a few other workflows like content-creator, document-creator, but I needed something to help me navigate my day-to-day as I begin a couple side quests outside my normal 9-5. The goal was simple: I didn't want another chat window I have to remember to open. I wanted something that knows my priorities, reads my calendar, checks my email, and texts me when I need a nudge. Not a chatbot, more like a Chief of Staff. And the goal is to operate within the bounds of the subscription with no extra costs, while also maximizing token efficiency. The other thing I didn't want to do is implement an orchestrating harness yet (OpenClaw, Hermes, etc). The challenge for myself was to keep this as simple as possible without inflating scope. Someone in this community said once: 'constraints are just as, if not more, important than your requirements. What do you NOT want your build to do?' I've definitely taken this to heart in my workflows. ## Planning I've made a few posts about this in comments, but I cannot stress the importance of planning before you build. My method was simple: - First I brain dumped context via voice dictation and transcribed this. Simple tools: VoiceMemos, copy, paste. - Next, I worked through the planning phase with the chat function of Claude in Opus 4.6. I wanted pushback, challenge, and for the model to force me to think deeper and keep me honest. This produced the product requirement document, or PRD. This was a multi-day process (a week?) in my free-time. - For the architecture build, I used Cowork. Handed it the PRD, answered a few basic questions, and then it went on it's way. Got it uploaded to a private git repo. - Currently, I'm working thru further debugging and walking thru the checklist within the PRD in a phased approach. As you'll see below, I have setup a remote screenshare so I can also let Cowork see what I'm doing. This was the most essential because we work TOGETHER to make things happen. it's like working side-by-side with my developer and engineer.

Step-by-step interactive guide from idea to output. Design an ICM workflow alongside Maya, one decision at a time, and watch a messy process become something an AI can run again and again. Right now, Maya has to try to remember what needs to be done and where each piece of information is kept. She needs a better solution. https://claude.ai/public/artifacts/7c9618f4-8324-4048-902c-cbcf77c9c102 Let’s build one with her. 😀