bmad-customize

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-customize-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-customize
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-customize
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-customize-hordricjr

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 of customizable skills: Scans installed skill directories 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 confirms before writing. - Verification of applied overrides: Runs the BMad customization resolver (or a manual merge fallback) to show how base, team, and user layers combine. - Use Case: A team lead wants every PRD workflow to prepend a compliance checklist step. The Skill locates the workflow's customize.toml, writes bmad-prd.toml with activation_steps_prepend, and verifies the merged result. ## Quick Start Ask the assistant to customize a BMad skill, for example: change the PM agent's persona and add a persistent fact using bmad-customize.

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 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 changed fields, and writes the override after your confirmation.

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 customization overrides merge with the base configuration?

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

No. Only skills shipping a customize.toml with an [agent] or [workflow] block expose a customization surface. For anything else, the Skill suggests creating a custom skill with bmad-builder or filing a feature request.

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

Common causes are a wrong field name, wrong merge mode (scalar versus array), or wrong file scope. The Skill verifies with resolve_customization.py and re-enters composition using the resolver output to correct the override.