Spec Kit vs Kiro vs OpenSpec vs BMAD (2026)
Four spec-driven development tools compared from their own docs: workflow, files, how specs stay current after the build, brownfield support, and which to pick.
Spec-driven development went from an idea to a crowded category in about a year. Google's autocomplete for "spec kit vs" now suggests OpenSpec, BMAD, Kiro, and more, and each project's README makes a confident case for itself.
This comparison uses each tool's own repository and documentation, checked on 16 November 2026. It isn't a benchmark. It describes what each tool asks you to do and, most importantly, what happens to the spec after the first build. For the method itself, see spec-driven development.
The short answer
| Spec Kit | Kiro | OpenSpec | BMAD | |
|---|---|---|---|---|
| What it is | Toolkit for your existing agent | An editor built around specs | Spec framework for AI coding assistants | Agile method with specialized agents |
| From | GitHub | Kiro | Fission AI | BMad Code |
| Unit of work | A feature | A spec (feature or bugfix) | A change | A change, sized to the work |
| Main files | constitution.md, spec.md, plan.md, tasks.md | requirements.md or bugfix.md, design.md, tasks.md | proposal.md, specs/, design.md, tasks.md | Briefs, specifications, architecture |
| After the build | Team chooses how to maintain specs | Not documented | Archiving a change updates the main specs | Carries decisions forward as context |
| Existing codebases | Guide for starting with a bounded change | Not covered in its specs docs | Built for brownfield first | Guide for inherited codebases |
| GitHub stars (16 Nov 2026) | 149,987 | Not applicable | 74,944 | 55,407 |
| License | MIT | See kiro.dev | MIT | Free and open source per README |
Spec Kit
Spec Kit adds spec-driven development to the coding agent you already use. Its README describes it in one line: define what to build and why, then turn the specification into a plan, tasks, and working code.
The flow runs as slash commands, one at a time, with a review after each: a constitution of project principles once per project, then specify, plan, tasks, implement, and converge until the work is complete. Optional steps cover clarification, checklists, and consistency analysis. Each step writes markdown, and there's a separate bug-fixing extension.
On existing projects, its guide says to start with a feature or modernization slice that can be reviewed on its own. After the first change, it asks the team to choose how specs are maintained: as an immutable record, as a living contract, or by reconciling discoveries back afterward.
Pick it when you want a light, widely used structure inside Claude Code, Copilot, or another agent you already use.
Kiro
Kiro is an editor with specs built in. A spec is three files: requirements.md with user stories and acceptance criteria (or bugfix.md for a bug), design.md for architecture and approach, and tasks.md for discrete, trackable tasks. Feature specs can start from requirements or from design. Kiro groups independent tasks into waves that run in parallel.
Its documentation doesn't say whether specs are kept in sync with code after implementation.
Pick it when your team is willing to adopt a new editor in exchange for specs being the default way of working.
OpenSpec
OpenSpec describes its philosophy as fluid rather than rigid, iterative rather than waterfall, and built for brownfield, not just greenfield. Work happens in changes. You explore an idea, then propose a change, which creates a folder with proposal.md, spec updates in specs/, design.md, and tasks.md. Then the agent applies it, and you archive it.
Archiving is the important step: the change's spec updates are merged into the main specs. Specs are plain markdown, with requirements written as SHALL statements and scenarios in WHEN and THEN form. For teams, OpenSpec offers stores, a separate repository for specs shared across code repositories, so a platform team can own requirements that other teams read.
Pick it when you work in an existing codebase and want specs that are current by default, not by discipline.
BMAD
BMad Method (Breakthrough Method for Agile AI Driven Development) covers more than specs. Its README describes it as turning an idea or change request into working software without giving up the thinking, with specialized perspectives for product, architecture, UX, development, and testing.
It sizes the process to the work: straight to implementation for clear changes, deeper planning for larger ones. Its stated goal is durable context, carrying product and technical decisions forward instead of re-explaining them in every chat. As of 16 November 2026 the stable line is v6.12 (npx bmad-method install), with a v7 preview alpha that installs as skills and changes often.
Pick it when you want a full method with planning roles, and you're comfortable adopting its workflow end to end.
The difference that matters: after the first build
All four do a good job of the first build. The harder question is what the next agent reads in a month.
- OpenSpec keeps main specs current through archiving.
- Spec Kit leaves the choice to the team, and the easiest option, an immutable record, is what most teams end up with.
- BMAD aims to carry decisions forward as context.
- Kiro's docs don't say.
None of them sees a decision made outside the tool. A requirement changed in a customer call, a constraint agreed in a pull request review, or a scope cut decided in Slack never reaches the spec unless someone writes it back. That is how spec drift starts, covered in spec-driven development problems.
Where Lockstep fits
Lockstep handles the decisions that happen outside the spec tool. It captures them from PRDs, Slack, and pull requests, and each becomes binding when its owner approves it; a changed requirement replaces the old version instead of overwriting it. Claude Code is briefed on the current decisions that apply at the start of each session, alongside whatever spec tool you use. An opt-in check can flag code changes that may conflict with a decision; it is advisory.
It doesn't generate specs, plans, or tasks. Session briefings work with Claude Code today. See how it works.
Sources checked 16 November 2026
- https://github.com/github/spec-kit
- https://github.github.io/spec-kit/how-to/existing-projects.html
- https://kiro.dev/docs/specs/
- https://github.com/Fission-AI/OpenSpec
- https://github.com/bmad-code-org/BMAD-METHOD
Related reading
For the product side, see spec-driven development for product managers. For a requirements template, see the PRD template for AI coding agents. For setting up Spec Kit in Claude Code, see Spec Kit with Claude Code. For Kiro against Claude Code in depth, see Kiro vs Claude Code.
Frequently asked questions
- What is the difference between Spec Kit and Kiro?
- Spec Kit is a toolkit you add to the coding agent you already use; it runs as slash commands that produce constitution.md, spec.md, plan.md, and tasks.md. Kiro is its own editor, with specs made of requirements.md, design.md, and tasks.md, and separate bugfix specs.
- What is the difference between Spec Kit and OpenSpec?
- Spec Kit organizes work by feature, and leaves it to each team to decide whether specs are kept current after the build. OpenSpec organizes work as changes: each change proposes spec updates, and archiving it merges them into the main specs, so specs stay current by default. OpenSpec also emphasizes existing codebases.
- What is BMAD?
- BMad Method, short for Breakthrough Method for Agile AI Driven Development, is a free and open-source method with workflows and specialized agents for product, architecture, UX, development, and testing. It sizes the process to the change, from direct implementation for small changes to deeper planning for large ones.
- Which spec-driven development tool should I use?
- Spec Kit if you want a light structure inside your current agent, Kiro if you want an editor built around specs, OpenSpec if you work in an existing codebase and want specs that stay current, and BMAD if you want a full agile method with planning roles. Try one on a single feature first.
- Do these tools keep specs in sync with code?
- Not automatically. OpenSpec updates specs when a change is archived. Spec Kit asks teams to choose a maintenance model after the first change. Specs still go stale when decisions change outside the tool, such as in a meeting or a pull request review.
Keep reading