C² Method3 min read
How to customise the C² Method for your team and project
The six folders are a starting shape, not a rulebook. What's load-bearing, what you can bend, and a worked example of extending it.
The fastest way to misread C² is to treat the six folders as a standard you have to comply with. They aren't. They're a starting shape, the layout that held up across a couple of years of real production work, handed to you so you don't start from a blank repo. It's convention over configuration: sensible defaults you can override, not rules you must obey.
What matters isn't the folders. It's the two ideas underneath them: context is a first-class artifact, and the agent reads it before it acts. Everything else is arrangement, and arrangement should serve your project. Here's what you can't bend, what you can, and a worked example of extending it.
What's load-bearing
Three things are genuinely structural. Keep these and you're doing C²:
- The Router. One file your agent reads first, that points to everything else.
- The Session Brief. Written memory across the gap between sessions.
- Knowledge capture. Discoveries committed to git, read again next time.
The numbered folders are just where those things live by default. Move them, rename them, split them, as long as the Router still points to them and the agent can still find them.
How to adapt the rest
A few moves that are not just allowed but encouraged:
- Add a folder. Tracking velocity and estimation accuracy? Add a
07-metrics/(worked example below). Running a research project? You might want an08-experiments/. - Sub-divide. A big product might split
01-planning/intoproduct-requirements/,strategy/androadmap/. - Drop what you don't use. A solo project may never touch
06-agents/. Delete it. An empty folder teaches nothing. - Rename for your team. If "release-notes" lands better as "changelog", rename it. The Router is the source of truth, not the folder name.
The test
Before you add or remove anything, ask one question: will the agent find what it needs, faster, because of this change? If yes, do it. If you're adding structure to feel organised rather than to load context, you're decorating, not building.
Worked example: add a 07-metrics folder
Most projects never need a seventh folder. But once you're a few months in and want to know whether your estimates are any good, or how throughput is trending, the data is sitting in your contextbase already, in the frontmatter of your briefs and PRDs. A 07-metrics/ folder is where you make it legible.
When it's worth it
Add 07-metrics/ when you have a real question you'd act on:
- Are my estimates calibrated? You've been filling in
estimated_hours/actual_hourson Prompt Briefs. - Is throughput trending up? You want a monthly count of briefs shipped.
- Where does time actually go? You want it broken down by area.
If you don't have a question, don't add the folder. Metrics nobody reads are just noise with a directory. If you're unsure what's even worth measuring, the DORA metrics are the industry standard for delivery performance, but adopt only the ones tied to a question you'd act on.
The shape
docs/07-metrics/
├── velocity/ ← monthly throughput notes
└── estimation.md ← calibration: estimated vs actual, by area
Wiring it in
Two small moves and it's part of the method:
- Point the Router at it. Add a line to
AGENTS.mdlinking07-metrics/so the agent reads it when you ask for a calibration check. If you haven't written your Router yet, see how to write AGENTS.md. - Make it a Learn-loop output. When you run the periodic consolidation, have the agent read the completed Prompt Briefs, total the estimate-vs-actual, and update
estimation.md. The data already exists in frontmatter. You're just summarising it.
The same three steps, in any direction
Nothing about the metrics example is special to metrics. The same three steps (decide there's a real question, give it a folder, point the Router at it) extend C² in any direction. The method grew this way in the first place.
The structure serves the work. Not the other way round.
See the docs structure you're adapting, or read the full method.
Questions people ask
- Do I have to use all six C² folders?
- No. The six folders are a starting shape, not a standard to comply with. Drop what you don't use, rename what lands better for your team, and add what your work needs. What has to stay is the Router, the session brief and knowledge capture.
- What parts of C² can't I change?
- Three things are structural: the Router (one file the agent reads first that points to everything else), the session brief (written memory across the gap between sessions), and knowledge capture (discoveries committed to git and read again next time). Keep those and you're doing C².
- How do I extend C² with a new folder?
- Three steps: decide there's a real question you'd act on, give it a folder, and point the Router at it. A 07-metrics folder for estimation accuracy and throughput is a worked example.
- How do I know if a change to the structure is worth it?
- Ask one question: will the agent find what it needs, faster, because of this change? If yes, do it. If you're adding structure to feel organised rather than to load context, you're decorating, not building.
Part of the C² Method. Start with the method
Put this in your repo
The C² Method is free and open. Point your agent at the kit and get started in minutes.