C² Method8 min read

Task Master vs BMAD vs Agent OS: which fits your repo?

A task queue, a full delivery method and a standards layer. What each one installs, what it puts in your repo, and who it suits, checked against their own repos and docs.

Stuart Leo

Task Master, BMAD and Agent OS get compared as if they were three versions of the same thing. They aren't. Task Master turns a PRD into a dependency-ordered task queue your agent works through. BMAD is a full agile delivery method run through named agent roles, from clarifying the idea to retrospectives. Agent OS captures your coding standards and injects the right ones into whatever plan your agent writes. Pick by the problem you actually have: a big PRD to sequence, a whole delivery process to run, or agents that ignore your conventions.

This is a closer look at those three, spun out of my wider comparison of spec-driven development tools. Every fact about them comes from their own repos and docs, linked inline and checked on the date at the bottom.

One disclosure up front. I built C², a method for keeping context across a repo, and I compare it at the end. So I'm not neutral. Where something isn't documented, I've left it out rather than guessed.

Task Master vs BMAD vs Agent OS at a glance

Task MasterBMAD MethodAgent OS
What it isPRD → task queue for your agentFull agile method with agent rolesCoding standards captured and injected
Starts fromA PRD you've writtenWherever your input is: a notion, an idea or a changeYour existing codebase's conventions
Installnpm package, run as MCP server or CLInpx bmad-method install (v6.12) or npx skills add (v7 preview)Base install, then a project install script
In your repo.taskmaster/ with PRD, config, tasks.jsonTicket tree of specs under _bmad-output/, plus an AGENTS.md blockagent-os/ with standards, product docs, spec folders
Calls models itselfYes, needs a provider key unless via Claude Code or Codex CLINo, runs inside your coding agentNo, runs inside your coding agent
LicenceMIT with Commons ClauseMITMIT
Latest release0.43.1, 31 March 2026v6.12.4, 14 October 2026 (v7 in preview)v3.0, 20 January 2026
GitHub starsabout 28,500about 55,500about 5,600
Best forSequencing a large PRDLarger work that needs product and architecture thinkingKeeping agents on your conventions

What is Task Master?

Task Master describes itself as an AI-powered task-management system you can drop into Cursor, Windsurf, Roo, Lovable and other tools. Its docs now live on Hamster's site.

How it works. You write a PRD. Task Master parses it into tasks, each with an id, title, description, status, dependencies, priority, implementation details, a test strategy and optional subtasks, per its task structure doc. From there your agent asks it what to work on next, expands a task into subtasks, and marks work done. It has a research command for pulling in current information, and tags for separate workstreams.

Install. From the README:

npm install -g task-master-ai
task-master init

# or, for Claude Code, as an MCP server
claude mcp add taskmaster-ai -- npx -y task-master-ai

What it puts in your repo. A .taskmaster/ folder. Your PRD goes in .taskmaster/docs/prd.txt, and an example lives in .taskmaster/templates/example_prd.txt after init. Model settings live in .taskmaster/config.json, tag state in .taskmaster/state.json, and the tasks themselves in a tasks.json file, with generated per-task files kept in sync from it. The tutorial notes that teams can hit merge conflicts in tasks.json when people add tasks on different branches, and it has a move command for resolving them.

The two things to know before adopting it. First, Task Master calls models itself. You configure main, research and fallback roles, and need at least one provider API key, unless you route through Claude Code or Codex CLI. Second, the licence is MIT with the Commons Clause. You can use it for any purpose and sell what you build with it, but you can't sell Task Master itself, host it as a service or build a competing product from it.

Activity. The latest tagged release is 0.43.1 from 31 March 2026, and the last push to the repo was in late April. On the evidence I can see, the open-source repo has slowed this year.

Who it suits. Someone who already has a good PRD and wants it broken into an ordered queue the agent can work through without losing its place.

What is BMAD Method?

BMAD calls itself agile AI-driven development: turning an idea or change request into working software "without giving up the thinking". Its README says it's free and open source with no paywalled workflows, under the MIT licence.

