bmad-customize

Topics in the source

• BMad Customize
• Preflight
• Activation
• Step 1: Classify intent
• Step 2: Discovery
• Step 3: Determine the right surface
• Step 4: Compose the override
• Step 5: Team or user placement

Translate the user's intent into a correctly-placed TOML override file under {project-root}/bmad/custom/ for a customizable agent or workflow skill. Discover, route, author, write, verify. Scope v1: per-skill [agent] overrides (bmad-agent- .toml / .user.toml) and per-skill [workflow] overrides (bmad- .toml / .user.toml). Central config ({project-root}/bmad/custom/config.toml) is out of scope — point users at the How to Customize BMad guide. When the target's customize.toml doesn't expose what the user wants, say so plainly. Don't invent fields. No {project-root}/bmad/ → BMad is not set up here. Offer to run the bmad skill's setup, installing bmad first if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad). Stop if the user declines. {project-root}/bmad/scripts/resolvecustomization.py missing → continue, but Step 6 verify falls back to manual merge. Both present → proceed. Greet the user. If the user's invocation already names a target skill AND a specific change, jump to Step 3. Directed — specific skill + specific change → Step 3. Exploratory — "what can I customize?" → Step 2. Audit/iterate — wants to review or change something already customized → Step 2,

This is an excerpt. Refer to the complete source and its current requirements.