# Concepts · BMAD+ documentation

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

Canonical: https://bmad-plus.rochetta.fr/docs/concepts/
Language: en
BMAD+ version: 0.23.1
Documentation reviewed: 2026-10-19
Author: Laurent Rochetta
License: MIT

[BMAD+ documentation](https://bmad-plus.rochetta.fr/docs/)

## Pages in this section

- [How BMAD+ works](https://bmad-plus.rochetta.fr/docs/concepts/how-bmad-plus-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](https://bmad-plus.rochetta.fr/docs/concepts/intake/): 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](https://bmad-plus.rochetta.fr/docs/concepts/swarm/): 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](https://bmad-plus.rochetta.fr/docs/concepts/nexus-orchestration/): 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](https://bmad-plus.rochetta.fr/docs/concepts/how-memory-works/): 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](https://bmad-plus.rochetta.fr/docs/concepts/code-review-and-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](https://bmad-plus.rochetta.fr/docs/concepts/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.

[Source on GitHub](https://github.com/lrochetta/BMAD-PLUS)