C² Method9 min read

Spec-driven development tools compared (2026)

Spec Kit, Kiro, BMAD, Agent OS, Task Master, OpenSpec and C², checked against their own repos and docs.

Stuart Leo

Spec-driven development exists because prompting code into existence stops working the moment a feature gets bigger than one chat. The agent guesses at the gaps. The guesses ship. A month later nobody, human or model, can say why the code does what it does. Every tool in this piece answers that with the same move — write down what you want, in files the agent can read, before it writes code.

That is where the agreement ends. Some of these are spec workflows you install into the agent you already use. One is a commercial agent with specs built in. One is a full delivery method. One is a task manager. One is mostly about coding standards.

I should say the awkward thing first. I built one of the seven — C², the method I run my own builds on. So I am biased, and you should read this with that in mind. I have tried to be fair the only way I know how. Every claim about another tool comes from its own repo or docs, checked on the date at the bottom, and where something isn't documented I've left it out rather than guessed.

If you want depth on one pairing, I've written head-to-heads on C² vs BMAD and C² vs spec-driven development as an idea, plus a wider map of AI development methodologies. This page is the current, tool-by-tool view.

The comparison at a glance

ToolCore ideaMain artefactsBest forLicence / cost
GitHub Spec KitSpec → plan → tasks → code, in any agentconstitution, spec.md, plan, tasks, checklistsOne feature at a time, across 40+ agentsMIT, free
Kiro (AWS)An agent with specs built into the productrequirements.md or bugfix.md, design.md, tasks.md, steering filesTeams happy to work inside one commercial toolCommercial, free tier then paid plans
BMAD MethodA full agile method run through named agent rolesbriefs, PRD, architecture, initiative → epic → story ticketsLarger work that needs product, design and architecture thinkingMIT, free
Agent OSCapture your coding standards, inject them into plansstandards + index.yml, mission, roadmap, spec foldersKeeping agents on your conventionsMIT, free
Task MasterParse a PRD into dependency-ordered tasksprd.txt, tasks.jsonBreaking a big PRD into a queue the agent works throughMIT + Commons Clause, free to use
OpenSpecA lightweight change folder per feature, merged into living specsproposal.md, specs/ deltas, design.md, tasks.mdBrownfield repos and iterating without phase gatesMIT, free
C²Context that compounds across the whole reporouter file, docs/ contextbase, PRD → prompt brief cascade, session briefs, gotchasLong-running projects where what you learn should carry forwardCC BY-NC-SA 4.0, free

GitHub Spec Kit: the reference SDD toolkit

Spec Kit is GitHub's open-source toolkit, and the most widely starred project here at about 150,000 stars. It installs with the specify CLI (Python 3.11+ and uv) and then runs as commands inside your agent. The integrations list names more than 40 agents, including Claude Code, Codex CLI, Cursor, GitHub Copilot, Gemini CLI and Kiro CLI, plus a generic option.

The core flow is constitution → specify → plan → tasks → implement → converge. The constitution holds project principles and is written once. The rest repeats per feature. Clarify, checklist and analyze are optional quality gates for work with real ambiguity, and converge checks the code against the artefacts until it reports Converged. Newer releases add bug-fix and idea-assessment processes as extensions, plus presets, workflows and catalogs for teams that want to bend the process.

It is mature and moving fast. Version 1.4.1 shipped on 16 November 2026, and it's MIT licensed. If you want the canonical shape of spec-driven development without changing agents, this is it.

Kiro: specs inside a commercial agent from AWS

Kiro is different in kind. It is an agent product, built and run by AWS, available as an IDE, a CLI, a web app and a mobile app. Specs are a feature of that product rather than something you install.

A Kiro spec is three files. requirements.md holds user stories and acceptance criteria written in EARS notation (or bugfix.md for a bug), design.md holds architecture and sequence diagrams, and tasks.md holds the implementation plan. Feature specs can run requirements-first or design-first. When you run all tasks, Kiro builds a dependency graph from tasks.md and runs independent tasks in parallel waves. Project-level context lives in steering files under .kiro/steering/, and Kiro also reads AGENTS.md.

Pricing starts with a free tier of 50 credits a month, then paid plans from $20 per user per month. The pricing page lists both Anthropic and OpenAI models alongside its default Auto routing. The changelog shows releases as recent as 16 November 2026.

