[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79P5GP4RCAP08SNP0S7JRV5":3,"skill-same:01M79P5GP4RCAP08SNP0S7JRV5":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79P5GP4RCAP08SNP0S7JRV5","bmad-customize",null,"Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow'.","OrigoStudio\u002Forigo-design","OrigoStudio","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F256943203?v=4","01M79P1MQHVZ4PTXBQVM11Q00S","Origo Studio","01M79P1MR8S30QEEM0Z6MGX1MA",1,"MIT","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fbmad-customize\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bmad-customize\ndescription: Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow'.\n---\n\n# BMad Customize\n\nTranslate the user's intent into a correctly-placed TOML override file under `{project-root}\u002F_bmad\u002Fcustom\u002F` for a customizable agent or workflow skill. Discover, route, author, write, verify.\n\nScope v1: per-skill `[agent]` overrides (`bmad-agent-\u003Crole>.toml` \u002F `.user.toml`) and per-skill `[workflow]` overrides (`bmad-\u003Cworkflow>.toml` \u002F `.user.toml`). Central config (`{project-root}\u002F_bmad\u002Fcustom\u002Fconfig.toml`) is out of scope — point users at the [How to Customize BMad guide](https:\u002F\u002Fdocs.bmad-method.org\u002Fhow-to\u002Fcustomize-bmad\u002F).\n\nWhen the target's `customize.toml` doesn't expose what the user wants, say so plainly. Don't invent fields.\n\n## Preflight\n\n- No `{project-root}\u002F_bmad\u002F` → BMad isn't installed. Say so, stop.\n- `{project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py` missing → continue, but Step 6 verify falls back to manual merge.\n- Both present → proceed.\n\n## Activation\n\nLoad `_bmad\u002Fconfig.toml` and `_bmad\u002Fconfig.user.toml` from `{project-root}` 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.\n\n## Step 1: Classify intent\n\n- **Directed** — specific skill + specific change → Step 3.\n- **Exploratory** — \"what can I customize?\" → Step 2.\n- **Audit\u002Fiterate** — wants to review or change something already customized → Step 2, lead with skills that have existing overrides; read the existing override in Step 3 before composing.\n- **Cross-cutting** — could live on multiple surfaces → Step 3, choose agent vs workflow explicitly with the user.\n\n## Step 2: Discovery\n\n```\npython3 {skill-root}\u002Fscripts\u002Flist_customizable_skills.py --project-root {project-root}\n```\n\nUse `--extra-root \u003Cpath>` (repeatable) if the user has skills installed in additional locations.\n\nGroup the returned `agents` and `workflows` for the user; for each show name, description, whether `has_team_override` or `has_user_override` is true. Surface any `errors[]`. For audit\u002Fiterate intents, lead with already-overridden entries.\n\nEmpty list: show `scanned_roots`, ask whether skills live elsewhere (offer `--extra-root`); otherwise stop.\n\n## Step 3: Determine the right surface\n\nRead the target's `customize.toml`. Top-level `[agent]` or `[workflow]` block defines the surface.\n\nIf a team or user override already exists, read it first and summarize what's already overridden before composing.\n\n**Cross-cutting intent — walk both surfaces with the user:**\n\n- Every workflow a given agent runs → agent surface (e.g. `bmad-agent-pm.toml` with `persistent_facts`, `principles`).\n- One workflow only → workflow surface (e.g. `bmad-prd.toml` with `activation_steps_prepend`).\n- Several specific workflows → multiple workflow overrides in sequence, not an agent override.\n\n**Single-surface heuristic:**\n\n- Workflow-level: template swap, output path, step-specific behavior, or a named scalar already exposed (`*_template`, `on_complete`). Surgical, reliable.\n- Agent-level: persona, communication style, org-wide facts, menu changes, behavior that should apply to every workflow the agent dispatches.\n\nWhen ambiguous, present both with tradeoff, recommend one, let the user decide.\n\nIntent outside the exposed surface (step logic, ordering, anything not in `customize.toml`): say so; offer `activation_steps_prepend`\u002F`append` or `persistent_facts` as approximations, or recommend `bmad-builder` to create a custom skill.\n\n## Step 4: Compose the override\n\nTranslate plain-English into TOML against the target's `customize.toml` fields. If an existing override was read, frame the change as additive.\n\nMerge semantics:\n\n- **Scalars** (`icon`, `role`, `*_template`, `on_complete`) — override wins.\n- **Append arrays** (`persistent_facts`, `activation_steps_prepend`\u002F`append`, `principles`) — team\u002Fuser entries append in order.\n- **Keyed arrays of tables** (menu items with `code` or `id`) — matching keys replace, new keys append.\n\nOverrides are sparse: only the fields being changed. Never copy the whole `customize.toml`.\n\n**Template swap** (`*_template` scalar): offer to copy the default template to `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}-{purpose}-template.md`, point the override at the new path, offer to help edit it.\n\n## Step 5: Team or user placement\n\nUnder `{project-root}\u002F_bmad\u002Fcustom\u002F`:\n\n- `{skill-name}.toml` — team, committed. Policies, org conventions, compliance.\n- `{skill-name}.user.toml` — user, gitignored. Personal tone, private facts, shortcuts.\n\nDefault by character (policy → team, personal → user), confirm before writing.\n\n## Step 6: Show, confirm, write, verify\n\n1. Show the full TOML. If the file exists, show a diff. Never silently overwrite.\n2. Wait for explicit yes.\n3. Write. Create `{project-root}\u002F_bmad\u002Fcustom\u002F` if needed.\n4. Verify:\n\n   ```\n   python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill \u003Cinstall-path> --key \u003Cagent-or-workflow>\n   ```\n\n   Show the merged output, point out the changed fields.\n\n   **Resolver missing or fails:** read whichever layers exist — `\u003Cinstall-path>\u002Fcustomize.toml` (base), `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` (team), `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` (user) — apply base → team → user with the same merge rules (scalars override, tables deep-merge, `code`\u002F`id`-keyed arrays merge by key, all other arrays append), describe how the changed fields resolve.\n\n   **Verify shows override didn't land** (field unchanged, merge conflict, file not picked up): re-enter Step 4 with the verify output as context. Usually wrong field name, wrong merge mode (scalar vs array), or wrong scope.\n\n5. Summarize what changed, where the file lives, how to iterate. Remind the user to commit team overrides.\n\n## Complete when\n\n- Override file written (or user explicitly aborted).\n- User has seen resolver output (or manual fallback merge summary).\n- User has acknowledged the summary.\n\nOtherwise the skill isn't done — finish or tell the user they're exiting incomplete.\n\n## When this skill can't help\n\n- **Central config** (`{project-root}\u002F_bmad\u002Fcustom\u002Fconfig.toml`) — see the [How to Customize BMad guide](https:\u002F\u002Fdocs.bmad-method.org\u002Fhow-to\u002Fcustomize-bmad\u002F).\n- **Step logic, ordering, behavior not in `customize.toml`** — open a feature request, or use `bmad-builder` to create a custom skill. Offer to help with either.\n- **Skills without a `customize.toml`** — not customizable.\n","# BMad Customize\n\nTranslate the user's intent into a correctly-placed TOML override file under `{project-root}\u002F_bmad\u002Fcustom\u002F` for a customizable agent or workflow skill. Discover, route, author, write, verify.\n\nScope v1: per-skill `[agent]` overrides (`bmad-agent-\u003Crole>.toml` \u002F `.user.toml`) and per-skill `[workflow]` overrides (`bmad-\u003Cworkflow>.toml` \u002F `.user.toml`). Central config (`{project-root}\u002F_bmad\u002Fcustom\u002Fconfig.toml`) is out of scope — point users at the [How to Customize BMad guide](https:\u002F\u002Fdocs.bmad-method.org\u002Fhow-to\u002Fcustomize-bmad\u002F).\n\nWhen the target's `customize.toml` doesn't expose what the user wants, say so plainly. Don't invent fields.\n\n## Preflight\n\n- No `{project-root}\u002F_bmad\u002F` → BMad isn't installed. Say so, stop.\n- `{project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py` missing → continue, but Step 6 verify falls back to manual merge.\n- Both present → proceed.\n\n## Activation\n\nLoad `_bmad\u002Fconfig.toml` and `_bmad\u002Fconfig.user.toml` from `{project-root}` 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.\n\n## Step 1: Classify intent\n\n- **Directed** — specific skill + specific change → Step 3.\n- **Exploratory** — \"what can I customize?\" → Step 2.\n- **Audit\u002Fiterate** — wants to review or change something already customized → Step 2, lead with skills that have existing overrides; read the existing override in Step 3 before composing.\n- **Cross-cutting** — could live on multiple surfaces → Step 3, choose agent vs workflow explicitly with the user.\n\n## Step 2: Discovery\n\n```\npython3 {skill-root}\u002Fscripts\u002Flist_customizable_skills.py --project-root {project-root}\n```\n\nUse `--extra-root \u003Cpath>` (repeatable) if the user has skills installed in additional locations.\n\nGroup the returned `agents` and `workflows` for the user; for each show name, description, whether `has_team_override` or `has_user_override` is true. Surface any `errors[]`. For audit\u002Fiterate intents, lead with already-overridden entries.\n\nEmpty list: show `scanned_roots`, ask whether skills live elsewhere (offer `--extra-root`); otherwise stop.\n\n## Step 3: Determine the right surface\n\nRead the target's `customize.toml`. Top-level `[agent]` or `[workflow]` block defines the surface.\n\nIf a team or user override already exists, read it first and summarize what's already overridden before composing.\n\n**Cross-cutting intent — walk both surfaces with the user:**\n\n- Every workflow a given agent runs → agent surface (e.g. `bmad-agent-pm.toml` with `persistent_facts`, `principles`).\n- One workflow only → workflow surface (e.g. `bmad-prd.toml` with `activation_steps_prepend`).\n- Several specific workflows → multiple workflow overrides in sequence, not an agent override.\n\n**Single-surface heuristic:**\n\n- Workflow-level: template swap, output path, step-specific behavior, or a named scalar already exposed (`*_template`, `on_complete`). Surgical, reliable.\n- Agent-level: persona, communication style, org-wide facts, menu changes, behavior that should apply to every workflow the agent dispatches.\n\nWhen ambiguous, present both with tradeoff, recommend one, let the user decide.\n\nIntent outside the exposed surface (step logic, ordering, anything not in `customize.toml`): say so; offer `activation_steps_prepend`\u002F`append` or `persistent_facts` as approximations, or recommend `bmad-builder` to create a custom skill.\n\n## Step 4: Compose the override\n\nTranslate plain-English into TOML against the target's `customize.toml` fields. If an existing override was read, frame the change as additive.\n\nMerge semantics:\n\n- **Scalars** (`icon`, `role`, `*_template`, `on_complete`) — override wins.\n- **Append arrays** (`persistent_facts`, `activation_steps_prepend`\u002F`append`, `principles`) — team\u002Fuser entries append in order.\n- **Keyed arrays of tables** (menu items with `code` or `id`) — matching keys replace, new keys append.\n\nOverrides are sparse: only the fields being changed. Never copy the whole `customize.toml`.\n\n**Template swap** (`*_template` scalar): offer to copy the default template to `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}-{purpose}-template.md`, point the override at the new path, offer to help edit it.\n\n## Step 5: Team or user placement\n\nUnder `{project-root}\u002F_bmad\u002Fcustom\u002F`:\n\n- `{skill-name}.toml` — team, committed. Policies, org conventions, compliance.\n- `{skill-name}.user.toml` — user, gitignored. Personal tone, private facts, shortcuts.\n\nDefault by character (policy → team, personal → user), confirm before writing.\n\n## Step 6: Show, confirm, write, verify\n\n1. Show the full TOML. If the file exists, show a diff. Never silently overwrite.\n2. Wait for explicit yes.\n3. Write. Create `{project-root}\u002F_bmad\u002Fcustom\u002F` if needed.\n4. Verify:\n\n   ```\n   python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill \u003Cinstall-path> --key \u003Cagent-or-workflow>\n   ```\n\n   Show the merged output, point out the changed fields.\n\n   **Resolver missing or fails:** read whichever layers exist — `\u003Cinstall-path>\u002Fcustomize.toml` (base), `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` (team), `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` (user) — apply base → team → user with the same merge rules (scalars override, tables deep-merge, `code`\u002F`id`-keyed arrays merge by key, all other arrays append), describe how the changed fields resolve.\n\n   **Verify shows override didn't land** (field unchanged, merge conflict, file not picked up): re-enter Step 4 with the verify output as context. Usually wrong field name, wrong merge mode (scalar vs array), or wrong scope.\n\n5. Summarize what changed, where the file lives, how to iterate. Remind the user to commit team overrides.\n\n## Complete when\n\n- Override file written (or user explicitly aborted).\n- User has seen resolver output (or manual fallback merge summary).\n- User has acknowledged the summary.\n\nOtherwise the skill isn't done — finish or tell the user they're exiting incomplete.\n\n## When this skill can't help\n\n- **Central config** (`{project-root}\u002F_bmad\u002Fcustom\u002Fconfig.toml`) — see the [How to Customize BMad guide](https:\u002F\u002Fdocs.bmad-method.org\u002Fhow-to\u002Fcustomize-bmad\u002F).\n- **Step logic, ordering, behavior not in `customize.toml`** — open a feature request, or use `bmad-builder` to create a custom skill. Offer to help with either.\n- **Skills without a `customize.toml`** — not customizable.\n",{"name":5,"description":7},"main","5d8b301b16a0b47e4c97f8c6d68ad82e0f86be2c",".agent\u002Fskills\u002Fbmad-customize",0,"https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design","https:\u002F\u002Fgithub.com\u002FOrigoStudio","Engineering ideas into products","2026-10-23 00:02:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add OrigoStudio\u002Forigo-design --skill bmad-customize",{"tool":38,"command":39},"bunx","bunx skills add OrigoStudio\u002Forigo-design --skill bmad-customize",{"tool":41,"command":42},"pnpm","pnpm dlx skills add OrigoStudio\u002Forigo-design --skill bmad-customize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fbmad-customize\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"scripts\u002Flist_customizable_skills.py","SCRIPT","脚本",8061,"https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fbmad-customize\u002Fscripts\u002Flist_customizable_skills.py",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"scripts\u002Ftests\u002Ftest_list_customizable_skills.py",9244,"https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fbmad-customize\u002Fscripts\u002Ftests\u002Ftest_list_customizable_skills.py",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79PWH7HW9TE5FTCHJ1W968C","wds-agent-saga-analyst","Strategic business analyst and product discovery partner for WDS. Use when the user asks to talk to Saga or requests the WDS analyst.","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-agent-saga-analyst\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79PWF5EAQTMC3XZBEFGP3HW","wds-agent-mimir-builder","Implementation agent. Owns the tech audit, the PRD, and the build. Reads Freya's Work Orders and turns them into working code — one verified task at a time.","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-agent-mimir-builder\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79PWCR1845ETM01V6SKVDMN","wds-agent-freya-ux","Strategic UX designer and design thinking partner for WDS. Use when the user asks to talk to Freya or requests the WDS designer.","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-agent-freya-ux\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79PW9MEM3299WHP4DN0AS46","wds-8-product-evolution","Brownfield improvements — the full WDS pipeline in miniature for existing products","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-8-product-evolution\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79PW81V0VQJJP0A9A47WR8N","wds-7-design-system","Create, import, browse, and maintain design system components and tokens","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-7-design-system\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79PW550F0KPHSWF5Z8Z529B","wds-6-asset-generation","Generate visual and text assets from specifications through AI-powered creative production","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-6-asset-generation\u002FSKILL.md",[],[]]