ICM-Architect great but ... what does it need?

I am the biggest fan of the ICM-architect and I have been running many projects hours on end in parallel that all started with building the ICM structure and routings via the ICM architect. Most of my projects are pretty similar either software, hardware/IoT or business and the architect offers robust routing and coordination of the projects. A few things I noticed:

Similar project but gets completely different ICM structure (still gets the job done)
New project assumes information off one running in parallel
Some run fully autonomous goal-based and others require constant YES-ing

I dont want to go and read all md files anymore (we are lazy)

What would you add to make it behave in the same "structured" way like how ICM was intended to be?

Share your ideas

4 comments

ICM-Architect great but ... what does it need?