Claude Code IBE Workflow Template (v0.3.0)
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.
5
2 comments
Billa Coetsee
3
Claude Code IBE Workflow Template (v0.3.0)
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by