wizz-method 1.16.1 → 1.18.0

package/src/bmm-skills/3-solutioning/wizz-generate-project-context/steps/step-03-complete.md

@@ -77,6 +77,10 @@ _This file contains critical rules and patterns that AI agents must follow when
 
 ---
 
+## Estado do Projeto
+
+{{stage_and_current_status}}
+
 ## Technology Stack & Versions
 
 {{concise_technology_list}}
@@ -196,6 +200,7 @@ sections_completed:
 status: 'complete'
 rule_count: { { total_rules } }
 optimized_for_llm: true
+stage: '{{project_stage}}' # prototype|mvp|production|maintenance
 ---
 ```
 

package/src/bmm-skills/4-implementation/wizz-agent-dev/customize.toml

@@ -37,7 +37,7 @@ activation_steps_append = []
 
 persistent_facts = [
   "file:{project-root}/**/project-context.md",
-  "If active_feature is set in {project-root}/_wizz/bmm/config.yaml, save every planning and implementation artifact under a subfolder named after it (e.g. {planning_artifacts}/{active_feature}/, {implementation_artifacts}/{active_feature}/). If it is empty or unset, write to the artifact roots as usual.",
+  "FEATURE: o hook SessionStart já resolve a feature ativa a partir do branch git e injeta 'FEATURE ATIVA: <slug>'. Se ela existir, salve TODO artefato de planejamento e implementação na subpasta com esse nome ({planning_artifacts}/{active_feature}/, {implementation_artifacts}/{active_feature}/) e grave o slug em active_feature no {project-root}/_wizz/bmm/config.yaml na primeira escrita, avisando em UMA linha. Memória gravada nesta sessão leva o mesmo slug como tema. Sem feature resolvida, escreva nas raízes. NUNCA pergunte a feature ao usuário: invoque wizz-set-feature só se ele pedir para trocar, ou se houver duas features abertas e o pedido não decidir entre elas.",
   "When implementing against a library or framework, consult Context7 for current docs, APIs, and version-specific syntax before relying on training data or web search: call resolve-library-id with the library name, then query-docs with the returned /org/project id and a specific question. If Context7 is unavailable, tell the user once that they can enable it with `npx ctx7 setup`, then fall back to web research.",
 ]
 

package/src/bmm-skills/4-implementation/wizz-retrospective/customize.toml

@@ -30,7 +30,9 @@ activation_steps_append = []
 #   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
 #     (glob patterns are supported; the file's contents are loaded and treated as facts).
 
-persistent_facts = []
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
 
 # Scalar: executed at the end of Phase 5 (Close), after the retrospective
 # document is saved and sprint-status is updated. Override wins.

package/src/bmm-skills/4-implementation/wizz-sprint-planning/customize.toml

@@ -30,7 +30,9 @@ activation_steps_append = []
 #   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
 #     (glob patterns are supported; the file's contents are loaded and treated as facts).
 
-persistent_facts = []
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
 
 # Scalar: executed when the workflow reaches its final step,
 # after sprint-status.yaml is generated and validated. Override wins.

package/src/modules/lowticket/README.md

@@ -0,0 +1,55 @@
+# Wizz Low Ticket
+
+A portable knowledge base and four operating skills for **low ticket direct response** in Brazil and Portugal: offers between roughly R$19 and R$97, sold cold on Meta Ads, on a phone, mostly inside the Instagram in-app browser.
+
+Install it and a fresh machine has the methodology and the four agents working, with no extra setup.
+
+## What ships
+
+| Skill | Does | Use when | Do not use when |
+|---|---|---|---|
+| `lowticket-metodologia` | routes a request to the one knowledge shard that answers it, loads the guardrails alongside | any low ticket work: offer, creative, page, campaign, funnel | SaaS, B2B, client site, high ticket |
+| `lowticket-trafego` | campaign diagnosis and ruler: structure, bid cap, when to cut, how to scale | reading, cutting or scaling a Meta campaign | Google Ads, brand campaigns, writing ads |
+| `lowticket-funil` | the post-checkout ladder: upsell, downsell, final offer, price rules | after the front-end converts, to raise average order value | before a front-end that converts exists |
+| `lowticket-minerador` | mining and judging a competitor offer, with a cut-off rubric | hunting a new offer to model | the offer is already defined (use `wizz-offer-forge`) |
+| `lowticket-pagina` | page performance: connect rate, LCP, pixel order, acceptance targets | optimizing or building a low ticket sales page | institutional sites or apps |
+
+All five read the Cérebro on activation and **none of them keeps its own memory**, the same contract as `wizz-offer-forge`. What is decided lives in the Cérebro; what is known lives in the shards.
+
+## The loading contract
+
+The knowledge base is 20 shards. It is not loaded whole. Reading everything costs around 36k tokens; a typical answer needs under 5k.
+
+| Step | Read | When |
+|---|---|---|
+| 0 | `knowledge/INDEX.md` + `knowledge/guardrails.md` | always |
+| 1 | **one** shard named by the INDEX | the request matches a trigger |
+| 2 | the raw source on the operator's machine | rare: the shard did not answer |
+
+## Language
+
+The framework surface is English: this file, the module definition, the SKILL.md frontmatter, the registry entry. **The knowledge is Portuguese**: the shard bodies, their filenames, the INDEX, the guardrails, the table headers.
+
+That split is deliberate. The market this describes is BR/PT and the vocabulary is native (`bid cap`, `connect rate`, `order bump`, `Utmify`, `Pix`); translating it would make it less precise, not more portable. Decision recorded 2026-08-28.
+
+## Origin
+
+The knowledge here is a distillation: facts, benchmarks, checklists and critical analysis, written from scratch. **No third-party lesson text, transcript, PDF or prompt ships in this package.** Raw sources stay on the author's machine, outside npm and outside git.
+
+If you extend a shard, keep it that way: write the fact, never the quote. `knowledge/15-como-estender.md` has the full process.
+
+Three tactics present in the source material are recorded and **not adopted** in `knowledge/guardrails.md`: buying engagement, AI avatars passing as real people, and synthetic testimonials. They are loaded on every activation and stay blocked until the operation's owner decides otherwise.
+
+## Optional config
+
+The creative swipe file (155 real pieces, ~2 GB of video and image) does not travel. The written analysis of it, `CATALOGO.md`, does, and it is enough to work from.
+
+To let the agent open a specific piece, point at the folder during install, or pin it by hand:
+
+```toml
+# _wizz/custom/config.user.toml  (never overwritten by the installer)
+[modules.lowticket]
+swipe_file_path = "/absolute/path/to/the/swipe/file"
+```
+
+Resolution order and the exact wording to use when the folder is absent: `skills/lowticket-metodologia/references/swipe-file.md`.

package/src/modules/lowticket/module.yaml

@@ -0,0 +1,31 @@
+code: lowticket
+name: "Wizz Low Ticket"
+description: "Low ticket direct-response playbook for Meta Ads (BR/PT): funnel diagnosis, bid-cap campaigns, creatives, sales pages, upsell ladders and offer mining. Knowledge base in Portuguese, loaded one shard at a time."
+default_selected: false
+
+# --- Origin note (read this before editing the knowledge base) ---
+#
+# The knowledge under skills/lowticket-metodologia/knowledge/ is a distillation
+# written from scratch: facts, benchmarks, checklists and critical analysis.
+# No third-party lesson text, transcript, PDF or prompt ships in this package.
+# The raw sources stay on the author's machine, outside npm and outside git.
+# Keep it that way: when you extend a shard, write the fact, never the quote.
+#
+# The knowledge body, the shard filenames and the INDEX are in Portuguese on
+# purpose (the market it describes is BR/PT and the vocabulary is native).
+# The framework surface (this file, SKILL.md frontmatter, the registry entry,
+# the README) stays in English like the rest of Wizz Method.
+# Decision recorded 2026-08-28.
+
+# --- Module-specific config ---
+
+swipe_file_path:
+  prompt:
+    - "Absolute path to your creative swipe file (the folder holding the reference videos and images)?"
+    - "Optional. Leave it empty: the skills still work from the written analysis in CATALOGO.md."
+  scope: user
+  default: ""
+  result: "{value}"
+
+directories:
+  - "{output_folder}/lowticket"

package/src/modules/lowticket/skills/lowticket-funil/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: lowticket-funil
+description: Designs the post-checkout ladder for a low ticket offer - upsell 1, upsell 2, downsell and a final offer - deciding what each step sells, which pain it answers, what it costs and why it sits in that position, then writes the pages. Use when a front-end offer already converts and the goal is to raise average order value, or when an existing upsell sequence is not converting. Do NOT use before a front-end that converts exists, and do NOT use for traffic, campaigns or the front-end offer itself.
+---
+
+# Low Ticket Funnel Extension
+
+Turns a single product into a post-checkout ladder. The whole discipline reduces to one question, asked at every step:
+
+**After this person buys this, what is the next problem they inevitably hit?**
+
+Every offer in the ladder exists because it answers that question for the step before it. An offer that does not answer it is a random product bolted onto a checkout, and it converts like one.
+
+## Prerequisite
+
+**There has to be a front-end that converts.** Extending a funnel above a front that does not sell multiplies zero. If the front is not validated, say so and point to `wizz-offer-forge` (build the offer) or `lowticket-trafego` (find out why it is not selling).
+
+## Source of truth
+
+Read the Cérebro state first (via the `cerebro` skill). Then, if `lowticket-metodologia` is installed, read `knowledge/INDEX.md` + `knowledge/guardrails.md` and the shard `07-funil-upsell.md`, especially §7.4 (the conversion and ticket cascade). Where a generic skill contradicts that shard, the shard wins and you say so.
+
+This skill has **no memory of its own**. What gets decided goes to the Cérebro; the artifact goes to a file.
+
+## Flow, in five moves
+
+Do not deliver the whole thing at once. Each move ends with a question, and the answer shapes the next one.
+
+### 1. Four questions, one message
+
+Explain in two lines what you are about to do, then ask exactly these, together:
+
+1. What is the front-end product? Name and what it delivers.
+2. What does it cost today?
+3. What is the main pain it solves?
+4. Who is it for? Audience, age band or situation.
+
+No follow-up questions at this stage unless something is missing outright.
+
+### 2. Diagnosis and two paths
+
+Restate what you heard in one line: *"Seu front é [produto] para [público]. Ele resolve [dor]. O ticket é [valor]."*
+
+Then offer **two** expansion paths, each with: the complementary pain, the product that would answer it, and why that pain shows up *after* the front-end. Explain the reasoning in plain language and ask which one fits. Develop a third only if asked.
+
+Two paths, not five. A menu is not a recommendation.
+
+### 3. The map
+
+Build the full ladder using the template in `references/mapa-do-funil.md`. Every step carries: name, price, pain, why it sits in that position, and three outcome bullets.
+
+Then state the flow out loud:
+
+```
+Front → Checkout → U1 → aceitou: U2 · recusou: Downsell → Oferta Final → Obrigado
+```
+
+Ask: adjust a product first, or write the copy?
+
+### 4. The pages
+
+One page per step, in the fixed 10-block order from `references/copy-das-paginas.md`. Tone shifts by step: aspirational on the front, celebratory on the upsell, empathetic on the downsell, plainly useful on the final offer.
+
+### 5. Implementation
+
+Offer, in this order: ready HTML, help with one-click OTO, adaptation to the platform in use, or adjusting the offers.
+
+## The rules that decide the ladder
+
+### Product
+
+- **An upsell is not a discount on the front.** U1 solves a *complementary* pain: the front teaches how to do X, U1 helps apply X.
+- **U2 is the natural next step for whoever took U1**, a more advanced pain. It is never shown to someone who refused U1.
+- **A downsell is a different, simpler product**, not the same product cheaper. "Você recusou por R$97, mas leva por R$27" is a discount, not a downsell. Reach for a checklist, a template, a condensed version, a fast-implementation kit, a tool, a script.
+- **The final offer answers a broad, frequent pain of the niche**, so nearly every buyer can want it.
+
+### Price
+
+| Step | Rule |
+|---|---|
+| Upsell 1 | 40% to 60% of the front price |
+| Upsell 2 | around U1, up to ~20% above |
+| Downsell | 10% to 25% **of the product that was refused**, not of the front |
+| Final offer | low enough for an instant decision; in BR, roughly R$9 to R$15 as a practical floor |
+
+Never raise the front price to make the ladder look more sophisticated. If the price was not given, ask before building the map.
+
+### Architecture
+
+Three paid steps after checkout, maximum. Everyone reaches the final offer. **U2 and the downsell are never shown to the same person.** Post-checkout offers should be one-click OTO; if the platform in use does not support that, say so before promising the implementation.
+
+If asked for five or more paid steps, say the recommendation is to consolidate. A longer ladder is not a bigger ladder.
+
+### Numbers, only when asked
+
+Treat these as reference, never as a promise: U1 15-25%, U2 20-35% among U1 buyers, downsell 20-35%, final offer 18-28%, total ticket around 1.5x to 2.3x the front. The canonical version is §7.4 of shard `07`.
+
+## Hard limits on the copy
+
+- **Never invent product facts.** Missing price, audience, pain, promise or mechanism: stop and ask. Do not fill the gap with something plausible.
+- **Never invent social proof.** No student counts, revenue, conversion rates, testimonials or results unless the user supplied them. No proof means no proof block.
+- **Never invent scarcity.** A one-time offer inside a funnel is real scarcity and can be said. A fake countdown, an invented deadline, a fictional seat count or a made-up price increase is not, and does not ship.
+- **Bullets are outcomes, not contents.** "12 módulos, 8 aulas, PDF de 40 páginas" is an inventory. "Você monta a primeira campanha sem travar na tela em branco" is an outcome.
+
+## Voice
+
+Portuguese (BR), spoken register, short sentences, no em-dashes. Concrete scenes instead of abstract emotion: not "você se sente inseguro", but "você abre o computador às 9h e às 11h ainda está tentando descobrir por onde começar". Repeat the product's name instead of cycling through synonyms.
+
+The full anti-AI word list and the rhythm rules are in `references/copy-das-paginas.md`. For a deeper pass, hand the draft to the `humanizer` skill.
+
+## Out of scope
+
+Traffic, campaigns, hiring, accounting, general operations. Bring it back to product, offer, price, pain, post-checkout sequence and copy, or route: `lowticket-trafego` for campaigns, `wizz-offer-forge` for the front-end offer, `lowticket-pagina` for the sales page itself.

package/src/modules/lowticket/skills/lowticket-funil/references/copy-das-paginas.md

@@ -0,0 +1,75 @@
+# Copy das páginas do funil
+
+## Os 10 blocos, nesta ordem
+
+1. Indicador de etapa
+2. Eyebrow / contexto
+3. Headline
+4. Corpo
+5. Ancoragem de preço
+6. Card de preço
+7. Três bullets de resultado
+8. CTA
+9. Recusa
+10. Barra de confiança
+
+A ordem não se mexe. Ela é o que faz a pessoa entender onde está no fluxo antes de decidir.
+
+## Regras por bloco
+
+**Headline.** Curta. De preferência com **uma** palavra destacada visualmente. Promessa concreta. Headline não é parágrafo.
+
+**Corpo.** Três a cinco parágrafos curtos, escritos para serem lidos no celular em movimento. Nada de bloco gigante.
+
+**Ancoragem.** `De R$X por R$Y`, com o valor original riscado quando virar HTML. **Não inventar o preço original.** Sem ancoragem legítima, perguntar ou deixar explícito que ela precisa ser definida.
+
+**Bullets.** Resultado, nunca inventário.
+
+| Errado | Certo |
+|---|---|
+| 12 módulos | Você monta a primeira campanha sem travar na tela em branco |
+| 8 aulas | Você sabe exatamente o que fazer depois da compra |
+| PDF de 40 páginas | Você para de perder tempo procurando o próximo passo |
+
+Não prometer resultado que o produto não entrega.
+
+**CTA.** Um por página. Ação mais benefício: `SIM, QUERO [BENEFÍCIO]`, `QUERO ACESSAR AGORA`, `SIM, QUERO ADICIONAR ISSO`.
+
+**Recusa.** O link existe sempre, discreto e não escondido: "Não, obrigado. Quero seguir sem essa oferta." Nada de manipulação agressiva do tipo "não, prefiro continuar perdendo dinheiro".
+
+## Tom por etapa
+
+| Etapa | Tom |
+|---|---|
+| Front | aspiracional e direto |
+| Upsell | celebratório: reconhece a compra que acabou de acontecer e apresenta a próxima oportunidade |
+| Downsell | empático: a recusa não foi um erro |
+| Oferta final | universal e simples: dá para entender a utilidade em cinco segundos |
+
+## Humanização
+
+Cortar antes de entregar:
+
+`crucial` · `jornada` · `mindset` · `transformador` · `revolucionário` · `empoderamento` · `protagonismo` · `alavancar` · `ecossistema` · `potencializar` · `holístico` · `agregar valor` · `sinergia`
+
+E as aberturas de piloto automático: "Nos dias de hoje...", "No cenário atual...", "Em um mundo onde...", "A verdade é que...", "No fundo...", "A questão é...", "Não só..., mas também...", "Transforme sua vida agora", "A oportunidade de ouro", "O futuro é seu".
+
+No lugar: linguagem falada. "do jeito certo", "na prática", "pra valer", "na real". Gíria só quando combina com o público.
+
+**Cena no lugar de emoção abstrata.** Em vez de "você se sente inseguro", algo que a pessoa realmente vive: "você abre o computador às 9h e às 11h ainda está tentando descobrir por onde começar".
+
+**Repetição é permitida.** Não trocar `produto` por `material`, `programa`, `formação`, `solução` a cada frase só para variar. Se o produto se chama X, ele se chama X.
+
+**Ritmo.** Frases curtas, misturadas com algumas um pouco maiores. Poucas orações subordinadas. Ler mentalmente em voz alta: se soar como apresentação corporativa, reescrever.
+
+**Sem travessão longo.** Vírgula, ponto, dois pontos ou parênteses.
+
+Para um passe mais fundo, mandar o rascunho para a skill `humanizer`.
+
+## Objeções
+
+Antecipar as reais: "está caro", "não tenho tempo", "será que funciona pro meu caso". Responder de forma concreta, sem inventar prova, depoimento ou número.
+
+## HTML
+
+Só gerar quando pedido. Quando gerar: HTML/CSS simples, mobile primeiro, carregamento leve, CTA e preço em destaque, link de recusa discreto, os 10 blocos preservados. Nada de script estranho e nada de integração inventada. Se a integração pedida não for conhecida, pedir a documentação em vez de improvisar.

package/src/modules/lowticket/skills/lowticket-funil/references/mapa-do-funil.md

@@ -0,0 +1,71 @@
+# Mapa do funil · template de saída
+
+Entregue o mapa completo antes de escrever qualquer copy. Ele é o contrato: se um produto muda depois, a copy toda muda junto.
+
+```
+FRONT-END
+Nome:
+Preço:
+Dor:
+
+UPSELL 1
+Nome:
+Preço:
+Dor:
+Por que vem agora:
+3 resultados:
+
+UPSELL 2
+Nome:
+Preço:
+Dor:
+Por que só aparece para quem aceitou o U1:
+3 resultados:
+
+DOWNSELL
+Nome:
+Preço:
+Dor:
+Por que é um produto diferente do recusado:
+3 resultados:
+
+OFERTA FINAL
+Nome:
+Preço:
+Dor:
+Por que praticamente todo comprador pode querer:
+3 resultados:
+```
+
+## A escada de dor
+
+O que muda de um degrau para o outro não é o preço, é a dor:
+
+| Degrau | Tipo de dor |
+|---|---|
+| Front | a dor principal |
+| U1 | a dor complementar, que só aparece depois de resolver a principal |
+| U2 | a dor avançada de quem já está aplicando |
+| Downsell | a dor imediata e simples, resolvida rápido |
+| Oferta final | a dor universal do nicho |
+
+## O fluxo
+
+```
+Front → Checkout → U1
+                    ├─ aceitou  → U2
+                    └─ recusou  → Downsell
+                                   ↓
+                              Oferta Final → Obrigado
+```
+
+Máximo três etapas pagas depois do checkout. Todo comprador chega na oferta final. U2 e downsell nunca aparecem para a mesma pessoa.
+
+## Checagem antes de fechar o mapa
+
+- [ ] Cada degrau resolve o próximo problema real, não um problema inventado para justificar a venda?
+- [ ] O downsell é produto diferente, não desconto?
+- [ ] O preço do downsell foi calculado sobre o produto recusado, não sobre o front?
+- [ ] O preço do front continuou intacto?
+- [ ] Os três resultados de cada degrau são resultados, e não conteúdo?
+- [ ] A plataforma suporta OTO de um clique? Se não, isso foi dito antes de prometer?