🛠️ New tool: ICM Architect

👑

⭐

I explain the details about it on today's high tea .

I built a Claude skill that turns a process, an idea, or a messy folder into an ICM workspace. The folder structure does the orchestration. Numbered folders carry the order, the hierarchy scopes context, and plain markdown files hold state. One agent walks the right files at the right time and does the work a multi-agent setup would.

Repo: github.com/RinDig/icm-architect

📦 What it does

Two modes.

🔨 Build. You describe your work and it pulls out the structure already sitting in how you talk about it. The stages, the points where you stop and check, what stays the same every run versus what is new. Then it picks one of five proven forms and scaffolds the smallest workspace that carries the job.

♻️ Restructure. Point it at a folder, repo, or vault you already have. It reads every file, sorts each one by role, shows you a migration map, waits for your yes, then moves and checks the result.

🧩 The five forms

Pipeline, umbrella, record library, knowledge bundle, context map. They mix and nest, so most real workspaces use more than one.

✅ The walk test

Every result gets checked cold. An agent with no memory has to open the root, find its way, act, and report status from the files alone. If it can't, the structure gets fixed until it can.

⚙️ How to use it

You can honestly just tell claude to download it from the link, but if you're using codex or something else it will just have to restructure the claude.md to agents.md

Or if you want to do more Hands-On install

Claude Code: drop the folder in ~/.claude/skills/icm-architect/, then say "ICM this" or "build me a workspace for X."

Claude apps: zip the folder and upload it under Settings, then Capabilities.

Fork it, break it, tell me what you built. 👇

159

126 comments

🛠️ New tool: ICM Architect