wizz-method 2.0.0 → 2.1.0

package/skills-registry.yaml

@@ -9,6 +9,12 @@
 #
 # Skills vivem em src/skills-lib/<id>/. Squads em src/squads/<id>/ (via wizz-party-mode).
 #
+# CAMPOS SÓ-LLM (audit item 24): `door`, `rel` e `not_when` NÃO são lidos por
+# nenhum código — só pelo roteador LLM em runtime. O validador de schema
+# (tools/validate-registry-schema.js) checa a FORMA deles e rejeita qualquer
+# OUTRA chave não documentada aqui (whitelist fechada por tipo de entrada):
+# mudar/remover um desses campos quebra roteamento sem quebrar build.
+#
 # MCPs (Model Context Protocol servers) também são declarados aqui, por área, no
 # campo `mcps:` (e `mcp_utility:` para os cross-cutting). Cada entrada tem:
 #   id      — nome do server no config da IDE (chave em mcpServers)
@@ -187,6 +193,19 @@ areas:
         check: "test -f node_modules/@fal-ai/client/package.json"
         # Pin de supply chain (2026-08-25): versão fixa (client oficial fal.ai); atualizar conscientemente.
         install: "npm install @fal-ai/client@1.10.1"
+      - id: apple-design
+        when: "Revisar/auditar UI NATIVA (iOS/macOS: SwiftUI, Flutter, React Native, Tauri, Electron) contra o Apple HIG e o Liquid Glass — compliance com o HIG, acessibilidade, dark mode, navegação. Cobre o gap que o wizz-taste-skill declara fora de escopo ('native mobile: use Apple HIG directly')."
+        not_when: "UI web: aí é wizz-ui-ux-pro-max / wizz-impeccable."
+        rel:
+          pairs_with: [wizz-taste-skill]
+        platform: [darwin, linux]
+        # Upstream sem licença declarada e reproduz texto do Apple HIG (122
+        # páginas): o Wizz só instala a partir do upstream, no opt-in do
+        # usuário, e nunca vendoriza/copia o conteúdo pra este repo (auditoria
+        # 2026-09-11, Parte 3.14, item 25). Escopo LOCAL. Pin de supply chain
+        # (2026-09-12): HEAD do upstream em 2026-09-09 (sem tags de release).
+        check: "grep -qx da2da6dd03aacf06da3fecf205347601d38bb141 ./.claude/skills/apple-design/.wizz-pin 2>/dev/null"
+        install: 'd="$(mktemp -d)" && git clone https://github.com/dickwu/apple-design-skill.git "$d" && git -C "$d" checkout da2da6dd03aacf06da3fecf205347601d38bb141 && npx -y skills add "$d" -y --copy && printf "%s\n" da2da6dd03aacf06da3fecf205347601d38bb141 > ./.claude/skills/apple-design/.wizz-pin && rm -rf "$d"'
     references:
       - "references/premium-agency-rules.md (regras $150k-tier, importadas por impeccable/huashu no modo high-end)"
 
@@ -278,22 +297,22 @@ areas:
       - id: wizz-offer-forge
         when: "Forjar oferta irresistível de resposta direta/infoproduto (mecanismo único, empilhamento de valor, garantia reversa, ponte de tráfego)."
       # Módulo lowticket (src/modules/lowticket) — ver nota em ads.skills.
-      - id: lowticket-metodologia
+      - id: wizz-lowticket-metodologia
         module: lowticket
         when: "Roteador da base low ticket BR/PT: gatilho → um shard. Régua de preço, garantia, copy e rastreamento que tem precedência sobre a skill genérica."
         not_when:
           - "SaaS, B2B, site de cliente, high ticket ou mentoria: os números não transferem."
-      - id: lowticket-funil
+      - id: wizz-lowticket-funil
         module: lowticket
         when: "Escada pós-checkout de low ticket: upsell 1, upsell 2, downsell, oferta final, régua de preço por degrau e copy das páginas."
         not_when:
           - "Antes de existir um front-end que converte: estender funil sobre front que não vende multiplica zero."
-      - id: lowticket-minerador
+      - id: wizz-lowticket-minerador
         module: lowticket
         when: "Garimpo e veredito de oferta de concorrente: vocabulário de busca, veredito em 4 níveis, comparação lado a lado, diagnóstico de por que não escalou."
         not_when:
           - "A oferta já está definida: aí é wizz-offer-forge."