Kiro vs Spec Kit comes down to one question. Do you want specs inside an integrated product, or a spec workflow that travels across the agents you already pay for?

BMAD Method: a full agile method with agent roles

BMAD is the most complete method here, and it has changed a lot. About 55,000 stars, MIT licensed, and free with no paywalled workflows, according to its README. The stable line is v6.12 (v6.12.4, 14 October 2026). V7 is a preview alpha that installs as agent skills, and the README gives its release target as mid-November 2026.

How BMad works is four stages: clarify, plan, build and verify, learn and adjust. You enter where your input is. A small change goes straight to build. Each stage has named agents — Mary the analyst, John the PM, Sofia the product owner, Sally on UX, Winston the architect, and a developer agent (Amelia in the released source, Mason in the current docs). Tracked work sits in a ticket tree of initiative → epic → story, and the docs are explicit that the ticket is the spec.

BMAD also takes project context seriously now. Its project-context skill writes and maintains a verified block in AGENTS.md. V7 needs an agent that supports skills, plus Node and uv.

Spec Kit vs BMAD is mostly a question of scope. Spec Kit carries one feature from spec to code. BMAD runs the whole delivery around it, roles and retrospectives included.

Agent OS: standards first, specs second

Agent OS, by Brian Casel at Builder Methods, made a deliberate retreat in v3.0 on 20 January 2026. The changelog says plan modes and frontier models now handle spec writing, task breakdown and orchestration well, so v3 hands those back to the agent. What it keeps is standards.

The commands are discover-standards, inject-standards, index-standards, plan-product and shape-spec. Standards live as markdown under agent-os/standards/ with an index.yml so the right ones get pulled in. Plan-product writes mission.md, roadmap.md and tech-stack.md. Shape-spec improves your agent's plan mode with targeted questions and saves a spec folder holding plan.md, shape.md, standards.md and references.md.

It works alongside Claude Code, Cursor, Antigravity and other tools, and it's MIT licensed with about 5,600 stars. Support comes through a paid Builder Methods Pro community.

BMAD vs Agent OS is not close in shape. BMAD is a full method with roles. Agent OS is a thin layer that makes sure whatever plan your agent writes follows your conventions.

Task Master: a PRD parsed into a task queue

Task Master does one thing and does it well. You write a PRD (.taskmaster/docs/prd.txt), it parses that into tasks with dependencies, and the agent asks for the next task, expands it into subtasks and marks it done. It runs as an MCP server or a CLI, and its docs list 13+ supported editors including Cursor, Claude Code, Windsurf, VS Code, Roo, Cline, Codex, Gemini CLI and Kiro.

Two details matter before you adopt it. First, it calls models itself, so you 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 commercially and sell what you build with it, but per the README you can't sell Task Master itself, host it as a service or build a competing product from it.

It has about 28,000 stars. The latest release is 0.43.1 from 31 March 2026, and its docs now live on Hamster's site. On the evidence I can see, the open-source repo has slowed this year.

Task Master vs BMAD is a category mismatch. Task Master manages the queue after the PRD exists. BMAD helps you work out what the PRD should say.

OpenSpec: lightweight change folders for brownfield work

OpenSpec, from Fission AI, is the lightest spec workflow here and the second most starred at about 75,000. Its stated philosophy is fluid not rigid, iterative not waterfall, and built for brownfield as well as greenfield.

Each change gets a folder under openspec/changes/, with proposal.md, a specs/ folder of requirement deltas, design.md and tasks.md. The deltas are plain markdown — ADDED requirements in SHALL form, with WHEN/THEN scenarios. Explore, propose, apply, then archive, and archiving merges the change into the living specs in openspec/specs/. That merge is the useful idea. The spec describes the system as it is now, not a pile of past feature requests.

It supports 30+ tools through skills, ships a beta "stores" feature for specs shared across repos, and is MIT licensed. Version 2.1.0 shipped on 17 November 2026. It also collects anonymous usage telemetry by default, which the README documents along with how to switch it off.

C²: context that compounds, not a spec tool

C² is mine, so take this section with the bias I named at the top. It is not a spec tool and I won't pretend it competes on that ground. It's a method for the context around a whole repo, and it's young: the public kit is new, even though the method behind it is two years and more than 1,000 agent sessions old.

