What problem does it solve? Teams using BMad skills often need to adjust agent personas, workflow steps, templates, or output paths without forking the original skill files. This Skill translates plain-English customization requests into correctly placed, correctly merged TOML override files under the project's _bmad/custom/ directory. ## Core Features & Use Cases - Discovery of customizable skills: Runs a scanner script that lists every installed BMad skill exposing an [agent] or [workflow] customization surface, along with existing team or user overrides. - Guided override authoring: Classifies intent (directed, exploratory, audit, cross-cutting), picks the right surface (agent vs workflow), and composes sparse TOML overrides with correct merge semantics for scalars, append arrays, and keyed tables. - Team vs user placement: Writes policy-level changes to committed {skill-name}.toml files and personal preferences to gitignored {skill-name}.user.toml files. - Verification loop: Runs the BMad customization resolver (or a manual base-team-user merge fallback) to confirm the override landed, and re-enters composition if it did not. - Use Case: A product manager wants the PM agent to always include company compliance facts in every workflow. The Skill locates bmad-agent-pm, adds a persistent_facts entry to a team override file, and verifies the merged result. ## Quick Start Ask the agent to customize a BMad skill, for example: customize the bmad PM agent so it always includes our security review policy in every workflow.
