What it does. Build workspaces where the folder structure does the orchestration. One agent, reading the right files at the right moment, replaces a multi-agent framework: numbered folders carry sequencing, hierarchy carries context scoping, plain markdown files carry state. A human can open any folder and see exactly what state the system is in, because state is just files.
Think of the workspace as a library. The routing files are the catalog: small, stable, they point at everything and store almost nothing. The content lives on the shelves (stage folders, node files, reference material). One librarian — one model — walks the building, and the question decides which shelf gets walked to. Nobody photocopies the library into a backpack; that is what context-stuffing is. The catalog is small on purpose.
Highlights
- Building from a described process, idea, or problem → Build mode.
- An existing folder, repo, or vault that needs ICM structure → Restructure mode.
- A body of work later agents must edit (code, markdown, or mixed) → System map form. Read references/system-map.md after picking the form.
- What is the repeating unit of work? (an episode, a client, a report, a person, a team?)
- Walk me through one run, start to finish. Where do you stop and check something before continuing?
When to use it. Design any process, idea, problem, or body of knowledge into an ICM (Interpretable Context Methodology) workspace — folder structure as agent architecture — or restructure an existing folder, repo…
Install
npx skills add RinDig/icm-architect
Or copy the skill folder manually:
git clone https://github.com/RinDig/icm-architect.git
cp -r icm-architect/ ~/.claude/skills/icm-architect
Source: RinDig/icm-architect — 1,409 stars, MIT, last pushed 2026-08-25.
