CRAFT — the Context-Reusable Agentic Folder Tree — gives vision, references, prompts, plans, and code a stable home. A directory shape your humans and your agents can both rely on.
The quality of AI output is bounded by the quality of its inputs. CRAFT separates slow-moving human signal — vision, domain, skills — from fast-moving AI output, and keeps each at a predictable path.
Agents stop re-deriving context every session. Humans stop losing intent in the churn.
The product vision, the domain language, the MVP definition, the value proposition. Short, dense, durable. The kind of thing you'd want a new teammate — or a new agent session — to read first.
Static or dynamic artifacts. Customer exports for data-model planning. Append-only dumps of Slack, Linear, Google Docs, transcripts. Figma exports. Design system snapshots. The raw material an agent might cite, search, or summarize.
Reusable agent capabilities, schedulable jobs, checklists, QA routines. The hard-won prompts and workflows that survive across projects.
A mature agentic workflow is mostly planning. Engineering data models, marketing site implementation plans, rollout reports — written collaboratively, TLDR at the top, rendered as HTML when they need to be shared.
Code repositories. Apps, services, infrastructure, libraries, plugins. The binaries compiled from everything above.
Vision and domain change in months. Plans change in hours. CRAFT puts each on its own clock so the slow, valuable inputs aren't buried under generated drafts.
The same specs/, references/, and prompts/ feed every plan and every agent session. Stop re-deriving the setup. Start composing on top of it.
Today's agentic tools read markdown better than they navigate systems. No MCP roundtrips, no retrieval gymnastics, no search dance — just files at predictable paths.
Agentic engineering has moved us up the stack. The context — vision, domain, prompts, plans — is the human-language equivalent of C++. The shipped repositories in build/ are the binaries we compile from it.
If that framing is right, then context deserves the same care we give code: version control, structure, conventions, reuse. CRAFT is the smallest folder shape that takes the idea seriously.
You don't need a framework to adopt CRAFT. Create the five top-level folders. Move what you already have into them. Add an AGENTS.md so your agent knows the layout. That's the onboarding.
CRAFT is intentionally minimal — a shape, not a system. Tooling will follow (write-only spec docs, reference syncers, plan renderers), but the spec works the day you create the directories.
CRAFT is being iterated in public. If something's missing, wrong, or could be sharper — open an issue. Tooling will grow around the shape; the shape itself stays small.
Maintained by Rekall. Use it · fork it · extend it.
CRAFT