BMad Method

BMad has no runtime process of its own. Installation copies one directory per skill (each with a SKILL.md) into the host tool's skills folder, and bmad setup adds shared config and Python helper scripts under _bmad/. A skill does one of three things: loads a persona agent, runs a multi-step workflow, or runs a single task. The host coding agent (Claude Code, Codex, Cursor and others) executes everything.

Work flows through role-based stages: planning skills produce a brief, PRD, UX and architecture documents and a ticket tree, then bmad-build implements a unit of work and runs several reviewer passes, using subagents where the host supports them. For unattended runs, bmad-build-auto handles exactly one ticket per invocation; picking the next ticket is left to a human, a coding session acting as orchestrator, or the separate bmad-loop module. Party mode can run personas inline in one model, as independent subagents, or as a Claude Code agent team.

State is kept in files, not a database. Documents and tickets are written to _bmad-output, inside the active initiative folder when one is set. Each plan file carries a frontmatter status (draft, ready-for-dev, in-progress, in-review, built, done, blocked) that lets a run resume where it stopped. Configuration resolves through layered TOML files, and project context is kept as a verified block in the repository's AGENTS.md.

The method is built around human checkpoints. bmad-build reports intent gaps, irreversible actions and footprint after investigating; anything flagged gets a written plan with open questions that the user answers and approves before implementation. For unattended bmad-build-auto runs, the docs describe dispatching a ticket with Halt after planning., waiting for a person to approve the plan, then dispatching again, and pausing after a ticket until a person says to continue. In party mode the user steers the discussion and can end it; bmad-advanced-elicitation shows proposed improvements that the user accepts or discards; bmad-walkthrough guides a human review of a commit or PR block by block.

npx skills add bmad-code-org/BMAD-METHOD

# In the project folder: install selected skills (the CLI asks which coding tool)
npx skills add bmad-code-org/BMAD-METHOD --skill bmad --skill bmod-core-tools \
  --skill bmod-method --skill bmad-build --skill bmad-ticket

# Codex alternative: install from the plugin marketplace instead
# codex plugin marketplace add bmad-code-org/bmad-plugins

# Then, inside the coding agent chat:
#   bmad setup        -> installs the runtime and scripts under _bmad/
#   bmad status       -> checks versions and suggests the next step
#   /bmad-build Reject empty passwords in the login form.
#   /bmad-party-mode --mode subagent "review the checkout plan"

• Needs a coding tool that supports skills, plus uv; the Skills CLI also needs Node.js, npm and Git. Since v6.11, bmad-build and bmad-build-auto halt if uv (Python 3.11+) is unavailable.
• The Skills CLI installs only the skills you name; include bmad and the module records bmod-core-tools and bmod-method, then run bmad setup.
• Use one installation method per skill (Skills CLI or plugin marketplace) to avoid duplicate commands, and restart the tool if new skills do not appear.
• The installer does not delete skill folders from removed modules; bmad setup offers to clean up renamed or retired skills.
• Breaking changes land in minor releases: in v6.12.0 persistent_facts ships empty and {diff_output} became {diff_file}; the unreleased layout needs bmad migrate method on v6 projects.
• Start bmad-build in a fresh chat; reusing a session from another workflow can mix contexts.

It has no MCP server or client of its own. Its team-adoption guide shows customizations that instruct the host coding agent to call MCP tools the host already has, such as context7 or Linear.

Yes. The code is under MIT license text (GitHub shows NOASSERTION because the LICENSE file adds a trademark notice), and the README says no workflows are paywalled.

Claude Code and Codex have official plugin marketplaces; the Skills CLI also installs the skills for Cursor, Windsurf, Cline, Antigravity and other tools that support skills. Party mode's agent-team option is Claude Code only.

The skills are Markdown SKILL.md files with TOML configuration; helper scripts are Python run through uv. There is no SDK to import.

Partly. bmad-build-auto completes one ticket per invocation and never picks the next one; a coding session acting as orchestrator, or the separate bmad-loop module, must dispatch tickets. It needs a host that can run subagents.