The Three-Agent Protocol Is Transferable. The Discipline Isn't.
The Copyable Part I've written about running Claude, Codex, and Gemini on the same codebase. The response I get most often is: "How do I set this up?" The setup is the easy part. Here it is: memory...

Source: DEV Community
The Copyable Part I've written about running Claude, Codex, and Gemini on the same codebase. The response I get most often is: "How do I set this up?" The setup is the easy part. Here it is: memory-bank/ activeContext.md # what's true right now progress.md # what's done, what's pending docs/plans/ # task specs for each agent CLAUDE.md # codebase rules + agent instructions scripts/hooks/ # pre-commit enforcement Copy that structure into your repo. Write a CLAUDE.md. Create a memory-bank/. You now have the skeleton. But the skeleton isn't why it works. What Actually Makes It Work Three things that don't fit in a file structure: 1. The spec is the contract, not the prompt. When I hand a task to Codex, I don't say "add a function that registers an ArgoCD cluster." I write a spec with exact old/new code blocks, a Definition of Done checklist, a commit message, and an explicit "What NOT to Do" section. The spec is what Codex reads. The spec is what I verify against. If the diff doesn't match