How it works. How BMad works lays out four stages: clarify, plan, build and verify, learn and adjust. They aren't a fixed sequence. A small fix can start at build. Each stage has named agents: Mary the analyst, John the product manager, Sofia the product owner, Sally on UX, Winston the architect and Mason the developer. Tracked work sits in a ticket tree. An initiative holds epics in build order. An epic is one capability delivered over several build sessions. A story is one build session's worth of work.

Install. BMAD ships on two lines. The stable line is v6.12, which the README says is frozen apart from bug fixes:

npx bmad-method install

It needs Node.js 20.12+, Python 3.10+ and uv. The v7 line is a preview alpha that installs as agent skills, and the README warns to expect breaking changes:

npx skills add bmad-code-org/BMAD-METHOD/skills/core-tools --skill '*'
npx skills add bmad-code-org/BMAD-METHOD/skills/method --skill '*'

The README gave v7's release target as mid-November 2026. As of my check, the latest tagged release is still v6.12.4 from 14 October.

What it puts in your repo. In the docs' example layout, work lands under _bmad-output/: an initiative spec, folders for its PRD, UX and architecture documents, and a tickets/ tree where tickets.toml files list the epics and stories and each story gets a plan file carrying its status. BMAD also has a project-context skill, bmad-project-context, that writes a verified block into AGENTS.md between <!-- bmad:context --> markers. It holds only what is costly to rediscover: policy, run caveats, non-default conventions, observed pitfalls. For Claude Code it proposes a one-line @AGENTS.md import into CLAUDE.md. It never commits. You review the change.

Who it suits. Teams and solo builders who want a complete method, with product, UX and architecture thinking before the build and retrospectives after. BMAD sizes the process to the work, but there is more of it than in either of the other two.

What is Agent OS?

Agent OS is by Brian Casel at Builder Methods. Its README says it helps you shape better specs and keeps agents aligned in a lightweight system that fits how you already build, alongside Claude Code, Cursor, Antigravity and other tools.

How it works. Version 3.0, released 20 January 2026, deliberately narrowed the tool. The changelog says spec writing is now best handled by your agent's plan mode, task breakdown by the agent's own todo lists, and orchestration by frontier models, so v3 retired those phases. What it kept is standards. There are five commands:

  • discover-standards surfaces conventions from your codebase and writes them up as standards.
  • index-standards keeps them organised in an index.yml.
  • inject-standards pulls the relevant ones into a conversation, plan, subagent or Claude skill.
  • plan-product writes product docs through an interactive conversation.
  • shape-spec improves plan mode with targeted questions and saves the result.

Install. There's a base installation, then a project install script run from inside your repo. The full instructions are on Builder Methods' site, which asks for your email before showing them. Agent OS itself is free and open source. Official support comes through a paid Builder Methods Pro membership.

What it puts in your repo. From the install script and command files: an agent-os/ folder with agent-os/standards/ and its index.yml, plus the commands copied into .claude/commands/agent-os/. plan-product writes agent-os/product/mission.md, roadmap.md and tech-stack.md. Each shape-spec run creates a dated folder under agent-os/specs/ holding plan.md, shape.md, standards.md and references.md.

Who it suits. Developers whose agents plan well enough but keep drifting from house conventions. It's the thinnest of the three by design.

Task Master vs BMAD: are they the same kind of tool?

No. Task Master manages the queue after the PRD exists. BMAD helps you decide what the PRD should say, and then runs the delivery around it, roles and retrospectives included. They overlap in one place: both break work down and track it. BMAD does that as a ticket tree of specs written in markdown. Task Master does it as structured tasks with dependencies in tasks.json, worked through a next command.

The practical differences are cost and licence. BMAD runs inside your coding agent. Task Master makes its own model calls, so you either supply API keys or route it through Claude Code or Codex CLI. And BMAD is plain MIT while Task Master carries the Commons Clause.

BMAD vs Agent OS

