bmad-customize

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Installed BMad skills expose only a fixed set of customization points, and hand-editing override files risks wrong field names, wrong merge modes, or wrong placement. This Skill translates plain-English customization requests into correctly placed, verified TOML overrides under _bmad/custom/. ## Core Features & Use Cases - Discovery and routing: Scans installed skills for customize.toml surfaces, classifies them as agent or workflow, and reports existing team/user overrides. - Override authoring: Composes sparse TOML overrides with correct merge semantics (scalars override, arrays append, keyed tables merge by code/id). - Team vs user placement: Writes policy-level changes to committed {skill-name}.toml and personal changes to gitignored {skill-name}.user.toml. - Verification: Runs the BMad customization resolver (or a manual base → team → user merge fallback) to confirm the override landed. - Use Case: A user says "make the PM agent always include our compliance checklist" — the Skill locates bmad-agent-pm, composes a persistent_facts override, writes it to _bmad/custom/bmad-agent-pm.toml, and verifies the merged result. ## Quick Start Ask the assistant to customize a BMad skill, for example: customize the bmad PM agent to always include our team's compliance checklist in every workflow.

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?▼

State the target skill and the change you want in plain English. The Skill reads the target's customize.toml, composes a sparse TOML override, writes it under _bmad/custom/, and verifies the merged result with the resolver script.

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

Team overrides live in {skill-name}.toml and are committed for policies and org conventions. User overrides live in {skill-name}.user.toml, are gitignored, and hold personal tone, private facts, or shortcuts.

How do TOML overrides merge with the base customize.toml?▼

Scalars like icon or template paths are replaced by the override. Arrays such as persistent_facts and activation_steps 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 and suggest using bmad-builder to create a custom skill instead.

What happens if the BMad resolver script is missing?▼

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

Why did my BMad override not take effect?▼

Common causes are a wrong field name, wrong merge mode (scalar versus array), or wrong file scope. The Skill re-enters composition using the resolver output as context to diagnose and fix the override.