-      - id: lowticket-pagina
+      - id: wizz-lowticket-pagina
         module: lowticket
         when: "Engenharia de performance da página de venda low ticket: connect rate, ordem do pixel, LCP/TTFB/CLS, peso acima da dobra, relatório antes e depois."
         not_when:
@@ -322,6 +341,19 @@ areas:
         when: "Decidir O QUE produzir de conteúdo (topic clusters, calendário, pilares)."
       - id: wizz-copy-editing
         when: "Revisar/editar o texto do roteiro ou da legenda antes de publicar."
+    clis:
+      - id: postiz
+        when: "PUBLICAR/agendar de verdade em redes sociais (30+ integrações) a partir do conteúdo que o wizz-social já gerou. Separa 'gerar' (Wizz) de 'publicar' (Postiz). Precisa autenticar antes (`postiz auth:login` ou env `POSTIZ_API_KEY`); para imagem/vídeo a própria CLI faz o upload."
+        not_when: "Escrever o roteiro ou a legenda: isso é skill da área (wizz-social-content, wizz-copy-editing)."
+        # Item 30 da auditoria (2026-09-11, Parte 3.7). Pin de supply chain
+        # (2026-09-12): versão publicada fixa no npm, atualizar conscientemente.
+        # CLI, não MCP: o schema de `mcps:` deste registry só aceita stdio
+        # ({command,args,env}) e o MCP hospedado da Postiz é HTTP+OAuth
+        # (https://mcp.postiz.com/mcp-oauth-dynamic) — não encaixa. Existe uma
+        # skill wrapper (`gitroomhq/postiz-agent`) que só dirige esta mesma CLI;
+        # opcional, não registrada aqui.
+        check: "command -v postiz >/dev/null 2>&1"
+        install: "npm install -g postiz@2.0.16"
 
   ads:
     agent: wizz-ads
@@ -344,12 +376,12 @@ areas:
       # Módulo lowticket (src/modules/lowticket) — instaladas COM O MÓDULO, não
       # por skills-lib. O campo `module` é o gate: resolveSkillIds as ignora ao
       # copiar de src/skills-lib, e o router continua enxergando as entradas.
-      - id: lowticket-metodologia
+      - id: wizz-lowticket-metodologia
         module: lowticket
         when: "Roteador da base low ticket BR/PT: gatilho → um shard (diagnóstico de funil, bid cap, criativo, oferta, página, Instagram, player de VSL, upsell, copy, rastreamento, mineração). Carrega guardrails junto."
         not_when:
           - "SaaS, B2B, site de cliente, high ticket ou mentoria: os números não transferem."
-      - id: lowticket-trafego
+      - id: wizz-lowticket-trafego
         module: lowticket
         when: "Diagnóstico e régua de campanha Meta de low ticket: estrutura 1-1-X, bid cap, régua de 3x, quando cortar, como escalar, ler print do gerenciador ou do funil."
         not_when:
@@ -398,13 +430,31 @@ areas:
         check: "sentry-cli --version"
         # Pin de supply chain (2026-08-25): versão fixa; atualizar conscientemente.
         install: "npm install -g @sentry/cli@3.6.2"
+      - id: archify
+        when: "DESENHAR um diagrama VALIDADO de arquitetura/workflow/sequência/dataflow/estado como HTML+SVG navegável (aceita Mermaid) — no passo 'Renderings & polish' do wizz-architecture, ou quando o usuário pedir um diagrama assim. Protocolo obrigatório validate → deliver → visual-check: nunca declarar sucesso sem ler o JSON do comando. Ele DESENHA o que já foi decidido; a decisão e o porquê continuam no wizz-architecture (memlog, AD-n)."
+        not_when:
+          - "Registrar a decisão de arquitetura em si: isso é o wizz-architecture."
+          - "Diagrama descartável de conversa: Mermaid inline já basta."
+        platform: [darwin, linux]
+        # Origem: auditoria 2026-09-11, Parte 3.10, item 25. Pin de supply chain
+        # (2026-09-12): tag de release v2.16.0, não main — upstream tem 155
+        # issues abertas, pin conservador. Atualizar conscientemente.
+        # Escopo LOCAL (diferente do hyperframes, que é global por escolha
+        # antiga): regra 1 da Doutrina de Instalação prefere local, sem motivo
+        # documentado pra abrir exceção aqui. A skill vive no subdiretório
+        # archify/ do repo (a raiz não tem SKILL.md), daí o `-s archify`.
+        # O bin faz um GET opcional de checagem de update ao rodar; desativar
+        # com o env ARCHIFY_UPDATE_CHECK_DISABLED=1 (sem campo `env` em clis).
+        check: "grep -qx c826e6c3a7abad19c0f3cd1ca57207d54b1ad8de ./.claude/skills/archify/.wizz-pin 2>/dev/null"
+        install: 'd="$(mktemp -d)" && git clone https://github.com/tt-a1i/archify.git "$d" && git -C "$d" checkout c826e6c3a7abad19c0f3cd1ca57207d54b1ad8de && npx -y skills add "$d" -s archify -y --copy && printf "%s\n" c826e6c3a7abad19c0f3cd1ca57207d54b1ad8de > ./.claude/skills/archify/.wizz-pin && rm -rf "$d"'
+        verify: "command -v node >/dev/null 2>&1"
 
   qa:
     agent: wizz-qa
     summary: "QA: verificar o código de fora (testes, E2E, review adversarial)."
     skills:
       - id: wizz-adversarial-reviewer
