bmad-customize

Authors TOML override files that customize installed BMad agent and workflow skills.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-customize-joao-victor-medeiros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-customize
Source: https://github.com/Joao-Victor-Medeiros/save-sc/tree/main/.agents/skills/bmad-customize
Command: npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-customize-joao-victor-medeiros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Changing the behavior of installed BMad skills normally requires editing their source files, which breaks on upgrades. This Skill translates plain-English customization requests into correctly placed TOML override files under _bmad/custom/, keeping base skills untouched. ## Core Features & Use Cases - Discovery of customizable skills: Scans installed skills for customize.toml files and lists agent and workflow surfaces with existing override status. - Guided override authoring: Classifies intent, picks the right surface (agent vs workflow), composes sparse TOML overrides with correct merge semantics, and places them as team or user files. - Verification: Runs the BMad customization resolver (or a manual merge fallback) to confirm the override landed as intended. - Use Case: A user says "make the PM agent always include our compliance checklist" — the Skill locates the agent's customize.toml, appends to persistent_facts, writes bmad-agent-pm.toml under _bmad/custom/, and verifies the merged result. ## Quick Start Ask the assistant to customize a BMad skill, for example: change the PRD workflow to use a different output template.

Frequently Asked Questions about bmad-customize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize a BMad skill without editing its source files?▼

Create a TOML override file under `{project-root}/_bmad/custom/` named after the skill, such as `bmad-agent-pm.toml`. The Skill discovers the target's `customize.toml`, composes only the fields you change, and verifies the merged result with the resolver script.

What is the difference between team and user override files in BMad?▼

Team overrides use `{skill-name}.toml` and are committed for shared policies and conventions. User overrides use `{skill-name}.user.toml`, are gitignored, and hold personal tone, private facts, or shortcuts. User layers merge on top of team layers.

How do BMad override files merge with the base customize.toml?▼

Scalars like `icon` or `*_template` are replaced by the override. Arrays such as `persistent_facts` and `activation_steps_prepend` append in order. Keyed arrays of tables merge by their `code` or `id` key, with matching keys replaced and new keys appended.

Can I customize a BMad skill that has no customize.toml?▼

No. Skills without a `customize.toml` expose no customization surface and cannot be overridden. The Skill will say so plainly and can suggest using bmad-builder to create a custom skill instead.

What happens if the BMad resolver script is missing during verification?▼

The Skill falls back to a manual merge: it reads the base `customize.toml`, team override, and user override, applies base → team → user merge rules, and describes how the changed fields resolve.