bmad-code-org/bmad-method

Breakthrough Method for Agile Ai Driven Development

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 16 minutes ago
Added to GitGenius on August 31st, 2026
Created on April 13th, 2025
Open Issues & Pull Requests: 31 (+0)
Number of forks: 5,975
Total Stargazers: 52,519 (+0)
Total Subscribers: 410 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.7 hours
Mean response time: 12.2 days
90th percentile: 48.9 days
Tracked items: 1,064

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "ide-tool-issue" is answered fastest, typically in about 18 hours, while "priority:high" waits about 10 days. Only 14% of issues opened in the past year have been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 21
New in 7 days: 5
Closed in 7 days: 86
Avg open age: 21 days
Stale 30+ days: 7
Stale 90+ days: 0

Recent activity

Opened in 7 days: 4
Closed in 7 days: 86
Comments in 7 days: 2
Events in 7 days: 5

Top labels

  • bug (151)
  • priority:medium (66)
  • documentation (26)
  • feature (23)
  • priority:high (20)
  • enhancement (19)
  • ide-tool-issue (13)
  • good-first-issue (12)

Detailed Description

BMad Method is an agile development framework that integrates AI-driven workflows to guide teams from initial concept through implementation and learning.

The framework addresses the problem that AI coding assistants, while effective at implementation, often encode unstated assumptions into code without preserving the reasoning behind decisions. BMad keeps developers in control by making important decisions explicit and maintaining them as durable context throughout the development process. It structures work through a delivery loop covering clarification, planning, building, verification, and learning phases. The approach scales to fit the work: straightforward changes move directly to implementation, while complex initiatives receive deeper planning and specialized perspectives from product, architecture, UX, development, and testing roles.

Developers should adopt BMad if they want to preserve architectural and product decisions as living context rather than re-explaining them in repeated conversations with AI tools, or if they need a process that works equally well for new projects and inherited codebases. The framework works end-to-end or integrates into existing delivery workflows through its briefs, specifications, and architecture artifacts. It requires Node.js 20.12 or later, Python 3.10 or later, and the uv package manager.

The project maintains a substantial base of real-world adopters, as evidenced by the fact that nearly all open issues originate from outside users rather than the core team. Maintainers typically respond to new issues and pull requests within a few days. Work in the issue tracker centers on bug fixes, medium-priority items, and documentation improvements.