-        when: "Passe único adversarial, ad hoc, fora de workflow — 'tear this apart' num trecho colado, sem contexto de projeto. Não confundir com wizz-review-adversarial-general (camada interna 'Blind Hunter' chamada só por wizz-code-review) nem com wizz-code-review (orquestrador bmm: 3 camadas paralelas + triagem, para review real de diff/PR)."
+        when: "Passe único adversarial, ad hoc, fora de workflow — 'tear this apart' num trecho colado, sem contexto de projeto. Não confundir com wizz-review-adversarial-general (persona do 'Blind Hunter'; o prompt operacional vive em review-prompts/blind-hunter.md e nenhum workflow invoca a skill) nem com wizz-code-review (orquestrador bmm: 3 camadas paralelas + triagem, para review real de diff/PR)."
       - id: security-audit-pentest
         when: "Auditoria/pentest de segurança do app inteiro — 'auditar segurança', 'pentest', 'encontrar vulnerabilidades', varredura antes de release. Só para teste de segurança AUTORIZADO (seus sistemas ou de clientes com permissão): ferramenta dual-use, nunca usar contra alvo sem autorização."
       - id: wizz-launch-readiness
@@ -444,6 +494,77 @@ areas:
       - id: wizz-implementation-planner
         when: "Plano técnico de implementação de site/app premium pós-direção aprovada. Pesquisa web/prior-art durante o planejamento usa a tool nativa WebSearch (sem custo/MCP metered — o MCP exa foi removido em 2026-08-25)."
 
+  # ── Áreas dev/produto (item 18 da auditoria de 2026-09-11, finding RT-H2):
+  # "dev" era citado dezenas de vezes no método (router, maestro,
+  # token-economy, encerramento) sem existir como chave de `areas:`. As 4
+  # chaves abaixo apontam para os agents do módulo bmm (src/bmm-skills,
+  # team software-development: Amelia/John/Paige/Sally) e listam as skills
+  # bmm correspondentes via `module: bmm` — mesmo mecanismo do módulo
+  # lowticket: NÃO são copiadas para `_wizz/skills-lib/` (são instaladas
+  # junto do módulo bmm), ficam no registry só para o router/maestro
+  # enxergarem e rotearem.
+  dev:
+    agent: wizz-agent-dev
+    summary: "Desenvolvimento de software: implementar story/bug/feature, TDD, review de código, sprint."
+    skills:
+      - id: wizz-quick-dev
+        module: bmm
+        when: "DEV PONTUAL: ajuste, bug fix, feature única sem cerimônia de story. Fluxo unificado: clarificar → planejar → implementar → review → apresentar. É o destino padrão quando o router/maestro diz 'dev pontual'."
+      - id: wizz-dev-story
+        module: bmm
+        when: "Implementar UMA story específica com spec preenchida ('dev this story', 'implementa a próxima story do sprint')."
+      - id: wizz-create-story
+        module: bmm
+        when: "Preparar story com todo o contexto de implementação ('cria a story', 'prepara a story'). Antes do dev, no gate de planejamento."
+      - id: wizz-code-review
+        module: bmm
+        when: "Review de código real de diff/PR: 3 camadas paralelas (Blind Hunter, Edge Case, Verification Gap) + triagem. Diferente de wizz-adversarial-reviewer (passe único ad hoc, área qa)."
+      - id: wizz-investigate
+        module: bmm
+        when: "Investigar bug/incidente, rastrear causa, construir modelo mental de uma área de código antes de mexer."
+      - id: wizz-sprint-planning
+        module: bmm
+        when: "Gerar/atualizar o sprint plan que sequencia stories para implementação."
+      - id: wizz-correct-course
+        module: bmm
+        when: "Mudança significativa durante o sprint: propor ajuste de curso ('correct course')."
+      - id: wizz-retrospective
+        module: bmm
+        when: "Review do trabalho concluído no epic (party mode)."
+
+  pm:
+    agent: wizz-agent-pm
+    summary: "Produto: PRD, brief, requisitos, escopo, priorização."
+    skills:
+      - id: wizz-prd
+        module: bmm
+        when: "Criar, atualizar ou validar PRD ('cria o PRD', 'documento de requisitos', 'define o escopo'). Consolida os antigos create/edit/validate-prd (removidos em v7)."
+      - id: wizz-product-brief
+        module: bmm
+        when: "Criar, atualizar ou validar o brief do produto ('cria o brief'). Antes do PRD, no kickoff de produto."
+      - id: wizz-prfaq
+        module: bmm
+        when: "Desafio Working Backwards PRFAQ para forjar conceito de produto ('cria a PRFAQ', 'work backwards')."
+      - id: wizz-set-feature
+        module: bmm
+        when: "Definir feature específica dentro do produto (análise de feature única)."
+
+  tech-writer:
+    agent: wizz-agent-tech-writer
+    summary: "Documentação: docs técnicas, diagramas, estrutura de conhecimento."
+    skills:
+      - id: wizz-document-project
+        module: bmm
+        when: "Documentar o projeto: gerar/atualizar docs de arquitetura e estrutura para contexto de agentes e humanos."
+
+  ux-designer:
+    agent: wizz-agent-ux-designer
+    summary: "UX: fluxos, user stories, especificação de experiência."
+    skills:
+      - id: wizz-ux
+        module: bmm
+        when: "Especificar experiência do usuário: fluxos, wireframes de conteúdo, user stories de UX (diferente da área designer, que constrói UI visual)."
+
   memoria:
     agent: wizz-memoria
     summary: "Memória do projeto: o que foi decidido, salvar, ver estado."

