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. 👇

https://gitlab.com/vigilkeep/ibe-workflow-template Still in validation. The template gives Claude Code projects a repeatable structure for holding onto intent across sessions and across contributors, built on three ideas working together: IBE (Intent-Based Engineering, see https://vigilkeep.net) for keeping the "why" attached to the work, not just the "what"; Van Clief's ICM (Interpretable Context Methodology) for making that context legible rather than buried in someone's head; and Karpathy's behavioral principles for keeping the agent's day-to-day conduct predictable and scoped. Two files carry state: STATUS.md is the canonical current-position snapshot, overwritten each session and meant to be read cold by anyone (or any model) picking up the work. STATE.md is a personal, per-workstation session log — useful, but not something the project can rely on to bridge between machines or people, which is the gap the "consolidation before commit" rule exists to guard against. The template itself is compositional: a routing table maps task types (orient, plan, create, review, decide, debug, document, upgrade) to the workspace files and skills they need, so projects load only what's relevant instead of the whole thing at once. Newest piece is the no-code upgrade path (ADR-007): a versioning scheme so projects that instantiated an earlier copy of the template can pull in later refinements without a full re-adopt. Beyond the initial pilot (which included a complex multi-project organization), it's now been run live across an additional three real adopting projects — spanning both website and greenfield-project contexts — with all three upgrading cleanly. That's enough signal to call the upgrade path validated, not just designed.

The template integrates three frameworks: Van Clief's routing (the structural backbone), Karpathy's behavioral rules (think before acting, minimum viable scope, surgical changes, goal-driven execution), and IBE intent preservation (the "why" behind every decision). Each tier has a clear job — CLAUDE.md routes, workspace context files carry domain knowledge, skills wire selectively per task. The core addition on top of Jake's routing: a session state pattern (STATE.md) that eliminates cold-start friction. Each session closes by setting the next session's intent. Work becomes a directed sequence rather than a series of isolated conversations. Results from two validations (a meta-framework design project and a non-software operational coordination project): - Zero context re-establishment at session start - Zero intent-misaligned rework - Second project stood up in ~25 min on first attempt, no structural modifications needed Template is public: https://gitlab.com/vigilkeep/ibe-workflow-template Happy to share the ADR that documents the one deliberate deviation from 3.3 guidance (CLAUDE.md runs ~70 lines instead of 40–50 — there's a specific reason).

You just saw how context changes per task. Vote below, then tell us in the comments: what two areas of your work did you set up, and did Claude behave differently in each one?

You just wrote a CLAUDE.md for one of your projects. Vote below, then drop yours in the comments. Bonus points if you ran the same task with and without it and can tell us the difference.