bmad-customizelisted

## Metodoloji Meta yuzey: urettigi yuzeyler arastirma metodolojisini miras alir (`docs/bmad/research-methodology.md`). Bu yuzeyin ciktisi metodoloji kapsami disinda kalamaz. # BMad Customize Translate the user's intent into a correctly-placed TOML override file under `{metodoloji-root}/custom/` for a customizable agent or workflow skill. Discover, route, author, write, verify. Scope v1: per-skill `[agent]` overrides (`bmad-agent-<role>.toml` / `.user.toml`) and per-skill `[workflow]` overrides (`bmad-<workflow>.toml` / `.user.toml`). Central config (`{metodoloji-root}/custom/config.toml`) is out of scope — point users at the [How to Customize BMad guide](https://docs.bmad-method.org/how-to/customize-bmad/). When the target's `customize.toml` doesn't expose what the user wants, say so plainly. Don't invent fields. ## Preflight - No `{metodoloji-root}/bmad/` → BMad isn't installed. Say so, stop. - `{metodoloji-root}/hooks/engine/resolve_customization.py` missing → continue, but Step 6 verify falls back to manual merge. - Both present → proceed. ## Activation Load `bmad/config.toml` and `bmad/config.user.toml` from `{metodoloji-root}` (the plugin installation — configuration is source material, never a project file) for `user_name` (default `BMad`) and `communication_language` (default `English`). Greet. If the user's invocation already names a target skill AND a specific change, jump to Step 3. ## Step 1: Classify intent - **Directed** — specific skill + specific ch