diff --git a/skills/mappa-vitya-brainstorming/SKILL.md b/skills/mappa-vitya-brainstorming/SKILL.md
index 09c7820..62d0730 100644
--- a/skills/mappa-vitya-brainstorming/SKILL.md
+++ b/skills/mappa-vitya-brainstorming/SKILL.md
@@ -53,7 +53,7 @@ become tasks, how many reviews". It passes a **routing decision** to
 | Where does the buffer live | A mappa `brainstorm` entity (status=buffer). NOT a file. |
 | When is a storm mature | The buffer-completion criterion, NOT a gut feel. |
 | Where does the spec/decisions go | A mappa **wiki concept**. Before any wiki work — run `mappa-knowledge` first. |
-| Multiple impl tasks | Paired `<slug>-review` per impl + an umbrella `<topic>-review`. Both blocked, non-implementer. |
+| Multiple impl tasks | **ИЛИ**: единичная таска → парная `<slug>-review`; кластер из одного шторма → зонтичный `<topic>-review` (парные НЕ создаются). Blocked, non-implementer. |
 | Who implements | ASK who implements (you are not automatically it). Boss does not implement (Rule 10). |
 | Who notifies | Send an `inbox_send` letter to every affected project. |
 | Zero-impl storm | Mature when decisions are distilled into a wiki concept; NO review umbrella (criterion holds vacuously). |
@@ -87,15 +87,15 @@ first** (Rule 6), it loads the project's AGENTS entity and the read/ingest
 contract.
 
 **5. Review is a separate, non-implementer role.**
-When multiple implementation tasks come out of the storm, create BOTH:
-- a **paired `<slug>-review`** per impl task (status=blocked, blocker=impl-ref);
-- an **umbrella `<topic>-review`** (status=blocked, blocker=impl-slugs).
+Review routing (оператор 2026-08-28): **парные review ИЛИ зонтик** (не BOTH).
+- **Единичная импл-таска** из шторма → парная `<slug>-review` (status=blocked, blocker=impl-ref), без зонтика.
+- **Кластер тасок** из одного шторма → зонтичный `<topic>-review` на весь кластер (status=blocked, blocker=impl-slugs); парные на каждую таску НЕ создаются (иначе двойное ревью одного и того же).
 
 Reviewer is the next session in the target, **not the implementer** — this
 fights the "I just wrote it" bias. You (the brainstorming agent) generate the
-review tasks; you do NOT do the code review yourself. The umbrella review is
-done only when its reviewer confirms — the storm is not mature until the
-umbrella `<topic>-review` is resolved, not merely created.
+review tasks; you do NOT do the code review yourself. The review is done only
+when its reviewer confirms — the storm is not mature until the review
+(`<slug>-review` ИЛИ `<topic>-review`) is resolved, not merely created.
 
 **6. Ask who implements. Do not assume it's you.**
 Brainstorms run anywhere by any agent. The implementer is not automatically the
@@ -128,7 +128,7 @@ promote skill executes the mappa write/promotion.
 | "I'll just jot notes in a markdown file" | Buffer must be a mappa brainstorm entity; the file channel is closed. |
 | "It feels done, let's write it up" | Maturity is the completion criterion, not a feeling. |
 | "The spec can live in docs/ for now" | Spec goes to a mappa wiki concept; before wiki — run `mappa-knowledge`. |
-| "I'll review my own tasks, then hand to the user" | Review is a separate non-implementer role; paired + umbrella. |
+| "I'll review my own tasks, then hand to the user" | Review is a separate non-implementer role; парная ИЛИ зонтик (не BOTH). |
 | "I'm the coding agent, I'll just implement it" | Ask who implements; in the boss zone the boss does not implement. |
 | "I'll note the impact in the spec, no need to ping" | Notify every affected project with an `inbox_send` letter. |