Maker is a meta-agent that designs, validates and packages new BMAD+ agents. Install command, the four creation phases, six prompts, the output folder and what the package is meant for.
Maker is an agent that creates other agents. You describe what you need, Maker walks you through the persona, the capabilities, the automatic activation triggers and the skills, shows you a design preview, and only then generates a package in the format BMAD+ expects. It is the pack for people who want a specialist that does not exist yet, such as a customer-support agent or a release-notes writer, written in the same shape as Atlas or Forge.
Discovery: one batch of five questions: what the agent does, which domain, whether it needs several roles, which tools or APIs it needs, which personality.
Design: a preview table (name, persona and icon, title, roles, pack name, capabilities with codes, triggers, dependencies). Nothing is generated until you approve; Maker iterates until you do.
Generation: the files listed in the outputs section below.
Validation: a self-check of the format, the manifest fields, the pack definition, the uniqueness of the two-letter codes and the integration guide, presented to you as a checklist.
Use it when the agent needs several roles or tools and you want to control every choice.
In your AI assistant
Maker, create a customer support agent. It should triage incoming tickets, draft replies in a calm tone and escalate billing disputes to a human. It needs read access to our help-centre articles. Two roles: Triage and Reply.
What you should get Maker asks its five discovery questions in a single batch (your request already answers several of them), then shows the design preview table and waits for approval. After approval it writes the package in _bmad-output/ready-to-integrate/ and presents the validation checklist.
Use it for a single-purpose agent. You can refine the result afterwards.
In your AI assistant
Maker, quick agent: a release-notes writer named Chronicle that turns a list of merged changes into user-facing notes. Icon: a scroll.
What you should get Only the two questions are asked (purpose, name and icon); everything else gets sensible defaults. The same package files are generated, and you can then ask for edits.
Point Maker at the folder of the agent and say what should change. Edit Agent works on the agent’s SKILL.md where it already is.
In your AI assistant
Maker, edit the agent in _bmad-output/ready-to-integrate/agents/agent-chronicle: add a capability with code BR that drafts a breaking-changes section, and make the description in its front matter more specific so it is not picked for every request that merely mentions an update.
What you should get The agent’s SKILL.md is changed in place, in the folder you named, and Maker keeps the rule that capability codes stay unique. One of its principles is to validate with you before finalising, so expect a summary of the edit to confirm. The package has no separate triggers file: how the agent gets picked comes from the description in its front matter.
Use it before you share or contribute an agent, including one that was not made by Maker.
In your AI assistant
Maker, validate this agent package: _bmad-output/ready-to-integrate/agents/agent-chronicle. List every problem and offer to fix each one.
What you should get A report on four points: SKILL.md format compliance, manifest completeness, uniqueness of capability codes and quality of the triggers (specific enough or not). Each issue comes with an offer to fix it. This reads files; it does not run the agent.
Use it when the design is settled and you want the files in one place.
In your AI assistant
Maker, package the Chronicle agent so I can hand the folder to a contributor.
What you should get The folder _bmad-output/ready-to-integrate/ holds agents/agent-chronicle/SKILL.md, agents/agent-chronicle/bmad-skill-manifest.yaml, pack-definition.yaml and INTEGRATION.md.
Use it to learn the expected structure, or to write an agent by hand.
In your AI assistant
Maker, show me the BMAD+ agent template.
What you should get The template of an agent SKILL.md: front matter with name and description, then the sections Overview, Identity, Communication Style, Principles, Capabilities (code, description, skill) and On Activation.
Maker needs nothing beyond Core and Node.js 20 for the installer: no Python, no key, no network service of its own. Creating and packaging an agent write only into _bmad-output/ready-to-integrate/; Edit Agent changes the SKILL.md of an existing agent wherever you point it. The only data that leaves your machine is what your AI tool sends to its model, as with any other agent.
Warning· The package targets the BMAD+ source, not your installed project
The generated INTEGRATION.md walks you through adding the agent to the BMAD+ source repository: copy the folder to src/bmad-plus/agents/, add the pack entry from pack-definition.yaml to registry.yaml (the single source of truth), add the help line to src/bmad-plus/module-help.csv, then run npm run build and node tools/build/generate-adapters.js --adopt, and finish with the drift checks (npm run build:check, generate-adapters --check --adopt, npm run check:counts). It is meant for contributing agents to BMAD+ itself; Maker does not register a new agent into a project that merely has BMAD+ installed.
Note· Validation is a reading of files
Maker’s checks cover format, fields and uniqueness. They do not prove that the new agent behaves well in practice; test it on a real task before you rely on it.
Note· Provenance
Maker was written by Laurent Rochetta, the author of BMAD+.