Ditch the orchestrator, hire a librarian

What it does

icm-architect is a Claude skill that designs folder trees to function as agent control planes. Feed it a process, idea, or existing directory and it returns an ICM workspace: numbered folders impose sequencing, nested hierarchies scope context, and markdown files carry state. The pitch is that one agent, reading the right shelf at the right moment, can replace a whole multi-agent orchestration stack.

The interesting bit

Instead of wiring agents together with code, you wire them together with directory structure. The validation is a “walk test”: an amnesiac agent must enter the folder cold, figure out where it is, do the work, and report back using only the files in front of it. If the library is confusing, the architecture fails.

Key highlights

• Two modes: Build scaffolds a new workspace from a description; Restructure audits an existing folder, classifies every file, and migrates it into the ICM pattern.
• Six composable forms—Pipeline, Umbrella, Record library, Knowledge bundle, Context map, and System map—cover everything from production lines to editable system blueprints.
• Routing files act as a stable catalog: tiny pointers that keep the agent moving without stuffing the context window.
• Every workspace must pass the walk test before it is considered valid.
• Ships with copyable templates for stage contracts, node cards, schemas, and context manifests.

Caveats

• Tightly bound to the Claude ecosystem; this is a skill package, not a standalone CLI or library.
• Restructure mode pauses for human approval on the migration map before it executes any moves.

Verdict

Worth a look if you suspect your agent framework is mostly glue around context management and you would rather express that as 01-inbox/ folders. Ignore it if you do not use Claude or if your routing needs change faster than your directory tree.