wize-dev-kit 0.14.0 → 0.16.0

package/docs/harnesses/antigravity.pt-BR.md

@@ -1,20 +0,0 @@
-# Google Antigravity — Wize Development Kit
-
-🌐 **Idiomas:** [English](antigravity.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-O Antigravity usa o mesmo formato público de Skill da Anthropic que o Claude Code e o Codex.
-
-## Saída
-
-- `.agent/skills/wize-{code}/SKILL.md` — repare no **singular** `.agent`, não `.agents` (esse é o diretório do Codex).
-- Um `AGENTS.md` na raiz (compartilhado com Codex, Cursor e Windsurf).
-
-## Destaques
-
-- `.antigravitycli/` é o diretório de estado do próprio CLI do Antigravity e nunca é tocado pelo kit — só `.agent/skills/` e `AGENTS.md` são gravados.
-
-## Como ativar
-
-Escolha **Antigravity** como alvo de IDE em `npx wize-dev-kit install` (ou adicione depois e rode `npx wize-dev-kit sync`). Reinicie o Antigravity e rode `/wize-orchestrator` ou peça pra ele ler o `AGENTS.md`.

package/docs/harnesses/claude-code.md

@@ -1,23 +0,0 @@
-# Claude Code — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](claude-code.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-Claude Code was the kit's first target and uses the public Anthropic Skill format verbatim.
-
-## Output
-
-`.claude/skills/wize-{code}/SKILL.md` — one directory per asset (persona, workflow, or skill). YAML frontmatter (`name`, `description`) plus the Markdown body. Companion files a workflow references by relative path (`steps/`, `templates/`, `data/`, `customize.toml`, ...) are copied alongside the `SKILL.md` so those paths resolve.
-
-There is no separate "agent" file shape here — personas (Wizer, Shuri, Hawkeye...) and workflows/skills all render to the same `SKILL.md` structure.
-
-## Notable
-
-- **Discovery is description-based.** Claude Code surfaces installed skills by matching the task at hand against each `description`; you can also invoke one directly by name (`/wize-dev-story`) or ask to "activate Wizer."
-- **Subagent fan-out is ad hoc, not persona-bound.** `wize-code-review` uses Claude Code's own Task/Agent tool to spin up isolated, parallel workers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) for a single review pass. Any skill can do this — it isn't wired to a specific `.claude/agents/*.md` subagent definition, since the kit doesn't emit one.
-- Claude Code does **not** read the root `AGENTS.md` the installer generates (that file is for Codex, Cursor, Windsurf, and Antigravity).
-
-## Setup
-
-Pick **Claude Code** as an IDE target during `npx wize-dev-kit install` (default). Restart Claude Code, then say *"Activate Wizer and brief him on the project"* or run `/wize-orchestrator`.

package/docs/harnesses/claude-code.pt-BR.md

@@ -1,23 +0,0 @@
-# Claude Code — Wize Development Kit
-
-🌐 **Idiomas:** [English](claude-code.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-Claude Code foi o primeiro alvo do kit e usa o formato público de Skill da Anthropic ao pé da letra.
-
-## Saída
-
-`.claude/skills/wize-{code}/SKILL.md` — um diretório por asset (persona, workflow ou skill). Frontmatter YAML (`name`, `description`) mais o corpo em Markdown. Arquivos complementares que um workflow referencia por caminho relativo (`steps/`, `templates/`, `data/`, `customize.toml`, ...) são copiados junto do `SKILL.md` para que esses caminhos resolvam.
-
-Não existe um formato separado de "agente" aqui — personas (Wizer, Shuri, Hawkeye...) e workflows/skills viram todos a mesma estrutura de `SKILL.md`.
-
-## Destaques
-
-- **Descoberta por descrição.** O Claude Code encontra as skills instaladas casando a tarefa em mãos contra cada `description`; também dá pra invocar direto pelo nome (`/wize-dev-story`) ou pedir pra "ativar o Wizer".
-- **Fan-out de subagentes é ad hoc, não amarrado a persona.** O `wize-code-review` usa a própria ferramenta Task/Agent do Claude Code pra levantar workers isolados e paralelos (Blind Hunter, Edge Case Hunter, Acceptance Auditor) numa única passada de review. Qualquer skill pode fazer isso — não está amarrado a uma definição de subagente `.claude/agents/*.md`, já que o kit não gera nenhuma.
-- O Claude Code **não** lê o `AGENTS.md` na raiz que o instalador gera (esse arquivo é pro Codex, Cursor, Windsurf e Antigravity).
-
-## Como ativar
-
-Escolha **Claude Code** como alvo de IDE em `npx wize-dev-kit install` (padrão). Reinicie o Claude Code e diga *"Ative o Wizer e dê o briefing do projeto a ele"* ou rode `/wize-orchestrator`.

package/docs/harnesses/codex.md

@@ -1,21 +0,0 @@
-# OpenAI Codex — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](codex.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-Codex shares the same Anthropic Skill format as Claude Code and Kimi Code.
-
-## Output
-
-- `.agents/skills/wize-{code}/SKILL.md` — one directory per persona, workflow, or skill.
-- A root `AGENTS.md` (shared with Cursor, Windsurf, and Antigravity) listing the roster and pointing at `wize-orchestrator` as the entry point.
-
-## Notable
-
-- `.agents/skills/` is Codex's documented path for repository-local skills — the kit writes there directly, not to a Codex-specific directory.
-- **History:** 0.7.2 briefly moved this output to `.codex/skills/`, which broke skill loading in real Codex sessions; 0.7.3 reverted it to `.agents/skills/`. If you're on an older install, run `npx wize-dev-kit update` to fix the path.
-
-## Setup
-
-Pick **Codex** as an IDE target during `npx wize-dev-kit install` (or add it and re-run `npx wize-dev-kit sync`). Restart Codex, then run `/wize-orchestrator` or ask it to read `AGENTS.md`.

package/docs/harnesses/codex.pt-BR.md

@@ -1,21 +0,0 @@
-# OpenAI Codex — Wize Development Kit
-
-🌐 **Idiomas:** [English](codex.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-O Codex usa o mesmo formato de Skill da Anthropic que o Claude Code e o Kimi Code.
-
-## Saída
-
-- `.agents/skills/wize-{code}/SKILL.md` — um diretório por persona, workflow ou skill.
-- Um `AGENTS.md` na raiz (compartilhado com Cursor, Windsurf e Antigravity) listando o elenco e apontando pro `wize-orchestrator` como ponto de entrada.
-
-## Destaques
-
-- `.agents/skills/` é o caminho documentado do Codex pra skills locais do repositório — o kit grava lá diretamente, não num diretório específico do Codex.
-- **Histórico:** a 0.7.2 moveu essa saída, por um breve período, para `.codex/skills/`, o que quebrou o carregamento das skills em sessões reais do Codex; a 0.7.3 reverteu para `.agents/skills/`. Se sua instalação é antiga, rode `npx wize-dev-kit update` pra corrigir o caminho.
-
-## Como ativar
-
-Escolha **Codex** como alvo de IDE em `npx wize-dev-kit install` (ou adicione depois e rode `npx wize-dev-kit sync`). Reinicie o Codex e rode `/wize-orchestrator` ou peça pra ele ler o `AGENTS.md`.

package/docs/harnesses/continue.md

@@ -1,21 +0,0 @@
-# Continue.dev — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](continue.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-## Output
-
-`.continue/prompts/wize-{code}.prompt` — one file per persona, workflow, or skill.
-
-## Notable
-
-- Frontmatter: `name`, `description`, `invokable: true`. The `invokable` flag is what registers the file as a slash command in Continue's palette instead of a passive context document.
-
-## Setup
-
-Pick **Continue** as an IDE target during `npx wize-dev-kit install` (or add it and re-run `npx wize-dev-kit sync`). Reload the Continue extension, then run `/wize-orchestrator` from the prompt palette.
-
-## Reference
-
-- [docs.continue.dev — Prompts](https://docs.continue.dev/customize/deep-dives/prompts)

package/docs/harnesses/continue.pt-BR.md

@@ -1,21 +0,0 @@
-# Continue.dev — Wize Development Kit
-
-🌐 **Idiomas:** [English](continue.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-## Saída
-
-`.continue/prompts/wize-{code}.prompt` — um arquivo por persona, workflow ou skill.
-
-## Destaques
-
-- Frontmatter: `name`, `description`, `invokable: true`. É a flag `invokable` que registra o arquivo como slash command na paleta do Continue, em vez de um documento de contexto passivo.
-
-## Como ativar
-
-Escolha **Continue** como alvo de IDE em `npx wize-dev-kit install` (ou adicione depois e rode `npx wize-dev-kit sync`). Recarregue a extensão do Continue e rode `/wize-orchestrator` na paleta de prompts.
-
-## Referência
-
-- [docs.continue.dev — Prompts](https://docs.continue.dev/customize/deep-dives/prompts)

package/docs/harnesses/cursor.md

@@ -1,22 +0,0 @@
-# Cursor — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](cursor.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-## Output
-
-`.cursor/rules/wize-{code}.mdc` — one rule per persona, workflow, or skill.
-
-## Notable
-
-- Frontmatter: `description`, `globs` (empty — not file-pattern-triggered), `alwaysApply: false`. Every wize-dev-kit rule attaches **on demand**, matched by Cursor against its `description`, rather than being injected into every prompt.
-- No native agent/subagent split in this format — personas and workflows/skills share the same `.mdc` shape (unlike [OpenCode](opencode.md)).
-
-## Setup
-
-Pick **Cursor** as an IDE target during `npx wize-dev-kit install` (or add it and re-run `npx wize-dev-kit sync`). Restart Cursor, then reference `@wize-orchestrator` or ask it to activate Wizer.
-
-## Reference
-
-- [cursor.com/docs/context/rules](https://cursor.com/docs/context/rules)

package/docs/harnesses/cursor.pt-BR.md

@@ -1,22 +0,0 @@
-# Cursor — Wize Development Kit
-
-🌐 **Idiomas:** [English](cursor.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-## Saída
-
-`.cursor/rules/wize-{code}.mdc` — uma rule por persona, workflow ou skill.
-
-## Destaques
-
-- Frontmatter: `description`, `globs` (vazio — não é disparado por padrão de arquivo), `alwaysApply: false`. Toda rule do wize-dev-kit se anexa **sob demanda**, casada pelo Cursor contra sua `description`, em vez de ser injetada em todo prompt.
-- Sem divisão nativa agente/subagente nesse formato — personas e workflows/skills compartilham o mesmo formato `.mdc` (diferente do [OpenCode](opencode.pt-BR.md)).
-
-## Como ativar
-
-Escolha **Cursor** como alvo de IDE em `npx wize-dev-kit install` (ou adicione depois e rode `npx wize-dev-kit sync`). Reinicie o Cursor e referencie `@wize-orchestrator` ou peça pra ativar o Wizer.
-
-## Referência
-
-- [cursor.com/docs/context/rules](https://cursor.com/docs/context/rules)

package/docs/harnesses/generic.md

@@ -1,20 +0,0 @@
-# Generic fallback — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](generic.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-For any AI IDE that isn't one of the [dedicated targets](../../README.md#supported-harnesses).
-
-## Output
-
-- `.wize/agents/wize-{code}.md` — plain Markdown per persona, workflow, or skill: a heading, a one-line summary blockquote, and the body. No frontmatter, no slash-command wiring.
-- A root `AGENTS.md` — the same baseline pointer file also read natively by Codex, Cursor, Windsurf, and Antigravity. It is never overwritten if one already exists in the repo.
-
-## Notable
-
-- This target has no activation mechanism of its own — you point your assistant at `.wize/agents/wize-orchestrator.md` (or `AGENTS.md`) and ask it to read and follow it.
-
-## Setup
-
-Pick **Generic fallback** as an IDE target during `npx wize-dev-kit install` — it's on by default alongside your primary target, precisely so an unsupported second tool in the same repo still has something to read.

package/docs/harnesses/generic.pt-BR.md

@@ -1,20 +0,0 @@
-# Fallback genérico — Wize Development Kit
-
-🌐 **Idiomas:** [English](generic.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-Para qualquer IDE com IA que não esteja entre os [alvos dedicados](../../README.pt-BR.md#harnesses-suportadas).
-
-## Saída
-
-- `.wize/agents/wize-{code}.md` — Markdown puro por persona, workflow ou skill: um título, um resumo de uma linha em bloco de citação, e o corpo. Sem frontmatter, sem integração de slash command.
-- Um `AGENTS.md` na raiz — o mesmo arquivo-ponteiro de baseline lido nativamente por Codex, Cursor, Windsurf e Antigravity. Nunca é sobrescrito se já existir um no repositório.
-
-## Destaques
-
-- Esse alvo não tem mecanismo de ativação próprio — você aponta seu assistente pra `.wize/agents/wize-orchestrator.md` (ou `AGENTS.md`) e pede pra ele ler e seguir.
-
-## Como ativar
-
-Escolha **Fallback genérico** como alvo de IDE em `npx wize-dev-kit install` — ele já vem ligado por padrão junto do seu alvo principal, justamente pra que uma segunda ferramenta sem suporte dedicado no mesmo repositório ainda tenha algo pra ler.

package/docs/harnesses/kimi-code.md

@@ -1,19 +0,0 @@
-# Kimi Code — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](kimi-code.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-Moonshot's Kimi Code consumes the same public Anthropic Skill format as Claude Code and Codex.
-
-## Output
-
-`.kimi/skills/wize-{code}/SKILL.md` — one directory per persona, workflow, or skill, with companion files (`steps/`, `templates/`, `data/`) copied alongside.
-
-## Notable
-
-- Kimi Code also auto-detects `.claude/skills/` and `.agents/skills/` (Codex) if present in the repo, so installing the **Kimi Code** target alongside **Claude Code** and/or **Codex** is harmless — Kimi just has more places to find the same skills.
-
-## Setup
-
-Pick **Kimi Code** as an IDE target during `npx wize-dev-kit install` (or add it and re-run `npx wize-dev-kit sync`). Restart Kimi Code, then run `/wize-orchestrator`.

package/docs/harnesses/kimi-code.pt-BR.md

@@ -1,19 +0,0 @@
-# Kimi Code — Wize Development Kit
-
-🌐 **Idiomas:** [English](kimi-code.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-O Kimi Code, da Moonshot, consome o mesmo formato público de Skill da Anthropic usado pelo Claude Code e pelo Codex.
-
-## Saída
-
-`.kimi/skills/wize-{code}/SKILL.md` — um diretório por persona, workflow ou skill, com arquivos complementares (`steps/`, `templates/`, `data/`) copiados junto.
-
-## Destaques
-
-- O Kimi Code também autodetecta `.claude/skills/` e `.agents/skills/` (Codex) se existirem no repositório, então instalar o alvo **Kimi Code** junto com **Claude Code** e/ou **Codex** é inofensivo — o Kimi só passa a ter mais lugares onde achar as mesmas skills.
-
-## Como ativar
-
-Escolha **Kimi Code** como alvo de IDE em `npx wize-dev-kit install` (ou adicione depois e rode `npx wize-dev-kit sync`). Reinicie o Kimi Code e rode `/wize-orchestrator`.

package/docs/harnesses/opencode.md

@@ -1,31 +0,0 @@
-# OpenCode — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](opencode.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-OpenCode is the harness where the kit's persona/workflow split maps onto a **native** primitive instead of being flattened to one file type. Everywhere else, "agent" and "workflow" both become the same kind of file; on OpenCode they become two different things OpenCode itself understands.
-
-## Output
-
-`npx wize-dev-kit sync` (or `install`) writes two trees:
-
-- `.opencode/agents/wize-{code}.md` — the 10 personas (Wizer, Pepper, Shuri, Hawkeye...).
-- `.opencode/commands/wize-{code}.md` — the workflows and skills (`/wize-dev-story`, `/wize-code-review`, ...).
-
-## Notable
-
-- **`mode: primary | subagent`.** Only `wize-orchestrator` (Wizer) is `primary`. Every other persona is `subagent` — addressable directly with `@wize-agent-dev`, or delegated to automatically based on its `description`.
-- **`agent:` on commands.** Each workflow/skill's `owner:` frontmatter (e.g. `owner: wize-agent-dev # Shuri`) is resolved against the installed personas, so `/wize-dev-story` runs under Shuri's system prompt instead of whatever agent happened to be active. Commands with no clear owner (the Agent Builder skills) are left unbound.
-- **`subtask: true` on fan-out workers.** `wize-review-adversarial` and `wize-review-edge-case-hunter` — the two named subagent workers `wize-code-review` dispatches in parallel — are marked `subtask: true`, so OpenCode isolates them from the caller's context regardless of who invokes them.
-
-This is also the harness the kit's own subagent fan-out pattern (documented in Wizer's persona) is written against: name each worker, scope its context, dispatch on `mode: subagent` / `subtask: true`, tolerate partial failure.
-
-## Setup
-
-Pick **OpenCode** as an IDE target during `npx wize-dev-kit install` (or add it and re-run `npx wize-dev-kit sync`). Restart OpenCode, then say *"Activate Wizer and brief him on the project"* or run `/wize-orchestrator`.
-
-## Reference
-
-- [opencode.ai/docs/agents](https://opencode.ai/docs/agents/)
-- [opencode.ai/docs/commands](https://opencode.ai/docs/commands/)

package/docs/harnesses/opencode.pt-BR.md

@@ -1,31 +0,0 @@
-# OpenCode — Wize Development Kit
-
-🌐 **Idiomas:** [English](opencode.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-OpenCode é a harness onde a divisão persona/workflow do kit mapeia para uma primitiva **nativa**, em vez de ser achatada num único tipo de arquivo. Em todo o resto, "agente" e "workflow" viram o mesmo tipo de arquivo; no OpenCode eles viram duas coisas diferentes que o próprio OpenCode entende.
-
-## Saída
-
-`npx wize-dev-kit sync` (ou `install`) grava duas árvores:
-
-- `.opencode/agents/wize-{code}.md` — as 10 personas (Wizer, Pepper, Shuri, Hawkeye...).
-- `.opencode/commands/wize-{code}.md` — os workflows e skills (`/wize-dev-story`, `/wize-code-review`, ...).
-
-## Destaques
-
-- **`mode: primary | subagent`.** Só o `wize-orchestrator` (Wizer) é `primary`. Toda outra persona é `subagent` — endereçável direto com `@wize-agent-dev`, ou delegada automaticamente com base na `description`.
-- **`agent:` nos commands.** O campo `owner:` de cada workflow/skill (ex.: `owner: wize-agent-dev # Shuri`) é resolvido contra as personas instaladas, então `/wize-dev-story` roda sob o system prompt da Shuri em vez do agente que estava ativo. Commands sem um dono claro (as skills do Agent Builder) ficam sem vínculo.
-- **`subtask: true` nos workers de fan-out.** `wize-review-adversarial` e `wize-review-edge-case-hunter` — os dois workers nomeados que o `wize-code-review` dispara em paralelo — vêm marcados como `subtask: true`, então o OpenCode os isola do contexto de quem invocou, não importa quem seja.
-
-Esta também é a harness contra a qual o padrão de fan-out de subagentes do kit (documentado na persona da Wizer) foi escrito: nomear cada worker, escopar seu contexto, despachar via `mode: subagent` / `subtask: true`, tolerar falha parcial.
-
-## Como ativar
-
-Escolha **OpenCode** como alvo de IDE em `npx wize-dev-kit install` (ou adicione depois e rode `npx wize-dev-kit sync`). Reinicie o OpenCode e diga *"Ative o Wizer e dê o briefing do projeto a ele"* ou rode `/wize-orchestrator`.
-
-## Referência
-
-- [opencode.ai/docs/agents](https://opencode.ai/docs/agents/)
-- [opencode.ai/docs/commands](https://opencode.ai/docs/commands/)

package/docs/harnesses/windsurf.md

@@ -1,22 +0,0 @@
-# Windsurf (Codeium) — Wize Development Kit
-
-🌐 **Languages:** **English** · [Português (pt-BR)](windsurf.pt-BR.md)
-
-← [Back to README](../../README.md)
-
-## Output
-
-`.windsurf/rules/wize-{code}.md` — plain Markdown, no frontmatter: a heading, a one-line summary blockquote, and the full body.
-
-## Notable
-
-- Windsurf's Cascade reads everything under `.windsurf/rules/` at session start. Activation mode (always-on, manual, model-decided, glob) is configured **inside the IDE's Rules panel** per file — the kit doesn't encode it, since Windsurf's rule format has no frontmatter for it.
-- Same flattening as Cursor: no agent/workflow distinction in the file format.
-
-## Setup
-
-Pick **Windsurf** as an IDE target during `npx wize-dev-kit install` (or add it and re-run `npx wize-dev-kit sync`). Restart Windsurf, review the new rules under **Cascade → Rules**, then ask it to activate Wizer.
-
-## Reference
-
-- [docs.windsurf.com — Cascade rules](https://docs.windsurf.com/windsurf/cascade/memories#rules)

package/docs/harnesses/windsurf.pt-BR.md

@@ -1,22 +0,0 @@
-# Windsurf (Codeium) — Wize Development Kit
-
-🌐 **Idiomas:** [English](windsurf.md) · **Português (pt-BR)**
-
-← [Voltar ao README](../../README.pt-BR.md)
-
-## Saída
-
-`.windsurf/rules/wize-{code}.md` — Markdown puro, sem frontmatter: um título, um resumo de uma linha em bloco de citação, e o corpo completo.
-
-## Destaques
-
-- O Cascade do Windsurf lê tudo dentro de `.windsurf/rules/` no início da sessão. O modo de ativação (sempre ativo, manual, decidido pelo modelo, por glob) é configurado **dentro do painel de Rules da IDE**, por arquivo — o kit não codifica isso, já que o formato de rule do Windsurf não tem frontmatter pra isso.
-- Mesmo achatamento do Cursor: sem distinção agente/workflow no formato do arquivo.
-
-## Como ativar
-
-Escolha **Windsurf** como alvo de IDE em `npx wize-dev-kit install` (ou adicione depois e rode `npx wize-dev-kit sync`). Reinicie o Windsurf, confira as novas rules em **Cascade → Rules**, e peça pra ativar o Wizer.
-
-## Referência
-
-- [docs.windsurf.com — Cascade rules](https://docs.windsurf.com/windsurf/cascade/memories#rules)

package/src/core-skills/wize-customize/skill.md

@@ -1,116 +0,0 @@
----
-
-code: wize-customize
-description: "Use quando precisar personalizar um agente, skill ou workflow built-in sem alterar os arquivos originais do kit."
-name: Customize
-module: core
-status: ready
----
-
-# Customize
-
-**Goal.** Guide the user through creating an override (customize.toml) for a built-in agent, skill, or workflow. The override lives at `.wize/custom/{type}/{code}/customize.toml` and is loaded by the adapter at sync time.
-
-Wizer drives. Tony on call for agent structure.
-
-## When to use
-
-- "Override the persona of `wize-agent-pm`."
-- "Customize the wording in `wize-product-brief`."
-- "Add a tool to `wize-orchestrator`."
-
-## When NOT to use
-
-- Creating a brand-new agent/skill/workflow → use `wize-create-agent` (or `wize-create-skill` / `wize-create-workflow`).
-- Updating built-ins directly (the kit does not support forking built-ins; the next update would clobber your changes).
-
-## Inputs
-
-- A target: agent code, skill code, or workflow code.
-- A scope: what to override (name, title, persona, tools, body).
-
-## Output
-
-- A new file at `.wize/custom/{type}/{code}/customize.toml` (or update of an existing one).
-- A re-run of `wize-dev-kit sync` to apply the override.
-
-## Steps
-
-### 1. Identify the target
-
-The user names the code (e.g., `wize-agent-pm`). The skill validates:
-
-- Code shape: `wize-{kind}-{slug}`.
-- Exists in the kit's built-in roster.
-
-If the target does not exist, suggest `wize-create-agent` instead.
-
-### 2. Inspect the existing override
-
-If `.wize/custom/{type}/{code}/customize.toml` exists, read it. The user is updating; otherwise creating.
-
-### 3. Ask what to change
-
-The skill asks the user to pick from the overrideable fields:
-
-- `name` (display name)
-- `title` (job title)
-- `persona` (markdown body)
-- `tools` (list of tool names the agent can call)
-- `icon` (emoji)
-
-One field per run. Re-run for additional fields.
-
-### 4. Generate the customize.toml
-
-Write the new (or merged) customize.toml. Keep the structure as comments so the user can see the template.
-
-```toml
-# Override for {code} — generated by /wize-customize
-# Re-running the skill merges; lines you delete are restored on next install.
-
-[persona]
-# name = "Your name here"
-# title = "Your title here"
-
-[tools]
-# Add tool names the agent can call. Empty = default set.
-# tools = []
-```
-
-### 5. Re-sync
-
-Run `wize-dev-kit sync` (or instruct the user to). The override is loaded by the adapter and emitted to the IDE targets.
-
-### 6. Hand off
-
-Notify the user of:
-
-- File written: `.wize/custom/{type}/{code}/customize.toml`.
-- Sync completed (or instructions to run it).
-- Where to verify the override (e.g., `.claude/skills/{code}/SKILL.md`).
-
-## Output template
-
-The skill does not write a markdown output; it writes the customize.toml and re-syncs.
-
-```toml
-# Override for wize-agent-pm — generated by /wize-customize
-
-[persona]
-name = "Hill"  # shortened from "Maria Hill"
-
-[tools]
-# tools = []   # default set
-```
-
-## Anti-patterns Wizer rejects
-
-- Suggesting direct edits to built-in files in `node_modules/wize-dev-kit/`. (Next update clobbers.)
-- Creating a customize.toml with no overrideable fields filled. (Empty = no-op.)
-- Auto-running `wize-dev-kit sync` silently. (Confirm with the user first.)
-- Customizing the same field twice in one run. (One field per run.)
-
-## Hand-off
-
-> "Override written at `.wize/custom/{type}/{code}/customize.toml`. Sync applied. Verify in `.claude/skills/{code}/SKILL.md` (or your IDE target)."

package/src/core-skills/wize-editorial-review-prose/skill.md

@@ -1,94 +0,0 @@
----
-
-code: wize-editorial-review-prose
-description: "Use quando um artefato Wize (brief, PRD, ADR, gate) precisar de revisão de prosa — clareza, tom, jargão e precisão."
-name: Editorial Review — Prose
-module: core
-status: ready
----
-
-# Editorial Review — Prose
-
-**Goal.** Catch prose drift in Wize artifacts (brief, PRD, ADR, gate, story, retrospective). Peggy Carter runs the review; the user applies the fixes.
-
-Peggy drives. Wizer is on call for the call to action ("rewrite the whole section" or "leave it").
-
-## When to use
-
-- "Review the prose in this PRD."
-- "Find jargon and hedging in the brief."
-- "Is this gate file clear?"
-
-## When NOT to use
-
-- Spelling/grammar (use a linter; out of scope here).
-- Structure (missing sections, wrong ordering) → use `wize-editorial-review-structure`.
-- Tone change (tone is intentional; leave it).
-
-## Inputs
-
-- A markdown file under `.wize/`.
-- A line range (optional; default = whole file).
-
-## Output
-
-- A markdown review with line-level findings, each tagged with severity (nit / suggest / recommend).
-
-## Steps
-
-### 1. Read
-
-Read the file (or line range). Skip code blocks. Skip frontmatter.
-
-### 2. Hunt (4 areas)
-
-- **Voice.** Active voice preferred. Flag passive constructions ("was decided by", "is being implemented").
-- **Jargon.** Acronyms not defined on first use. Discipline-specific terms (e.g., "JTBD", "NFR") that are not in the project glossary.
-- **Hedging.** Softeners that hide commitment: "might", "could possibly", "we should consider", "it would be nice". Suggest a stronger verb.
-- **Pronouns.** Ambiguous "this", "it", "they" without a clear referent. Suggest a specific noun.
-
-### 3. Rank
-
-Per finding:
-
-- **Nit** — minor; user can ignore.
-- **Suggest** — worth a 5-second fix.
-- **Recommend** — blocks the artifact's clarity; should be fixed.
-
-### 4. Hand off
-
-Output is a markdown list. The user applies or rejects each finding. Peggy does not auto-edit.
-
-## Output template
-
-```markdown
----
-date: 2026-06-17
-file: planning/prd.md
-author: Peggy
----
-
-# Prose review — prd.md
-
-## Recommendations
-- L42: "we should consider using a token bucket" → "we use a token bucket". Hedging hides the decision. **[recommend]**
-- L78: "this might affect the user" → "this affects new signups". Pronoun + hedging. **[recommend]**
-
-## Suggests
-- L15: "rate-limit" appears 4 times. First use: spell out "rate-limit (per-IP cap on request rate)". **[suggest]**
-- L23: passive "is implemented by" → active "we implement". **[suggest]**
-
-## Nits
-- L88: comma splice. **[nit]**
-```
-
-## Anti-patterns Peggy rejects
-
-- Auto-editing the source file. (Suggest; never write.)
-- Commenting on tone or style preference. (Tone is intentional; structure is a separate review.)
-- Marking everything as recommend. (Cap at 5 recommends per review.)
-- Reviewing code blocks. (Out of scope.)
-
-## Hand-off
-
-> "Prose review complete for `{file}`. {N} findings. {M} recommends, {K} suggests, {L} nits. Apply or reject per finding."