What problem does it solve? Teams using the BMad method often need to adjust agent personas, workflow steps, templates, or output paths without forking the installed skills. This Skill translates plain-English customization requests into correctly placed, correctly merged TOML override files under _bmad/custom/, eliminating guesswork about file naming, merge semantics, and team-versus-user placement. ## Core Features & Use Cases - Discovery of customizable skills: Runs a scanner script that lists every installed BMad skill exposing a customize.toml, grouped by agent or workflow surface, with existing override status. - Guided override authoring: Classifies intent (directed, exploratory, audit, cross-cutting), picks the right surface, composes sparse TOML overrides, and confirms before writing team (.toml) or user (.user.toml) files. - Verification with fallback: Validates the result via resolve_customization.py, or manually replays the base → team → user merge rules when the resolver is missing. - Use Case: A product manager wants the BMad PM agent to always include company compliance facts. The Skill locates bmad-agent-pm, composes a persistent_facts override in _bmad/custom/bmad-agent-pm.toml, and verifies the merged output. ## Quick Start Ask the assistant to customize a BMad skill, for example: customize the bmad agent pm to always include our compliance guidelines as persistent facts.
