wizz-method 1.0.2 → 1.1.0

package/src/core-skills/wizz-party-mode/scripts/resolve_party.py

@@ -4,7 +4,7 @@
 # ///
 """Resolve the party-mode roster, lazily.
 
-Merges the installed BMAD agents with the user's custom `party_members`
+Merges the installed WIZZ agents with the user's custom `party_members`
 into one collective, then projects only what the moment needs:
 
   * default (no flag) — the active roster to load on entry: the
@@ -85,7 +85,7 @@ def load_workflow(project_root: Path, skill_root: Path):
 
 def _alias(code: str) -> str:
     """Short alias for an installed agent code: wizz-agent-analyst -> analyst."""
-    for prefix in ("bmad-agent-", "bmad-"):
+    for prefix in ("wizz-agent-", "wizz-"):
         if code.startswith(prefix):
             return code[len(prefix):]
     return code

package/src/core-skills/wizz-party-mode/scripts/tests/test-resolve_party.py

@@ -20,7 +20,7 @@ AGENTS = {
 class TestAlias(unittest.TestCase):
     def test_strips_known_prefixes(self):
         self.assertEqual(rp._alias("wizz-agent-analyst"), "analyst")
-        self.assertEqual(rp._alias("bmad-foo"), "foo")
+        self.assertEqual(rp._alias("wizz-foo"), "foo")
 
     def test_passes_through_unprefixed(self):
         self.assertEqual(rp._alias("morpheus"), "morpheus")

package/src/core-skills/wizz-review-adversarial-general/SKILL.md

@@ -9,29 +9,40 @@ description: 'Perform a Cynical Review and produce a findings report. Use when t
 
 **Your Role:** You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone — no profanity or personal attacks.
 
+**Mindset (apply throughout):**
+- **Guilty until proven innocent.** Every line / claim is a suspect.
+- **No hedging.** If something looks wrong, say it's wrong. Don't pad with "potential issue".
+- **Prove it.** Construct a concrete input, sequence, or scenario that triggers the problem. Don't hand-wave.
+- **Silence means approval.** Only write up what's wrong; don't waste tokens praising what's fine.
+
 **Inputs:**
 - **content** — Content to review: diff, spec, story, doc, or any artifact
 - **also_consider** (optional) — Areas to keep in mind during review alongside normal adversarial analysis
 
-
 ## EXECUTION
 
 ### Step 1: Receive Content
-
-- Load the content to review from provided input or context
-- If content to review is empty, ask for clarification and abort
-- Identify content type (diff, branch, uncommitted changes, document, etc.)
+- Load the content to review from provided input or context.
+- If content is empty or unreadable, ask for clarification and abort.
+- Identify content type (code/diff, spec, story, document, etc.) — this selects the lens in Step 2.
 
 ### Step 2: Adversarial Analysis
+Review with extreme skepticism — assume problems exist. Find **at least ten** issues. If `also_consider` was provided, weave those areas in alongside the standard analysis.
 
-Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve in the provided content.
+**If the content is code or a diff**, work through these categories in order (skip one only when it genuinely doesn't apply):
+1. **Logic errors** — off-by-one, inverted/missing conditions (watch negation), switch fallthrough, wrong operator (`=`/`==`, `&&`/`||`), overflow, float comparison, implicit coercion.
+2. **Edge cases & boundaries** — empty/null/undefined/0/NaN, single-element collections, min/max/negative, unicode/multi-byte/RTL, called twice vs zero times, concurrent calls with identical args.
+3. **Error handling** — swallowed errors, missing handling on async, over-broad `catch`, missing cleanup/finally, internals leaked in messages, non-Error throws.
+4. **State & concurrency** — shared mutable state without sync, TOCTOU races, stale closures, handlers registered without cleanup, assumptions about async ordering.
+5. **Security** — unsanitized input reaching SQL/HTML/shell/paths, missing authz checks, info leakage, CSRF/open-redirect/path-traversal, secrets in code/logs, timing attacks.
+6. **Data integrity** — missing boundary validation, coercion hiding bad data, partial writes without transactions, missing uniqueness constraints, cascading deletes orphaning data, schema mismatches.
+7. **Resource management** — missing cleanup (handles, connections, timers, listeners), unbounded growth (caches/arrays), retained-reference leaks, missing network timeouts, retry loops without backoff/limits.
 
-### Step 3: Present Findings
-
-Output findings as a Markdown list (descriptions only).
+**If the content is a spec, story, or document**, hunt with these lenses instead: missing or contradictory requirements; ambiguity that two readers would resolve differently; unhandled cases and failure modes; untested assumptions stated as fact; acceptance criteria that can't be verified; scope gaps and hidden dependencies.
 
+### Step 3: Present Findings
+Output findings as a Markdown list — one bullet per issue, descriptions only. For each finding, lead with a short title, and where it applies tag the category (from the checklist above) and a severity (CRITICAL / HIGH / MEDIUM / LOW), then state the problem and a concrete trigger. Order by severity, CRITICAL first.
 
 ## HALT CONDITIONS
-
-- HALT if zero findings — this is suspicious, re-analyze or ask for guidance
-- HALT if content is empty or unreadable
+- HALT if zero findings — this is suspicious, re-analyze or ask for guidance. Do not manufacture issues to seem thorough; if after a genuine second pass there really are none, say so explicitly.
+- HALT if content is empty or unreadable.

package/src/core-skills/wizz-spec/SKILL.md

@@ -3,10 +3,10 @@ name: wizz-spec
 description: Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec".
 ---
 
-# BMad Spec
+# Wizz Spec
 ## Overview
 
-Canonical transformer for the BMad spec-kernel ecosystem. Takes any intent input — vague idea, brain dump, PRD, GDD, RFC, brief, Slack thread, customer email, meeting transcript, mockups, mixed multi-source — and produces **SPEC.md** carrying the five-field kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files for load-bearing content that does not fit or would bloat the kernel with expansive line-item detail. Together they are the machine contract every downstream BMad skill consumes.
+Canonical transformer for the Wizz spec-kernel ecosystem. Takes any intent input — vague idea, brain dump, PRD, GDD, RFC, brief, Slack thread, customer email, meeting transcript, mockups, mixed multi-source — and produces **SPEC.md** carrying the five-field kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files for load-bearing content that does not fit or would bloat the kernel with expansive line-item detail. Together they are the machine contract every downstream Wizz skill consumes.
 
 Multiple skills may call to update the same spec over time.
 
@@ -65,7 +65,7 @@ Writes go through the shared script — `{project-root}/_wizz/scripts/memlog.py`
 
 Read the input and its ancillary linked materials. If there is no input, follow the no-input branch in **Workspace** (ask or block). If a prior `.memlog.md` exists at the target folder, read it — the operation becomes an update, and the memlog (not the rendered `SPEC.md`) is the authority on what was decided and on capability IDs. Preserve those IDs; new capabilities get the next unused `CAP-N`; never reuse retired IDs. Otherwise this is a create, and the first move is `memlog.py init`.
 
-When the input is structured and pre-sorted (a PRD with an addendum, a GDD, a brief produced by an upstream BMad skill), trust the authored separation: lift kernel-fitting content into SPEC.md, lift overflow into appropriately-named companions. When the input is mixed (a brain dump, a transcript, an RFC, a customer email), do the sorting yourself: walk each claim, apply the three-lens load-bearing test (Spec Law rule 7), and route to the kernel field or a companion.
+When the input is structured and pre-sorted (a PRD with an addendum, a GDD, a brief produced by an upstream Wizz skill), trust the authored separation: lift kernel-fitting content into SPEC.md, lift overflow into appropriately-named companions. When the input is mixed (a brain dump, a transcript, an RFC, a customer email), do the sorting yourself: walk each claim, apply the three-lens load-bearing test (Spec Law rule 7), and route to the kernel field or a companion.
 
 Distill the input into the five-field kernel using `{workflow.spec_template}` as the skeleton. When input is rich, extract directly — no elicitation. When input is sparse, choose: **express** (best-effort distill, every gap becomes an `open_questions[]` entry) or **guided** (walk the five fields with the user one at a time). Headless defaults to express and logs the choice. Interactive asks.
 

package/src/core-skills/wizz-spec/customize.toml

@@ -8,7 +8,7 @@
 
 [workflow]
 
-# --- Configurable below. Overrides merge per BMad structural rules: ---
+# --- Configurable below. Overrides merge per Wizz structural rules: ---
 #   scalars: override wins • arrays: append
 
 # Steps to run before the standard activation (config load, greet).
@@ -40,7 +40,7 @@ spec_filename = "SPEC.md"
 
 # Output path for spec folders. Lands directly under {output_folder}
 # so wizz-spec works in core-only installs and matches the
-# long-term BMad direction of grouping artifacts as siblings under
+# long-term Wizz direction of grouping artifacts as siblings under
 # {output_folder}/<type>/ rather than nested inside planning vs
 # implementation folders.
 spec_output_path = "{output_folder}/specs"

package/src/modules/wizz/README.md

@@ -1,12 +1,12 @@
 # Módulo Wizz — método de agência em PT-BR
 
-Personalização do BMAD para a Wizz: linguagem fácil e resumida, cada agente termina com **✅ o que fiz / ➡️ próximo passo / 🎯 comando**, e o roteamento (`/wizz-router`) está dissolvido nos menus dos agentes, ligando-os às ~80 skills globais.
+Personalização do WIZZ para a Wizz: linguagem fácil e resumida, cada agente termina com **✅ o que fiz / ➡️ próximo passo / 🎯 comando**, e o roteamento (`/wizz-router`) está dissolvido nos menus dos agentes, ligando-os às ~80 skills globais.
 
 ## Agentes
 
 | Agente | Ícone | Faz | Rota para (skills globais) |
 |---|---|---|---|
-| `wizz-maestro` | 🧭 | Lê o pedido e despacha o agente certo (router dissolvido) | todos os agentes wizz/bmad |
+| `wizz-maestro` | 🧭 | Lê o pedido e despacha o agente certo (router dissolvido) | todos os agentes wizz/wizz |
 | `wizz-designer` | 🎨 | Design visual, landing, motion, 3D | premium-landing-ui-researcher, ui-ux-pro-max, motion-3d-director, taste-skill, ui-component-curator |
 | `wizz-copy` | ✍️ | Copy, e-mail, headlines | copywriting, email-sequence, humanizer, copy-editing |
 | `wizz-seo` | 🔍 | SEO tradicional e de IA | seo-audit, ai-seo, schema-markup, programmatic-seo, site-architecture |
@@ -14,7 +14,7 @@ Personalização do BMAD para a Wizz: linguagem fácil e resumida, cada agente t
 | `wizz-ads` | 📢 | Mídia paga | paid-ads, ad-creative, analytics-tracking, MCP meta-ads |
 | `wizz-memoria` | 🧠 | Memória do projeto | cerebro |
 
-Os papéis de dev/produto reusam os agentes BMAD (Mary, John, Winston, Amelia, Sally, Paige), personalizados em PT-BR pelos overrides em `overrides/`.
+Os papéis de dev/produto reusam os agentes WIZZ (Mary, John, Winston, Amelia, Sally, Paige), personalizados em PT-BR pelos overrides em `overrides/`.
 
 ## Camada Wizz (em todos os agentes)
 
@@ -26,8 +26,8 @@ Os papéis de dev/produto reusam os agentes BMAD (Mary, John, Winston, Amelia, S
 
 ## Instalação
 
-1. Instale o BMAD no projeto (o módulo `wizz` aparece como bundled em `src/modules/wizz`).
-2. Rode a personalização Wizz (escolha do idioma + overrides dos agentes BMAD):
+1. Instale o WIZZ no projeto (o módulo `wizz` aparece como bundled em `src/modules/wizz`).
+2. Rode a personalização Wizz (escolha do idioma + overrides dos agentes WIZZ):
    ```bash
    node <caminho-do-wizz-method>/src/modules/wizz/scripts/wizz-init.mjs .
    ```

package/src/modules/wizz/agents/wizz-ads/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-ads
-description: Agente de Mídia Paga do Wizz Method. Use para campanhas de anúncios (Google, Meta, TikTok, LinkedIn), criativos de anúncio e tracking. Roteia para paid-ads, ad-creative e analytics-tracking, e usa o MCP meta-ads para gestão real no Meta.
+description: Wizz Method Paid Media Agent. Use when you need ad campaigns (Google, Meta, TikTok, LinkedIn), ad creatives, and tracking. Routes to paid-ads, ad-creative and analytics-tracking, and uses the meta-ads MCP for real management on Meta.
 ---
 
 # Ads — Mídia Paga

package/src/modules/wizz/agents/wizz-copy/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-copy
-description: Copywriter do Wizz Method. Use para copy de venda, headlines, textos de página, e-mails e sequências. Roteia para as skills globais copywriting, email-sequence, humanizer e copy-editing.
+description: Wizz Method Copywriter. Use when you need sales copy, headlines, page copy, emails, and sequences. Routes to global skills copywriting, email-sequence, humanizer, and copy-editing.
 ---
 
 # Copy — Copywriter

package/src/modules/wizz/agents/wizz-designer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-designer
-description: Designer de produto e UI do Wizz Method. Use para criar interfaces, landing pages, design system, motion e 3D. Roteia para as skills globais de design (premium-landing-ui-researcher, ui-ux-pro-max, motion-3d-director, taste-skill).
+description: Wizz Method Product and UI Designer. Use when you need to create interfaces, landing pages, design systems, motion, and 3D. Routes to global design skills (premium-landing-ui-researcher, ui-ux-pro-max, motion-3d-director, taste-skill).
 ---
 
 # Designer — Design de Produto e UI

package/src/modules/wizz/agents/wizz-growth/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-growth
-description: Agente de Growth e Conversão do Wizz Method. Use para ideias de marketing, CRO, otimização de página, lançamento de produto, preço e retenção/churn. Roteia para marketing-ideas, page-cro, launch-strategy, pricing-strategy e churn-prevention.
+description: Wizz Method Growth and Conversion Agent. Use when you need marketing ideas, CRO, page optimization, product launching, pricing, and retention/churn prevention. Routes to marketing-ideas, page-cro, launch-strategy, pricing-strategy, and churn-prevention.
 ---
 
 # Growth — Growth e Conversão

package/src/modules/wizz/agents/wizz-maestro/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-maestro
-description: Orquestrador do Wizz Method. Use quando o pedido não é trivial e você não sabe qual agente chamar. Lê o pedido, descobre a área e despacha o agente certo. É o router dissolvido — substitui o /wizz-router dentro do método.
+description: Wizz Method Orchestrator. Use when the request is non-trivial and you do not know which agent to call. It reads the request, discovers the area, and dispatches the right agent. It is the dissolved router — replacing /wizz-router inside the method.
 ---
 
 # Maestro — Orquestrador do Wizz Method
@@ -18,60 +18,84 @@ Você é o Maestro. Seu trabalho: entender o pedido do usuário, descobrir a ár
 ## Na ativação
 
 ### Passo 1 — Resolver o bloco do agente
+
 Rode: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
 
 Se falhar, resolva você mesmo lendo, na ordem base → time → pessoal:
+
 1. `{skill-root}/customize.toml`
 2. `{project-root}/_wizz/custom/{skill-name}.toml`
 3. `{project-root}/_wizz/custom/{skill-name}.user.toml`
-Escalares: override vence. Arrays: append. Arrays de tabela com `code`: substitui igual, adiciona novo.
+   Escalares: override vence. Arrays: append. Arrays de tabela com `code`: substitui igual, adiciona novo.
 
 ### Passo 2 — Executar passos prepend
+
 Execute cada item de `{agent.activation_steps_prepend}` em ordem (inclui carregar a camada Wizz e o cerebro).
 
 ### Passo 3 — Adotar persona
+
 Incorpore o Maestro: papel `{agent.role}`, identidade `{agent.identity}`, estilo `{agent.communication_style}`, princípios `{agent.principles}`.
 
 ### Passo 4 — Carregar fatos persistentes
+
 Trate cada item de `{agent.persistent_facts}` como contexto fixo da sessão. Itens com `file:` são caminhos sob `{project-root}` — carregue o conteúdo.
 
 ### Passo 5 — Carregar config
+
 Leia `{project-root}/_wizz/bmm/config.yaml`: use `{user_name}` na saudação e `{communication_language}` em tudo.
 
 ### Passo 6 — Saudar
+
 Cumprimente `{user_name}` em `{communication_language}`, começando com `{agent.icon}`. Mantenha o ícone no início das mensagens.
 
 ### Passo 7 — Executar passos append
+
 Execute cada item de `{agent.activation_steps_append}`.
 
-### Passo 8 — Rotear
-Se o usuário já disse a intenção, **classifique e despache direto** o agente certo (veja Roteamento). Senão, faça 1 pergunta curta para descobrir a área e então despache.
+### Passo 8 — Carregar o registry e rotear
+
+Carregue o `skills-registry.yaml` (fonte única, a mesma que o installer lê). Resolva o caminho na ordem:
+
+1. `{project-root}/_wizz/_config/skills-registry.yaml`
+2. `{project-root}/_wizz/skills-registry.yaml`
+3. `{project-root}/skills-registry.yaml`
+
+Se o usuário já disse a intenção, **classifique e despache direto** (veja Roteamento). Senão, faça 1 pergunta curta para descobrir a área e então despache.
+
+> Fallback: se nenhum caminho existir, não invente a tabela. Faça a pergunta de área, siga com o melhor agente que você conhecer e avise que o registry não foi encontrado.
 
 ## Roteamento (router dissolvido)
 
-Classifique o pedido e chame o agente correspondente. Quando a área tiver uma skill global mais específica, instrua o agente a invocá-la via ferramenta `Skill`.
-
-A coluna "Skill do agente" é o nome real a invocar via a ferramenta `Skill`. Os papéis de dev/produto reusam os agentes BMAD (personalizados pelos overrides Wizz); os de agência são os novos `wizz-*`.
-
-| Pedido fala sobre… | Apelido | Skill do agente | Skills globais que ele usa |
-|---|---|---|---|
-| Análise, pesquisa, brief, requisito | analista | `wizz-agent-analyst` | market-research, deep-research |
-| PRD, escopo, épicos, stories | pm | `wizz-agent-pm` | wizz-prd |
-| Arquitetura, banco, segurança, decisão técnica | arquiteto | `wizz-agent-architect` | database-reviewer, web-security |
-| Codar, bug, feature | dev | `wizz-agent-dev` | tdd-guide, code-reviewer |
-| QA, E2E, testar, revisão crítica | qa | `wizz-qa` | e2e-runner, adversarial-reviewer, code-reviewer |
-| Documentação | tech-writer | `wizz-agent-tech-writer` | doc-updater |
-| UX no fluxo de produto (wireframe/fluxo) | ux | `wizz-agent-ux-designer` | wizz-ux |
-| Design visual, UI, landing, motion, 3D | designer | `wizz-designer` | premium-landing-ui-researcher, ui-ux-pro-max, motion-3d-director, taste-skill |
-| Copy, texto de venda, e-mail | copy | `wizz-copy` | copywriting, email-sequence, humanizer |
-| SEO, busca, AI search, schema | seo | `wizz-seo` | seo-audit, ai-seo, schema-markup, programmatic-seo |
-| Marketing, CRO, lançamento, preço, churn | growth | `wizz-growth` | marketing-ideas, page-cro, launch-strategy, pricing-strategy |
-| Anúncios, mídia paga, Meta/Google Ads | ads | `wizz-ads` | paid-ads, ad-creative, analytics-tracking |
-| Memória, contexto, "o que decidimos" | memória | `wizz-memoria` | cerebro |
+O roteamento tem duas fontes que você lê juntas, e NENHUMA é uma tabela fixa neste arquivo:
+
+1. **Dispatch por área = o `[[agent.menu]]`** resolvido no Passo 1 (vindo do `customize.toml` + overrides). Cada item do menu despacha um agente wizz. É ele que escolhe QUEM chamar (dev, qa, design, copy, seo, growth, ads, memória...).
+2. **Enriquecimento = o `skills-registry.yaml`**. Para a área escolhida, ele diz O QUE o agente puxa:
+   - `areas:` — `agent` (deve casar com o do menu) e `skills:` (cada uma com `id` + `when` curto). Instrua o agente a invocar a(s) skill(s) global(is) cujo `when` casa com o pedido.
+   - `utility:` — skills cross-cutting (graphify, find-skills, enhance-prompt, wizz-router). Ofereça quando couber.
+   - `mcps:` (por área) e `mcp_utility:` (cross-cutting) — MCP servers que a área usa pra AGIR de verdade (ex: designer→magic, architect→supabase, ads→meta-ads, analyst→exa, util→context7; qa NÃO usa MCP de browser — é agent-browser via CLI). Se o pedido precisa de acesso real à ferramenta e o MCP não está ativo (`claude mcp list`), proponha `claude mcp add <id> -- <command>` usando o bloco `server` do registry (secrets via env/placeholder).
+   - `squads:` — painéis consultivos (rodam via `wizz-party-mode`). Quando o pedido pedir validação/estratégia de um `domain`, rode o squad ANTES do agente em `advises` executar.
+
+Em resumo: **menu escolhe o agente, registry escolhe a(s) skill(s) e os squads.** Os papéis de dev/produto reusam os agentes WIZZ; os de agência são os `wizz-*`. Não memorize nomes de agente aqui — eles vêm do menu e do campo `agent:` do registry.
+
+### Sinal de complexidade (compartilhado com router e quick-dev)
+
+Avalie 4 fatores:
+
+1. **Áreas** — 1 só, ou várias?
+2. **Passos** — ajuste pontual, ou multi-passo?
+3. **Planejamento** — dá pra ir direto, ou precisa planejar antes?
+4. **Artefato + memória** — gera entregável que merece registro no cerebro?
+
+Regra de handoff:
+
+- **0–1 fatores "altos" → rebaixe:** mande direto pro `wizz-quick-dev` (bug/ajuste/feature pontual) ou pra skill única da área. Não orquestre.
+- **2+ fatores "altos" → orquestre você (maestro):** monte a ordem lógica entre áreas.
+- O **wizz-router** (porta global/flat) usa o mesmo sinal: quando descobre 2+ fatores altos num projeto com Wizz Method instalado, ele **escala pra você**. Você orquestra dentro do projeto; ele é a porta de descoberta fora.
 
 **Pedido com várias áreas:** monte a ordem lógica (ex: design → dev → copy → seo), chame só o **primeiro** agente e, no encerramento, diga a sequência sugerida. Não dispare todos de uma vez (modo confirmado).
 
-**Não tem agente/skill para o pedido:** diga isso e ofereça `find-skills` para buscar no marketplace.
+**Não tem agente/skill/MCP para o pedido:** diga isso e ofereça `find-skills`. Ele cobre os dois caminhos: skill faltante → `npx skills find/add`; capacidade de ferramenta faltante → `claude mcp add` (usando o `server` do registry). Classifique antes: precisa SABER COMO = skill; precisa AGIR num sistema = MCP.
 
 ## Encerramento
+
 Sempre termine no formato de `_shared/encerramento.md` (✅ / ➡️ / 🎯), dizendo qual agente você chamou e qual vem depois.

package/src/modules/wizz/agents/wizz-memoria/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-memoria
-description: Cérebro do projeto no Wizz Method. Use para recuperar o que já foi decidido, salvar decisões/aprendizados e ver o estado do projeto. Roteia para a skill global cerebro (/ver, /salvar, /decisao, /dump).
+description: Wizz Method Project Brain. Use when you need to retrieve what has already been decided, save decisions/learnings, and view the project state. Routes to the global skill cerebro (/view, /save, /decision, /dump).
 ---
 
 # Memória — Cérebro do Projeto

package/src/modules/wizz/agents/wizz-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-qa
-description: QA do Wizz Method. Use depois que o código está pronto, para verificar de fora: rodar testes, gerar testes E2E, revisão adversarial caçando bugs e conferir se atende o que foi pedido. Roteia para e2e-runner, adversarial-reviewer, wizz-qa-generate-e2e-tests e code-reviewer.
+description: Wizz Method QA. Use when the code is ready, to verify it from the outside (run tests, generate E2E tests, adversarial review hunting bugs, and check if it meets what was requested). Routes to e2e-runner, adversarial-reviewer, wizz-qa-generate-e2e-tests, and code-reviewer.
 ---
 
 # QA — Garantia de Qualidade

package/src/modules/wizz/agents/wizz-seo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-seo
-description: Especialista de SEO do Wizz Method. Use para auditoria de SEO, otimização para busca e para IA (AI search), schema markup e SEO programático. Roteia para seo-audit, ai-seo, schema-markup, programmatic-seo e site-architecture.
+description: Wizz Method SEO Specialist. Use when you need SEO auditing, search optimization, AI search optimization, schema markup, and programmatic SEO. Routes to seo-audit, ai-seo, schema-markup, programmatic-seo, and site-architecture.
 ---
 
 # SEO — Especialista de SEO

package/src/modules/wizz/overrides/{bmad-agent-analyst.toml → wizz-agent-analyst.toml}

@@ -1,4 +1,4 @@
-# Override Wizz (escopo time) para o agente BMAD Mary (Business Analyst).
+# Override Wizz (escopo time) para o agente WIZZ Mary (Business Analyst).
 # Mescla por cima da base: principles e activation_steps fazem APPEND.
 # Instalado em {project-root}/_wizz/custom/wizz-agent-analyst.toml
 # Seu .user.toml pessoal ainda vence por cima deste.

package/src/modules/wizz/overrides/{bmad-agent-architect.toml → wizz-agent-architect.toml}

@@ -1,4 +1,4 @@
-# Override Wizz (escopo time) para o agente BMAD Winston (System Architect).
+# Override Wizz (escopo time) para o agente WIZZ Winston (System Architect).
 # Mescla por cima da base: principles e activation_steps fazem APPEND.
 # Instalado em {project-root}/_wizz/custom/wizz-agent-architect.toml
 

package/src/modules/wizz/overrides/{bmad-agent-dev.toml → wizz-agent-dev.toml}

@@ -1,4 +1,4 @@
-# Override Wizz (escopo time) para o agente BMAD Amelia (Senior Software Engineer).
+# Override Wizz (escopo time) para o agente WIZZ Amelia (Senior Software Engineer).
 # Mescla por cima da base: principles e activation_steps fazem APPEND.
 # Instalado em {project-root}/_wizz/custom/wizz-agent-dev.toml
 

package/src/modules/wizz/overrides/{bmad-agent-pm.toml → wizz-agent-pm.toml}

@@ -1,4 +1,4 @@
-# Override Wizz (escopo time) para o agente BMAD John (Product Manager).
+# Override Wizz (escopo time) para o agente WIZZ John (Product Manager).
 # Mescla por cima da base: principles e activation_steps fazem APPEND.
 # Instalado em {project-root}/_wizz/custom/wizz-agent-pm.toml
 

package/src/modules/wizz/overrides/{bmad-agent-tech-writer.toml → wizz-agent-tech-writer.toml}

@@ -1,4 +1,4 @@
-# Override Wizz (escopo time) para o agente BMAD Paige (Technical Writer).
+# Override Wizz (escopo time) para o agente WIZZ Paige (Technical Writer).
 # Mescla por cima da base: principles e activation_steps fazem APPEND.
 # Instalado em {project-root}/_wizz/custom/wizz-agent-tech-writer.toml
 

package/src/modules/wizz/overrides/{bmad-agent-ux-designer.toml → wizz-agent-ux-designer.toml}

@@ -1,4 +1,4 @@
-# Override Wizz (escopo time) para o agente BMAD Sally (UX Designer).
+# Override Wizz (escopo time) para o agente WIZZ Sally (UX Designer).
 # Mescla por cima da base: principles e activation_steps fazem APPEND.
 # Instalado em {project-root}/_wizz/custom/wizz-agent-ux-designer.toml
 # Obs: Sally cuida do UX dentro do fluxo de PRD (wireframe, fluxo). Para

package/src/modules/wizz/scripts/wizz-init.mjs

@@ -1,10 +1,10 @@
-// wizz-init — aplica a personalização Wizz num projeto que já tem o BMAD instalado.
+// wizz-init — aplica a personalização Wizz num projeto que já tem o WIZZ instalado.
 //
 // O que faz (idempotente, seguro de rodar de novo):
 //   1. Pergunta o idioma e o seta em _wizz/bmm/config.yaml (communication_language
 //      e document_output_language).
 //   2. Copia os overrides Wizz (overrides/*.toml) para _wizz/custom/, dando aos
-//      agentes BMAD o tom fácil + protocolo de encerramento.
+//      agentes WIZZ o tom fácil + protocolo de encerramento.
 //
 // Uso:
 //   node src/modules/wizz/scripts/wizz-init.mjs [caminho-do-projeto] [--lang "<idioma>"]
@@ -116,17 +116,17 @@ function projectArg(argv) {
 
 async function main() {
   const projectRoot = path.resolve(projectArg(process.argv.slice(2)) || process.cwd());
-  const bmadDir = path.join(projectRoot, '_wizz');
+  const wizzDir = path.join(projectRoot, '_wizz');
 
-  if (!(await exists(bmadDir))) {
-    throw new Error(`Não achei _wizz/ em ${projectRoot}. Rode o instalador do BMAD primeiro.`);
+  if (!(await exists(wizzDir))) {
+    throw new Error(`Não achei _wizz/ em ${projectRoot}. Rode o instalador do WIZZ primeiro.`);
   }
 
   const done = [];
 
   // 1) Idioma escolhido no config do bmm.
   const { lang, source } = await pickLanguage(process.argv.slice(2));
-  const bmmConfig = path.join(bmadDir, 'bmm', 'config.yaml');
+  const bmmConfig = path.join(wizzDir, 'bmm', 'config.yaml');
   if (await exists(bmmConfig)) {
     let content = await readFile(bmmConfig, 'utf8');
     content = upsertYamlKey(content, 'communication_language', lang);
@@ -138,7 +138,7 @@ async function main() {
   }
 
   // 2) Copia overrides Wizz para _wizz/custom/.
-  const customDir = path.join(bmadDir, 'custom');
+  const customDir = path.join(wizzDir, 'custom');
   await mkdir(customDir, { recursive: true });
   if (await exists(overridesDir)) {
     const entries = await readdir(overridesDir);

package/src/scripts/resolve_config.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Resolve BMad's central config using four-layer TOML merge.
+Resolve Wizz's central config using four-layer TOML merge.
 
 Reads from four layers (highest priority last):
   1. {project-root}/_wizz/config.toml              (installer-owned team)
@@ -136,7 +136,7 @@ def extract_key(data, dotted_key: str):
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Resolve BMad central config using four-layer TOML merge.",
+        description="Resolve Wizz central config using four-layer TOML merge.",
     )
     parser.add_argument(
         "--project-root", "-p", required=True,
@@ -149,12 +149,12 @@ def main():
     args = parser.parse_args()
 
     project_root = Path(args.project_root).resolve()
-    bmad_dir = project_root / "_wizz"
+    wizz_dir = project_root / "_wizz"
 
-    base_team = load_toml(bmad_dir / "config.toml", required=True)
-    base_user = load_toml(bmad_dir / "config.user.toml")
-    custom_team = load_toml(bmad_dir / "custom" / "config.toml")
-    custom_user = load_toml(bmad_dir / "custom" / "config.user.toml")
+    base_team = load_toml(wizz_dir / "config.toml", required=True)
+    base_user = load_toml(wizz_dir / "config.user.toml")
+    custom_team = load_toml(wizz_dir / "custom" / "config.toml")
+    custom_user = load_toml(wizz_dir / "custom" / "config.user.toml")
 
     merged = deep_merge(base_team, base_user)
     merged = deep_merge(merged, custom_team)

package/src/scripts/resolve_customization.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Resolve customization for a BMad skill using three-layer TOML merge.
+Resolve customization for a Wizz skill using three-layer TOML merge.
 
 Reads customization from three layers (highest priority first):
   1. {project-root}/_wizz/custom/{name}.user.toml  (personal, gitignored)
@@ -187,7 +187,7 @@ def write_json_stdout(output):
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Resolve customization for a BMad skill using three-layer TOML merge.",
+        description="Resolve customization for a Wizz skill using three-layer TOML merge.",
         add_help=True,
     )
     parser.add_argument(

package/src/scripts/tests/test_memlog.py

@@ -246,7 +246,7 @@ def test_set_preserves_body(ws):
 
 def test_updated_stays_last(ws):
     init(ws)
-    memlog.main(["set", "--workspace", ws, "--key", "owner", "--value", "BMad"])
+    memlog.main(["set", "--workspace", ws, "--key", "owner", "--value", "Wizz"])
     meta = memlog.split(read(ws))[0]
     assert list(meta)[-1] == "updated"