package/src/bmm-skills/1-analysis/research/wizz-domain-research/SKILL.md

@@ -14,7 +14,6 @@ description: 'Conduct domain and industry research. Use when the user says wants
 - Bare paths (e.g. `domain-steps/step-01-init.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## PREREQUISITE
 
@@ -24,13 +23,13 @@ description: 'Conduct domain and industry research. Use when the user says wants
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: read `{project-root}/_wizz/_resolved/wizz-domain-research.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-domain-research` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-domain-research.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-domain-research.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/1-analysis/research/wizz-domain-research/domain-steps/step-06-research-synthesis.md

@@ -443,7 +443,7 @@ Complete authoritative research document on {{research_topic}} that:
 
 ## On Complete
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+Run: read `workflow.on_complete` from the `{project-root}/_wizz/_resolved/wizz-domain-research.json` snapshot loaded in step 1
 
 If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
 

package/src/bmm-skills/1-analysis/research/wizz-market-research/SKILL.md

@@ -14,7 +14,6 @@ description: 'Conduct market research on competition and customers. Use when the
 - Bare paths (e.g. `steps/step-01-init.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## PREREQUISITE
 
@@ -24,13 +23,13 @@ description: 'Conduct market research on competition and customers. Use when the
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: read `{project-root}/_wizz/_resolved/wizz-market-research.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-market-research` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-market-research.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-market-research.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/1-analysis/research/wizz-market-research/steps/step-06-research-completion.md

@@ -477,7 +477,7 @@ Comprehensive market research workflow complete. User may:
 
 ## On Complete
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+Run: read `workflow.on_complete` from the `{project-root}/_wizz/_resolved/wizz-market-research.json` snapshot loaded in step 1
 
 If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
 

package/src/bmm-skills/1-analysis/research/wizz-technical-research/SKILL.md

@@ -14,7 +14,6 @@ description: 'Conduct technical research on technologies and architecture. Use w
 - Bare paths (e.g. `technical-steps/step-01-init.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## PREREQUISITE
 
@@ -24,13 +23,13 @@ description: 'Conduct technical research on technologies and architecture. Use w
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: read `{project-root}/_wizz/_resolved/wizz-technical-research.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-technical-research` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-technical-research.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-technical-research.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/1-analysis/research/wizz-technical-research/technical-steps/step-06-research-synthesis.md

@@ -486,7 +486,7 @@ Complete authoritative technical research document on {{research_topic}} that:
 
 ## On Complete
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+Run: read `workflow.on_complete` from the `{project-root}/_wizz/_resolved/wizz-technical-research.json` snapshot loaded in step 1
 
 If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
 

package/src/bmm-skills/1-analysis/wizz-agent-analyst/SKILL.md

@@ -14,19 +14,18 @@ You are Mary, the Business Analyst. You bring deep expertise in market research,
 - Bare paths (e.g. `references/guide.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## On Activation
 
 ### Step 1: Resolve the Agent Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: read `{project-root}/_wizz/_resolved/wizz-agent-analyst.json` (subtree `agent`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-agent-analyst` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-agent-analyst.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-agent-analyst.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/1-analysis/wizz-agent-tech-writer/SKILL.md

@@ -14,19 +14,18 @@ You are Paige, the Technical Writer. You transform complex concepts into accessi
 - Bare paths (e.g. `references/guide.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## On Activation
 
 ### Step 1: Resolve the Agent Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: read `{project-root}/_wizz/_resolved/wizz-agent-tech-writer.json` (subtree `agent`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-agent-tech-writer` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-agent-tech-writer.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-agent-tech-writer.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/1-analysis/wizz-document-project/SKILL.md

@@ -14,19 +14,18 @@ description: 'Document brownfield projects for AI context. Use when the user say
 - Bare paths (e.g. `instructions.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## On Activation
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: read `{project-root}/_wizz/_resolved/wizz-document-project.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-document-project` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-document-project.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-document-project.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/1-analysis/wizz-document-project/workflows/deep-dive-instructions.md

@@ -291,7 +291,7 @@ These comprehensive docs are now ready for:
 
 Thank you for using the document-project workflow!
 </action>
-<action>Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+<action>Run: read `workflow.on_complete` from the `{project-root}/_wizz/_resolved/wizz-document-project.json` snapshot loaded in step 1 — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
 <action>Exit workflow</action>
 </action>
 </step>

package/src/bmm-skills/1-analysis/wizz-document-project/workflows/full-scan-instructions.md

@@ -1103,6 +1103,6 @@ When ready to plan new features, run the PRD workflow and provide this index as
   </action>
 
 <action>Display: "State file saved: {{project_knowledge}}/project-scan-report.json"</action>
-<action>Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+<action>Run: read `workflow.on_complete` from the `{project-root}/_wizz/_resolved/wizz-document-project.json` snapshot loaded in step 1 — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
 
 </workflow>

package/src/bmm-skills/1-analysis/wizz-prfaq/SKILL.md

@@ -24,19 +24,18 @@ The PRFAQ forces customer-first clarity: write the press release announcing the
 - Bare paths (e.g. `references/press-release.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## On Activation
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: read `{project-root}/_wizz/_resolved/wizz-prfaq.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-prfaq` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-prfaq.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-prfaq.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/1-analysis/wizz-prfaq/references/verdict.md

@@ -78,6 +78,6 @@ purpose: "Token-efficient context for downstream PRD creation"
 
 This is the terminal stage. If the user wants to revise, loop back to the relevant stage. Otherwise, the workflow is done.
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+Run: read `workflow.on_complete` from the `{project-root}/_wizz/_resolved/wizz-prfaq.json` snapshot loaded in step 1
 
 If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.

package/src/bmm-skills/1-analysis/wizz-product-brief/SKILL.md

@@ -15,7 +15,7 @@ At the opening greeting, let the user know they can invoke `wizz-party-mode` for
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+1. Resolve customization: Read `{project-root}/_wizz/_resolved/wizz-product-brief.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-product-brief` from the project root and read the snapshot again. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
 3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
 4. `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers in `## Discovery`, org tools preferred when their directive matches. If a named tool is unavailable at runtime, fall back to standard behavior and note the gap when relevant.

package/src/bmm-skills/2-plan-workflows/wizz-agent-pm/SKILL.md

@@ -14,19 +14,18 @@ You are John, the Product Manager. You drive PRD creation through user interview
 - Bare paths (e.g. `references/guide.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## On Activation
 
 ### Step 1: Resolve the Agent Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: read `{project-root}/_wizz/_resolved/wizz-agent-pm.json` (subtree `agent`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-agent-pm` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-agent-pm.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-agent-pm.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/2-plan-workflows/wizz-agent-ux-designer/SKILL.md

@@ -14,19 +14,18 @@ You are Sally, the UX Designer. You translate user needs into interaction design
 - Bare paths (e.g. `references/guide.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## On Activation
 
 ### Step 1: Resolve the Agent Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: read `{project-root}/_wizz/_resolved/wizz-agent-ux-designer.json` (subtree `agent`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-agent-ux-designer` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-agent-ux-designer.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-agent-ux-designer.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
 

package/src/bmm-skills/2-plan-workflows/wizz-create-prd/SKILL.md

@@ -9,7 +9,7 @@ This skill was consolidated into `wizz-prd`. It is retained as a thin compatibil
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_wizz/custom/wizz-create-prd.toml` and `wizz-create-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+1. Resolve customization: Read `{project-root}/_wizz/_resolved/wizz-create-prd.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-create-prd` from the project root and read the snapshot again.
 
 2. Load `{project-root}/_wizz/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
 

package/src/bmm-skills/2-plan-workflows/wizz-edit-prd/SKILL.md

@@ -9,7 +9,7 @@ This skill was consolidated into `wizz-prd`. It is retained as a thin compatibil
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_wizz/custom/wizz-edit-prd.toml` and `wizz-edit-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+1. Resolve customization: Read `{project-root}/_wizz/_resolved/wizz-edit-prd.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-edit-prd` from the project root and read the snapshot again.
 
 2. Load `{project-root}/_wizz/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
 

package/src/bmm-skills/2-plan-workflows/wizz-prd/SKILL.md

@@ -15,7 +15,7 @@ You are a master facilitator and coach helping the user create, edit, or validat
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+1. Resolve customization: Read `{project-root}/_wizz/_resolved/wizz-prd.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-prd` from the project root and read the snapshot again. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers, org tools preferred when their directive matches. Research itself fires during Discovery — see **Research subagents**.
 3. Load `{project-root}/_wizz/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
 4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. In the greeting, let the user know that at any point they can invoke `wizz-party-mode` for multi-agent perspectives or `wizz-advanced-elicitation` for deeper exploration on a specific section. Then scan for misroute on the first message: if the signal points elsewhere (game → Wizz GDS; express build → `wizz-quick-dev`; one-pager → `wizz-product-brief`; vet product idea → `wizz-prfaq`; agent skill or custom agent → `wizz-workflow-builder`), suggest they might want the other options before continuing.

package/src/bmm-skills/2-plan-workflows/wizz-ux/SKILL.md

@@ -30,7 +30,7 @@ UX may lead, follow, or stand alone. Inherit `sources:` by reference; the spines
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+1. Resolve customization: Read `{project-root}/_wizz/_resolved/wizz-ux.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-ux` from the project root and read the snapshot again. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools; consult them alongside generic web research on the same triggers, org tools preferred when their directive matches.
 3. Load `{project-root}/_wizz/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
 4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn. In the greeting, let the user know `wizz-party-mode` and `wizz-advanced-elicitation` are always available. Then scan for misroute on the first message: PRD → `wizz-prd`; architecture → `wizz-architecture`; game UX → Wizz GDS; agent/skill → `wizz-workflow-builder`; brief → `wizz-product-brief`.

package/src/bmm-skills/2-plan-workflows/wizz-validate-prd/SKILL.md

@@ -9,7 +9,7 @@ This skill was consolidated into `wizz-prd`. It is retained as a thin compatibil
 
 ## On Activation
 
-1. Resolve customization: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_wizz/custom/wizz-validate-prd.toml` and `wizz-validate-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+1. Resolve customization: Read `{project-root}/_wizz/_resolved/wizz-validate-prd.json` (subtree `workflow`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-validate-prd` from the project root and read the snapshot again.
 
 2. Load `{project-root}/_wizz/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
 

package/src/bmm-skills/3-solutioning/wizz-agent-architect/SKILL.md

@@ -14,19 +14,18 @@ You are Winston, the System Architect. You turn product requirements and UX into
 - Bare paths (e.g. `references/guide.md`) resolve from the skill root.
 - `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
 - `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
 
 ## On Activation
 
 ### Step 1: Resolve the Agent Block
 
-Run: `python3 {project-root}/_wizz/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: read `{project-root}/_wizz/_resolved/wizz-agent-architect.json` (subtree `agent`). If the file is missing, empty or not valid JSON, run `npx wizz-method resolve --skill wizz-agent-architect` from the project root and read the snapshot again
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 
 1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_wizz/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_wizz/custom/{skill-name}.user.toml` — personal overrides
+2. `{project-root}/_wizz/custom/wizz-agent-architect.toml` — team overrides
+3. `{project-root}/_wizz/custom/wizz-agent-architect.user.toml` — personal overrides
 
 Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.