bmad-customize

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-customize-unbakedcosmos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-customize
Source: https://github.com/unbakedcosmos/thumbnailer/tree/main/.claude/skills/bmad-customize
Command: npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-customize-unbakedcosmos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Customizing installed BMad skills requires knowing which fields each skill exposes, where override files belong, and how team and user layers merge. This Skill translates plain-English change requests into correctly placed, verified TOML overrides under _bmad/custom/ without hand-editing or guessing field names. ## Core Features & Use Cases - Discovery and routing: Scans installed skills via a Python script to list every customizable agent and workflow surface, including which ones already have team or user overrides. - Override authoring: Composes sparse TOML overrides against each skill's customize.toml, applying correct merge semantics for scalars, append arrays, and keyed menu items. - Verified writes: Shows a diff, waits for confirmation, writes the team (.toml) or user (.user.toml) file, then verifies the result with the BMad customization resolver or a manual merge fallback. - Use Case: A user says "make the PM agent always include our compliance checklist." The Skill identifies the agent surface, adds the checklist to persistent_facts in bmad-agent-pm.toml, and verifies the merged output. ## Quick Start Ask the assistant to customize a BMad skill, for example: change the PRD workflow to use a different output template for this project.

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 sparse TOML override in `{project-root}/_bmad/custom/` named after the skill, containing only the fields you want to change. The BMad resolver merges it over the skill's base `customize.toml` at load time.

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

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.

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, and keyed menu items merge by their `code` or `id`. Layers apply base, then team, then user.

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

No. Skills without a `customize.toml` expose no customization surface, so overrides cannot target them. The recommended path is to use the bmad-builder skill to create a custom skill instead.

Why did my BMad override not take effect after writing the file?▼

Common causes are a wrong field name, using a scalar where an append array is expected, or placing the file in the wrong scope. Run `resolve_customization.py --skill <path> --key <agent-or-workflow>` to inspect the merged output and diagnose the mismatch.