I am not new to software or AI, but have been trying to wrap my head around ICM for a while. Recently ran the script-to-animation workflow, asked it to make up a silly theme. Whadaya know, it worked. :) What I'm interested in, though, is whether ICM can be used for full SDLC. Let's say a game. Hypothetically (wink, wink.) Having trouble figuring out how to break it down, and if the middle "loop" (implement features until done, to oversimplify it) even fits ICM. The planning could probably be a workflow, at least. So I don't know if that should be split off as a separate workflow, create specs, and then - what? Has anybody used ICM for end-to-end software development? Did it work? Challenges? Tips?

I have been using Claude Code, Cowrk, and Chat for more than 2 years. I built my existing folder structure before Cowork was even a thing, so all of my AI project folders are on my root folder where Documents, Desktop, Downloads, and the other system folders are located. By the time Cowork was released I had already built several apps with repos, databases, and deployments that relied on my current folders staying right they were or I would have to rebuild everything. Now I'm trying to modify this mess of a structure, which as a global ~.claude/CLAUDE.md file that is now over 1MB, which by markdown file standards is the bloat of all bloats. I just updated the icm-architect skill to use AGENTS.md files instead of CLAUDE.md, but in the global hidden folder, this does not work, because it is ONLY Claude specific. So, as I'm making these changes I'm getting pushback from Claude. The biggest is routing. Here's my question. Claude code uses the .claude folder, so I can't get around this. Should the CLAUDE.md file be a duplicate of the AGENTS.md at the ~root folder, in my case? Right now my ~/AGENTS.md file has 11 global rules, mapping to all the project folders, and instructions to use the icm-architect skill for creating new projects.