/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

bmad-code-org/BMAD-METHOD

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T19:48:39.127Z

1mo ago

bmad-code-org/BMAD-METHOD

BMAD-METHOD is a large, actively maintained Node.js open source framework for AI-driven agile development. It ships as an installable CLI/package, includes a documentation site and tests, and is positioned around structured agent workflows, specialized roles, and multi-agent collaboration across the development lifecycle.

Loading tags...

Stars42,961

Forks5,152

Default branchmain

Last pushed2026-03-29T21:01:09Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if Claude Code is your target runtime and you want a more opinionated, prepackaged BMAD variant. Choose upstream if you care more about staying current, broad platform support, and the most maintained baseline.

Prefer this fork if you want a Claude Code-tuned BMAD experience with added routing, continuity, and dashboard-oriented workflows. Prefer upstream if you need the newest platform support, installer work, and fastest-moving BMAD features.

Choose this fork if you want BMAD adapted into a design-studio operating model with custom workflow semantics and module structure. Stay with upstream if you need the latest general-purpose BMAD features, installer/platform support, and lower maintenance risk.

Choose this fork if Chinese localization and a more curated adoption path matter more than staying current with upstream. Choose upstream if you need the latest installer, platform support, and the broadest feature set.

Choose this fork if Beads integration is a requirement and you want BMAD adapted around that workflow. Choose upstream if you want the newest BMAD platform support, installer work, and lower maintenance risk.

Choose this fork if you want richer preset workflows and expansion packs, especially for game dev or creative writing. Choose upstream if you need the latest installer, platform support, and lower maintenance risk.

Prefer this fork if you want a feature-rich, specialized BMAD distribution with extra domain packs and platform integrations. Prefer upstream if you value staying current, lower maintenance risk, and the broadest compatibility with the latest BMAD changes.

Choose this fork only if its custom workflows and installer conventions match your process and you are comfortable living behind upstream. If you want the newest BMAD platform support, installer fixes, and active mainline evolution, upstream is the safer default.

Choose this fork if you want the extra workflow packaging and automation it appears to add, and you do not need the latest upstream platform and installer work. If you want maximum compatibility and active upstream velocity, upstream is the safer default.

Choose this fork if you want a more focused BMAD variant with installer polish and a reduced surface area. Choose upstream if you need the fullest, newest, and most actively maintained BMAD feature set.

Fork comparison

24601/BMAD-AT-CLAUDE

54/100

slowing

significant_divergence

Choose this fork if Claude Code is your target runtime and you want a more opinionated, prepackaged BMAD variant. Choose upstream if you care more about staying current, broad platform support, and the most maintained baseline.

Likely purpose

To adapt BMAD-METHOD for Claude Code users and workflows, with extra emphasis on Claude integration, custom team/agent bundles, and downstream packaging.

Best for

Claude Code users who want BMAD-style agent workflows without doing the port themselves.; Adopters who value Claude-specific integration over staying current with upstream.; Teams that prefer customized downstream bundles for game dev, fullstack, or minimal-UI workflows.

Additional features

Claude Code integration and a Claude-specific port of the framework.
Custom integration routing under `bmad-claude-integration/` for Claude-oriented behavior.
Expanded generated team and agent bundles in `dist/`, including fullstack, no-UI, IDE-minimal, and game-dev expansion packs.
Flattener/CLI integration work with custom directory support.
Hybrid hooks/subagent message-queue experimentation aimed at Claude subagent workflows.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

It appears materially behind upstream core, with 385 commits behind and a much older release line in the fork history.
Likely missing or lagging upstream’s newest workflows, platform support, installer refactors, and recent agent/skill updates from the actively maintained mainline.
Some upstream capabilities appear harder to rely on here because the fork diverged heavily into Claude-specific packaging rather than tracking the canonical BMAD release stream.
It trails upstream by 385 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Best fit for Claude Code users who want BMAD concepts already adapted to that environment.
Likely useful if you want prebuilt team/agent distributions instead of assembling them yourself.
The fork shows real productization work, not just a shallow README tweak.

Risks

High divergence means upstream docs, workflows, and release assumptions may not match this fork.
Being behind upstream increases the chance of missing bug fixes, installer improvements, and newer platform integrations.
Experimental Claude/subagent plumbing may be less stable than upstream’s mainline paths.