# BMAD vs Spec-kit: Choosing the Right Framework

> A direct comparison of the two main SDD frameworks  when to use each, their trade-offs, and how to decide what fits your team and project.

- **Source:** https://ainativesoftware.engineering/roadmap/day-6/bmad-vs-spec-kit-choosing-the-right-framework
- **Site:** AI-Native Software Engineering — https://ainativesoftware.engineering/book

- **Day:** 6 · position 3 of 3
- **Reading time:** 1 minute
- **Day overview:** [Day 6](https://ainativesoftware.engineering/roadmap/day-6.md)

A direct comparison of the two main SDD frameworks  when to use each, their trade-offs, and how to decide what fits your team and project.

## Theory

Both BMAD and Spec-kit operationalize Spec-Driven Development, but they make very different trade-offs.

| Dimension | Spec-kit | BMAD |
|---|---|---|
| **Setup overhead** | Low  file templates in any repo | Higher  framework installation and configuration |
| **Persona model** | None (you drive the workflow) | Rich set of role-based AI personas |
| **Artifact depth** | Spec + Plan + Tasks | Brief, PRD, Architecture, Stories, Tasks |
| **Best for** | Small features, individual engineers, greenfield projects | Complex features, cross-functional teams, brownfield codebases |
| **GitHub integration** | Native PR workflow | Configurable, not GitHub-specific |
| **Learning curve** | Gentle | Steeper, but pays off on larger projects |


### When to use Spec-kit

- You want a low-friction entry point into SDD
- Your team already uses GitHub heavily
- The scope is a single feature or small project
- You need to onboard engineers quickly


### When to use BMAD

- You're working on a complex, multi-phase project
- You need consistent artifacts across a cross-functional team
- You're working in a brownfield codebase where context management matters
- You want quality gates and persona-guided reasoning built into the workflow


### The frameworkless option

For very small tasks or experienced engineers, neither framework may be necessary. Frameworkless SDD  writing a quick SPEC.md and TASKS.md manually  is always a valid starting point.

**Theory resources**

- [BMAD vs Spec-kit - Video Comparison](https://www.youtube.com/watch?v=sGYvGUkerA0)

## Practice

Run this in a repository you already know, not a toy project.

1. Take the Todo application you built with BMAD in the previous exercise.
2. Optionally, re-implement a portion of it using Spec-kit's approach instead.
3. Compare the two experiences across these dimensions:
   - How did spec generation differ?
   - How did the generated artifacts differ in depth and structure?
   - Which approach felt more natural for your team composition?
   - Where was AI assistance more or less effective?
4. Write a one-page decision guide: given a project type and team size, which framework would you recommend and why?

- **Previous topic:** [The BMAD Workflow Map](https://ainativesoftware.engineering/roadmap/day-6/the-bmad-workflow-map.md)
- **Next topic:** [AI in Requirements and Product Collaboration](https://ainativesoftware.engineering/roadmap/day-7/ai-in-requirements-and-product-collaboration.md)

---

_AI-Native Software Engineering by Alfonso Graziano (O'Reilly Media, Early Release; print edition February 2027). Every page of ainativesoftware.engineering is also served as Markdown: append `.md` to any URL. Index: https://ainativesoftware.engineering/llms.txt — whole site in one file: https://ainativesoftware.engineering/llms-full.txt._