C² vs BMAD: two ways to build with AI agents

BMAD and C² are two of the better-known methods for building software with AI coding agents, and they come up together a lot. They share a premise — AI changes how you should structure development — but they answer it differently. Here's an honest head-to-head from someone who built one of them and ships production software with it daily.

What each is

BMAD (Breakthrough Method for Agile AI-Driven Development) is an orchestrated SDLC. It defines specialised AI personas — Product Manager, Architect, Developer, QA — and moves work through phases (analysis → planning → solutioning → implementation) with artifacts and guardrails at each step. It's opinionated, end-to-end, and complete — if the persona pipeline is the thing you want.

C² (the C² Method) is a lighter, agent-agnostic method built on one architectural idea: every project runs two systems — a codebase and a contextbase — and the contextbase (briefs, patterns, gotchas, decisions) is a first-class, version-controlled artifact the agent reads before it acts. Work runs through a light cascade of briefs, the human is the pilot who directs throughout, and the contextbase compounds every session.

The core difference

BMAD's centre of gravity is the persona workflow — who does what, in what order. C²'s centre of gravity is the contextbase — what the system knows, and how that knowledge compounds across sessions.

That one distinction decides almost everything else. In BMAD, context lives inside the pipeline: it's loaded to run a phase and consumed doing it. In C², context is an asset that accrues — every session commits what was learned, so the next session starts ahead. After fifty sessions a C² contextbase is denser in real decisions than the code itself; a pipeline doesn't leave that behind.

Three practical consequences:

• Weight. BMAD is a fuller framework you adopt and serve. C² is a method plus markdown templates — lighter to start, easier to bend, nothing to rip out later.
• Ownership and portability. C² is plain markdown in git with no orchestration layer, so it transfers between agents with zero friction and the context you build is yours — not locked inside a framework.
• Range. A C² contextbase is the same shape for a solo founder on one product and a team running many apps across multiple locations. BMAD's persona orchestration is built for a team that wants exactly that pipeline — heavy for a solo builder, and indifferent to whether your context compounds.

Side by side

When to pick which

• Pick C² if you want the lightest structure that still compounds — a contextbase the agent reads first, a few brief templates, the discipline of a session brief — and you want it to fit whether you're solo today or running several apps across a team tomorrow. For most builders, this is the one.
• Pick BMAD if you specifically want a prescriptive, role-based pipeline that tells the team and the agents exactly who does what at each phase, and you're happy to adopt a fuller framework to get it.

They're not mutually exclusive at the level of ideas. If you run BMAD, C²'s contextbase discipline — a router, a knowledge folder, session briefs as memory — slots in underneath the persona workflow and gives it the one thing it lacks: memory that compounds. If you run C², BMAD's persona thinking can inform how you design your agent team.

The honest summary: BMAD gives you a workflow to serve; C² gives you a contextbase you own. Most teams feel the context problem first — the agent forgetting, the knowledge evaporating — and that's the gap C² was built to close.

Read the C² method, see how all the methodologies compare, or the head-to-head with Shape Up. For the wider shift this is part of, see the alternative to Agile.