These differ in shape more than anything. BMAD is a full method with six named roles and four stages. Agent OS v3 is a standards layer that hands planning back to your agent and makes sure the plan follows your conventions.

They also disagree about where the field is heading. Agent OS's v3 changelog is an argument that agents now handle specs and task breakdown well enough on their own. BMAD's position is that the thinking around the code still needs structure, scaled to the size of the change. Both are reasonable bets. Which one you agree with is a decent guide to which tool you'll be happy with.

Where C² differs

C² is mine, so take this section with that bias. It isn't a task manager, a delivery method with roles, or a standards injector, and it doesn't compete with any of these three on their own ground.

C² is about the context around the whole repo, kept over time. A C² repo has a router file at the root (AGENTS.md, CLAUDE.md or GEMINI.md) that points into a docs/ contextbase. Work flows down a cascade from PRD to prompt brief. Every session ends with a session brief. Every non-obvious trap becomes a gotcha file so nobody hits it cold twice. There's no CLI to install. You copy a starter folder of markdown templates into the repo. The current version is v1.4.3, released 25 September 2026, with an experimental fleet kit for running one agent per PRD. It's free under CC BY-NC-SA 4.0.

To be fair to all three, each now holds some durable context. Task Master keeps the task history. Agent OS keeps standards and product docs. BMAD's project-context skill keeps a verified block of pitfalls and caveats, and I've written about how that compares in C² vs BMAD. The difference I care about is scope. Their context serves their workflow. A contextbase is the record of the repo itself: every decision, every trap, every session's handover. That's what makes the twelfth feature start ahead of the first.

So they compose. Task Master's .taskmaster/, BMAD's output tree or Agent OS's agent-os/ folder can sit inside a repo that also has a router and a contextbase. Let the router point the agent at them. Let the session briefs and gotchas carry what was learned into the next piece of work.

How to choose

  • You have a solid PRD and want it sequenced. Task Master, after reading the licence and deciding how you'll pay for its model calls.
  • You want help deciding what to build, not just building it. BMAD. Stay on v6.12 if you need stability until v7 is released.
  • Your agents plan fine but ignore your conventions. Agent OS.
  • Every session starts cold and the same traps keep recurring. That's a context problem, and it's the one I built C² for.

Last checked: 20 November 2026. All three projects change often. If anything here is out of date, tell me and I'll fix it.

Start here: the wider spec-driven development tools comparison, C² vs BMAD, or set up C² in your repo.

Questions people ask

What is the difference between Task Master and BMAD?
Task Master is a task manager. You give it a PRD and it parses it into tasks with dependencies, then tells your agent what to work on next. BMAD is a full delivery method with named agent roles that helps you decide what to build, plan it as an initiative, epics and stories, build it and run retrospectives. Task Master starts once the PRD exists. BMAD helps you write it.
BMAD vs Agent OS: which should I use?
Use BMAD if you want a whole method, with product, UX and architecture roles and a ticket tree, sized to the work. Use Agent OS if your agents already plan well and your problem is that they ignore your conventions. Agent OS v3 captures your coding standards and injects the relevant ones into plans, and leaves spec writing to your agent's plan mode.
Is Task Master free?
It's free to use. The licence is MIT with the Commons Clause: you can use it commercially and sell what you build with it, but you can't sell Task Master itself, offer it as a hosted service or build a competing product from it. It calls models itself, so you need a provider API key unless you route through Claude Code or Codex CLI.
Can I use Task Master, BMAD or Agent OS with Claude Code?
Yes, all three. Task Master installs as an MCP server with one claude mcp add command. BMAD's v7 preview installs as agent skills into Claude Code and other skill-capable tools. Agent OS installs its commands into .claude/commands/agent-os/ in your project.
Where does C² fit against Task Master, BMAD and Agent OS?
C² is the method I built, so weigh this accordingly. It isn't a task manager or a spec tool. It's a router file plus a docs contextbase of briefs, decisions, session briefs and gotchas that carries what you learn across the whole repo. It can sit underneath any of the three.

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.