Audio brief · 2 min
Compare

RACE Programming vs BMAD Method

BMAD gives an engineer a team of AI agent personas, from analyst to developer, inside a coding tool. RACE Programming prescribes the human team that delivers for a client, with the AI agent inside it. BMAD agents can be part of the machinery a RACE team runs.


What BMAD is

Agile roles played by AI agents

The BMad Method is maintained by BMad Code, LLC under the MIT license and is free and open source. Its README calls it Agile AI Driven Development, covering the whole effort, not only the code: what to build, how it holds together, and how it changes as you learn. Work moves through a delivery loop: clarify, plan, build and verify, learn and adjust. Small changes go straight to build; complex work gets deeper planning.

The method installs as skills into coding tools such as Claude Code, Cursor, Codex and others. The agent reference lists five named personas in the BMad Method module: Analyst (Mary), Product Manager (John), Architect (Winston), Developer (Amelia) and UX Designer (Sally). Planning skills produce documents such as a product brief, a PRD, an architecture spine, a short specification and epics with stories, as described in Choose a Planning Path. Further modules cover test architecture, unattended epic execution and more.

Sources checked October 21, 2026, against the stable release v6.12.4. A V7 preview is in development and may change details.

At a glance

AI personas, or a human team with the agent inside

Dimension RACE Programming BMAD Method
What it is Prescriptive Agentic SDLC framework Open source skills, agent personas and workflows for AI-driven development
Who holds the roles People: Team Principal, Forward Deployed Engineer, AI Product, Quality Engineer, Software Engineers AI personas: Analyst, Product Manager, Architect, Developer, UX Designer
Where the AI sits Silicon Software Engineer, inside both the Pit Wall and the Pit Crew The personas themselves, invoked by the user
Work artifact Executable User Story, accepted with the Team Principal Brief, PRD, architecture, specification, epics and stories
Cadence Continuous Kanban flow; each Executable User Story production-ready in 2-3 days at the floor; Pit Stops on the client's release cadence Delivery loop sized to the work; sprint planning and story tracking available
What RACE does differently

The roles are accountable people

  • Roles and topology. The Team Principal owns product direction and acceptance and never manages engineers. The Pit Wall pairs a Forward Deployed Engineer with an AI Product and is the only contact on the product. The Pit Crew is a Quality Engineer and two Software Engineers. A TPM is accountable for the project goals.
  • Executable User Story. One artifact holds the user story, a working prototype, NFR in EARS, an ADR, Gherkin acceptance, test data and a delivery cost in dollars.
  • Flow and release cadence. Each Executable User Story is production-ready in two to three days at the floor; a Pit Stop releases it on the client's release cadence.
  • Machinery share of the backlog. The Forward Deployed Engineer owns the engagement's delivery machinery; the number to watch is the share of the backlog it clears. RACE scales by raising that share, not by adding people.
Where they combine

BMAD personas as workflows of the Silicon Software Engineer

In RACE the AI agent is a teammate with many workflows. BMAD personas fit that slot. The Pit Wall can use the Analyst and Product Manager skills to research and draft the parts of an Executable User Story, then decide and sign it off with the Team Principal. The Pit Crew can run the Developer's build and review skills inside the Quality Engineer's guardrails. The Forward Deployed Engineer chooses and tunes these skills as part of the engagement's machinery, and the RACE Engineer carries what works across engagements.

When to choose which

Different layers, often both

  • Choose BMAD when an engineer or a small group wants an agent-guided path from idea to working code in their coding tool.
  • Choose RACE Programming when you deliver for a client or a business and need the team model: roles, client contact, verification, cadence and economics.
  • Use both when you adopt RACE and want BMAD skills as part of the team's machinery.

Using BMAD already? The framework page shows the human roles and artifacts around the agents.

Read the framework → · RACE vs Spec Kit → · More comparisons →

FAQ

Frequently asked questions

What is the difference between RACE Programming and the BMAD Method?
The BMad Method is a free, open source approach to AI-driven development, maintained by BMad Code, LLC under the MIT license. It installs skills and named AI agent personas (Analyst, Product Manager, Architect, Developer, UX Designer) into a coding tool, and moves work through a loop of clarify, plan, build and verify, learn and adjust. Its agile roles are played by AI agents working with you. RACE Programming is a prescriptive Agentic SDLC framework whose roles are people: the Team Principal, the Pit Wall (Forward Deployed Engineer and AI Product) and the Pit Crew, with the Silicon Software Engineer, the AI agent, inside both tiers.
Can a RACE team use BMAD?
Yes. BMAD skills and personas are machinery, and in RACE Programming the Forward Deployed Engineer owns the engagement's delivery machinery. BMAD planning skills can help the Pit Wall draft parts of the Executable User Story, and its build and review skills can run inside the Pit Crew's guardrails. The human decisions stay with the RACE roles that own them.
Are BMAD agents the same as RACE roles?
No. A BMAD Product Manager or Architect is an AI persona that one engineer invokes in a coding tool. A RACE AI Product or Forward Deployed Engineer is a person accountable to a client, with decision rights, who works with the Silicon Software Engineer. BMAD personas can serve as workflows of that agent.
When should I choose BMAD and when RACE Programming?
Choose BMAD when one engineer or a small group wants a structured, agent-guided way to go from idea to working code in their coding tool. Choose RACE Programming when you run delivery for a client or a business and need the team model: roles, client contact, verification, release cadence and economics. They combine well.