A C² repo has a router file at the root (AGENTS.md by default, or CLAUDE.md or GEMINI.md) that routes to docs rather than duplicating them. Under it sits a docs/ contextbase — planning, working, knowledge, operations. Work flows down a cascade of PRD → feature PRD → prompt brief → task → session brief. Every session ends in a session brief, and every non-obvious trap becomes a gotcha 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.

How to choose

Start with the job you actually have.

  • You want one feature specced, planned and built, in the agent you already use. Spec Kit. It's the reference implementation and supports the widest range of agents.
  • You work in a large existing codebase and want the spec to describe the system as it is now. OpenSpec. The change-folder-then-archive loop is built for brownfield work.
  • You want an integrated product and will commit to one vendor. Kiro. Specs, steering, parallel task runs and hooks in one place, on a paid plan.
  • You want a whole delivery method, with product, UX and architecture thinking before the build. BMAD. Expect more process than the others, sized to the work.
  • Your problem is agents ignoring your conventions, not missing specs. Agent OS.
  • You already have a good PRD and want it turned into an ordered queue. Task Master, once you've read the licence.
  • Your problem is that every session starts cold. That's a context problem, not a spec problem. It's the one C² was built for.

For "best spec-driven development framework", my honest answer is Spec Kit for most people starting today. It is free, portable, actively released and closest to the idea itself. OpenSpec is the lighter alternative if Spec Kit's gates feel heavy.

Where C² fits

The line between these tools has blurred. Spec Kit has a constitution, Kiro has steering files, Agent OS has standards and BMAD now maintains a block in AGENTS.md. Every serious tool has worked out that a spec without project context drifts.

The difference I care about is scope and time. A spec is about one feature, and it's done when the feature ships. The contextbase is about the whole repo, and it is never done. The decision behind feature one, the trap you hit in week three, what changed in yesterday's session — those belong to the repo, not to any single spec, and they're what make feature twelve start ahead of feature one. I wrote more on that in what a contextbase is.

So they compose. Run Spec Kit or OpenSpec for the feature — their spec folders sit happily inside a C² docs/ tree, and a prompt brief can simply point at one. Let the router send the agent to the right spec. Let the session brief and the gotchas carry what you learned into the next feature. The spec tool makes this feature right. C² makes sure the repo remembers it.


Last checked: 18 November 2026. These tools release weekly, sometimes daily. If something here is out of date or wrong, tell me and I'll correct it. Accuracy is the only reason a comparison like this is worth reading.

Go deeper with C² vs BMAD, C² vs spec-driven development, or write acceptance criteria your agent can check. Or read the method.

Questions people ask

What are the best spec-driven development tools in 2026?
The main ones are GitHub Spec Kit, Kiro from AWS, BMAD Method, OpenSpec, Agent OS and Task Master. Spec Kit and OpenSpec are free, MIT-licensed spec workflows that run inside the coding agent you already use. Kiro is a commercial agent with specs built in. BMAD is a full agile method with named agent roles. Agent OS focuses on codebase standards, and Task Master turns a PRD into a dependency-ordered task list.
Spec Kit vs BMAD: which should I use?
Use Spec Kit if you want one feature carried from spec to plan to tasks to code, with optional quality gates, inside whichever agent you already run. Use BMAD if you want a whole delivery method with named agent roles (analyst, PM, product owner, architect, developer) and a ticket tree of initiatives, epics and stories. Both are free and MIT-licensed.
Kiro vs Spec Kit: what is the difference?
Kiro is a commercial agent from AWS that runs in its own IDE, CLI, web and mobile apps, with specs (requirements.md, design.md, tasks.md) built into the product. Spec Kit is a free, open-source toolkit that installs spec commands into more than 40 existing coding agents. Kiro gives you an integrated product. Spec Kit gives you portability across agents.
Task Master vs BMAD: are they the same kind of tool?
No. Task Master is a task manager: it parses a PRD into tasks with dependencies and tells the agent what to work on next. BMAD is a full method covering clarifying the idea, planning, building and retrospectives. Task Master's licence is MIT with the Commons Clause, so you cannot sell or host Task Master itself. BMAD is plain MIT.
Can I use a spec-driven development tool with C²?
Yes. A spec tool shapes the work for one feature. C² is a method for the context around the whole repo: a router file, a docs contextbase, session briefs and gotchas. Run Spec Kit or OpenSpec for the feature, and let C² carry what you learned into the next one.

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.