Hey, ran into something and curious if others have felt this too. I used the ICM method to build a tool. Staged pipeline, each step fed the next, worked great for getting the thing built. But now I'm realizing ICM feels designed for building fresh. If I want to build the same app for a different user, running the pipeline again makes sense. But if I want to edit the existing app, the pipeline docs are useless. They're stale and the agent has no efficient way to navigate the actual codebase. You need a completely different approach for editing. Less staged pipeline, more routing the agent around the live code so it knows where everything is. Has anyone figured out how to handle this transition? From ICM build mode to edit/iteration mode? Do you build an ICM around the edit/iteration mode as well ?

On April 10 I was trying to clean up my Instagram.Tighten the cover graphics. Build a repeatable system. Stop redesigning the same template every week. A one-afternoon job. What actually happened was the first real test of an architecture I had been sketching for writing work — and I tested it on design. I built a sandbox, gave it a governing file, separated references from working material, wrote one clean brief… and let it run. Fifty covers came back in minutes. Same palette. Same typography. Same visual language. None off-brand. That was the moment something shifted. Not because of the output — but because of what it proved: Once an architecture is clear enough, the question is no longer “what can I delegate?”It becomes “what is now worth building?” In 21 days, that small test turned into: - Three working teams (orchestrator, content, design) - Four books shipped or shippable - A new website - Two additional teams already scoped Same operator. Same hours in the day. For those who asked about mindset and process — this is the real answer: 1. I stopped thinking in prompts and started thinking in systems.The model is not the asset. The structure around it is. 2. I separated thinking from doing.The orchestrator doesn’t write. It reads, structures, briefs, and validates.The workers execute. They don’t improvise outside their lane. 3. Everything moves through briefs.No direct “do this” requests. Every handoff is:task → context → scope → acceptance → return checklist.That alone removed most iteration cycles. 4. Context is layered, not dumped.Reference material lives separately from working material.The model doesn’t have to “figure out what matters” — it’s already decided. 5. The human sits outside the system.Not inside prompting.Outside — validating outputs and deciding what ships. The clearest proof this wasn’t theory came from the hardest task I’ve ever tried to coordinate: Mapping TCM meridians, Thai Sen lines, and Anatomy Trains on the human body — in one consistent visual language.

​I often post about my wins with Claude Code or the progress on my book project, but there’s one part of the equation I haven’t touched on yet: Time. ​I’m lucky enough to be able to build a little during my work hours, but my primary focus is still being a Finance Manager. The real work happens when the house is finally quiet. ​But here is the reality: I have a 3-year-old and a 9-month-old. ​If you’ve been there, you know. My "second shift" starts after they are tucked in, but it’s always a gamble. Especially with a 9-month-old—you never really know how the night is going to go or how many times you’ll be woken up. ​The Internal Conflict: I’m a natural "A-person." I love waking up early and feeling fresh. But to get anything done on my private projects, I often have to push late into the night. ​I’m constantly trying to balance three things that all feel non-negotiable: ​Family Time: This is my fuel. I refuse to sacrifice being present with my kids. ​Sleep: As an early riser, I need sleep to function as a Finance Manager and a dad. ​Development: I have a deep drive to learn, build, and move my projects forward. ​The truth? Most days, it feels like I can only pick two. ​If I work late on a website or an automation, I’m a zombie the next morning. If I go to bed early to be a "good dad" at 6:00 AM, my projects stand still, which frustrates me. It’s a constant puzzle of trying to be "efficiently lazy" with the few hours I actually have. ​I don’t have a "5-step master plan" for this. I’m just navigating it one night at a time—sometimes winning, sometimes just trying to stay awake during a meeting. ​How do you guys balance this? For those of you with young kids, demanding jobs, and big goals—how do you find the space to create without burning out or missing the "golden years" with your family? ​I’m curious to hear how you prioritize when everything feels equally important. 👇