Concepts

What BMAD+ is and the ideas behind it: agents, skills, packs and memory, and how they fit together.

Pages in this section

• How BMAD+ works

  What BMAD+ puts in your project, who executes what, and how a request such as "Atlas, ..." becomes files: host-managed execution, the AGENTS.md spine, packs, agents, skills, workflows.

• Intake: ask first, then act

  Why a pack asks before it acts, how an intake.yaml defines its questions field by field, how answers get a status, and a complete design read with real output. Includes how to write your own.

• Swarms of sub-agents

  When to run a panel, a jury or a fanout of sub-agents, the four files that define one, seeded dealing, the 26-unit budget, honest tallies, and a worked buyer panel with real output.

• Nexus: autopilot, parallel work and durable runs

  Autopilot with checkpoints, supervised parallel work, plan export from a swarm, and the durable runtime (create, start, launch, collect, verify, accept) with its Codex adapter and limits.

• Memory: decisions, lessons and the brain

  How BMAD+ keeps decisions, lessons and handoffs between sessions: project memory, the global or portfolio brain and its detection, Zecher, the mem and memory commands, what is never overwritten.

• Code review and human acceptance

  How review scope, anchor and gate make a code review checkable, the built-in rules, and how a person plays an acceptance recipe that is read, triaged and gated. Why a release tag needs one.

• The registry and skills

  registry.yaml as the single source of truth: pack fields, uses_skills, external_module, pipelines, intake, the guarding checks, what is generated, and how a team adds an agent or a pack with Maker.