bmad-customize

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

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-customize-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-customize
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-customize
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-customize-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Changing the behavior of installed BMad agents or workflows normally requires editing their source files, which breaks on updates. 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: Scans installed skills for customize.toml surfaces and lists which agents and workflows can be overridden, including existing team/user overrides. - Guided authoring: Classifies intent (directed, exploratory, audit, cross-cutting), picks the right agent vs workflow surface, and composes sparse TOML overrides with correct merge semantics. - Verified writes: Shows a diff, waits for confirmation, writes team (.toml) or user (.user.toml) files, then verifies the merged result with the resolver script or a manual fallback merge. - Use Case: A team lead wants every PRD workflow to use a custom template and append an org compliance step. The Skill locates bmad-prd, composes the override, writes _bmad/custom/bmad-prd.toml, and verifies the resolved output. ## Quick Start Ask the assistant to customize a BMad skill, for example: override the bmad-prd workflow to use my custom template and add a compliance review step.

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 agent or workflow skill?

Create a TOML override file under `_bmad/custom/` named after the skill, such as `bmad-agent-pm.toml` or `bmad-prd.toml`. Only include the fields you want to change; scalars override base values while arrays like `persistent_facts` append.

What is the difference between team and user override files?

Team overrides use `{skill-name}.toml` and are committed to the repository for shared policies and conventions. User overrides use `{skill-name}.user.toml`, are gitignored, and hold personal tone, private facts, or shortcuts.

Can I customize any BMad skill with TOML overrides?

Only skills that ship a `customize.toml` file exposing an `[agent]` or `[workflow]` block are customizable. Skills without that file cannot be overridden, and behavior not exposed in `customize.toml` requires a feature request or a custom skill built with bmad-builder.

How do I verify a BMad customization override was applied?

Run `resolve_customization.py` with the skill install path, project root, and surface key to see the merged output. If the resolver is missing, manually merge base, team, and user layers using scalar-override and array-append rules.

Why is my BMad override not taking effect?

Common causes are a wrong field name, wrong merge mode (treating a scalar as an array), or wrong file scope or location. Re-check the target's `customize.toml` fields and confirm the file sits in `_bmad/custom/` with the exact skill name.