bmad-customize

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-customize-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-customize
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-customize
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-customize-pastasus

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. - Verified writes: Shows a diff before writing, then verifies the result with the BMad customization resolver or a manual base-team-user merge fallback. - Use Case: A user says "make the PM agent always ask about budget constraints" and the Skill writes a bmad-agent-pm.toml override appending to persistent_facts, then confirms the merged result. ## Quick Start Ask the assistant to customize a BMad skill, for example: "customize bmad so the PRD workflow uses my own 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 override only contains the fields you change, and BMad merges it over the skill's base `customize.toml` at load time.

What is the difference between team and user override files 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 preferences like tone or private facts.

How do I find which BMad skills support customization?

Run the list_customizable_skills.py script with your project root. It scans installed skills for `customize.toml` files and returns JSON grouping agent and workflow surfaces, including whether overrides already exist.

Can I change workflow step logic or ordering with a BMad override?

No. Overrides can only set fields exposed in the target's `customize.toml`, such as templates, activation step prepends or appends, and persistent facts. Deeper behavior changes require a feature request or building a custom skill with bmad-builder.

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. Verify with resolve_customization.py to see the merged output, then correct the override and re-verify.