rindig/icm-architect ? reverse-engineered prompt

Build me a Claude skill that can take any process, idea, or existing folder and turn it into an ICM workspace. I want it to figure out the natural stages, the stable parts versus the parts that change each run, then create the smallest folder structure that makes the work easy for an agent to follow and easy for a person to inspect.

It should also be able to look at an existing repo or vault, classify what each file is doing, suggest a migration plan, then restructure it safely and check that the result still makes sense. Please include a few reusable starter templates for the common workspace patterns, like a pipeline, a portfolio of work, a record library, a knowledge hub, and a map of an organization.

Make it feel practical, with clear instructions, good defaults, and a simple way to verify that a fresh agent can understand the workspace just by reading the files. If you need anything current from the docs, look it up online.