@rse/ase 0.9.3 → 0.9.5

package/plugin/skills/ase-meta-brainstorm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-brainstorm
-argument-hint: "[--help|-h] <topic>"
+argument-hint: "[--help|-h] [--max-clarify|-c=3] [--min-ideas|-i=12] [--min-rank|-r=7] [--max-shortlist|-s=4] <topic>"
 description: >
     Collaboratively brainstorm a topic by diverging on ideas, converging
     through clustering and scoring, and distilling a shortlist with
@@ -15,16 +15,23 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-brainstorm">
 Collaboratively Brainstorm a Topic
 </skill>
 
+<expand name="getopt"
+    arg1="ase-meta-brainstorm"
+    arg2="--max-clarify|-c=3 --min-ideas|-i=12 --min-rank|-r=7 --max-shortlist|-s=4">
+    $ARGUMENTS
+</expand>
+
 <objective>
-Collaboratively brainstorm the topic <topic>$ARGUMENTS</topic> by first
-*diverging* into a broad space of candidate ideas, then *converging*
-through clustering and scoring, and finally distilling a *shortlist*
-with a single recommended direction.
+Collaboratively brainstorm the topic <topic><getopt-arguments/></topic>
+by first *diverging* into a broad space of candidate ideas, then
+*converging* through clustering and scoring, and finally distilling a
+*shortlist* with a single recommended direction.
 </objective>
 
 Guiding Tenets
@@ -83,19 +90,20 @@ Honor the following tenets throughout the brainstorming:
 
     Before generating any ideas, *explore the project context* (review
     relevant existing files, documentation, and recent changes) and
-    determine the <m/> (<m/>=1-3) *essential unknowns* about the topic
-    - the purpose, constraints, scope boundaries, and success criteria
-    that must be pinned down for the brainstorming to be reasonably
-    grounded.
+    determine the <m/> (<m/> = 1..<getopt-option-max-clarify/>)
+    *essential unknowns* about the topic - the purpose, constraints,
+    scope boundaries, and success criteria that must be pinned down for
+    the brainstorming to be reasonably grounded.
 
-    Notice: you are intentionally constraint to just 1-3 unknowns,
-    as too much upfront intent clarification kills the brainstorming
-    of ideas later. So, you *MUST* reduce the clarifications of the
-    unknowns to the absolute minimum!
+    Notice: you are intentionally constrained to just
+    1..<getopt-option-max-clarify/> unknowns, as too much upfront intent
+    clarification kills the brainstorming of ideas later. So, you *MUST*
+    reduce the clarifications of the unknowns to the absolute minimum in
+    general and cap it at <getopt-option-max-clarify/>!
 
-    For each essential unknown, derive a short 1-3 word facet <facet-M/>
-    and a corresponding question <question-M/> whose answer materially
-    changes which ideas make sense at all.
+    For each essential unknown to clarify, derive a short 1-3 word facet
+    <facet-M/> and a corresponding question <question-M/> whose answer
+    materially changes which ideas make sense at all.
 
     1.  For each <question-M/> in the iteration cycle <M/> (<M/>=1...<m/>):
 
@@ -152,8 +160,9 @@ Honor the following tenets throughout the brainstorming:
     variety in outcome.
 
     Do still *not* judge, rank, or prune ideas in this step. Generate
-    ideas until you either reach at least 12 distinct candidate ideas or
-    have clearly exhausted the meaningfully distinct space.
+    ideas until you either reach at least <getopt-option-min-ideas/> distinct
+    candidate ideas or have clearly exhausted the meaningfully distinct
+    space.
 
     Store each candidate idea in <idea-N/> with the format
     `**<idea-name-N/>**: <idea-statement-N/>` (where <idea-name-N/> is a
@@ -191,10 +200,10 @@ Honor the following tenets throughout the brainstorming:
         purpose and constraints on a Likert scale of 0 (poor) to 10
         (excellent), considering *value*, *uniqueness*, *risk*, and
         *alignment with the existing code base*. Keep only ideas in the
-        clusters with a rank of at least 7.
+        clusters with a rank of at least <getopt-option-min-rank/>.
 
     3.  From the scored ideas <idea-N/>, distill a *shortlist* of the top
-        3-4 options, sorted by rank from highest to lowest.
+        <getopt-option-max-shortlist/> options, sorted by rank from highest to lowest.
 
         For this, draw the shortlist from *distinct* clusters <cluster-C/>
         wherever possible - prefer a diverse shortlist spanning different
@@ -208,7 +217,7 @@ Honor the following tenets throughout the brainstorming:
         and its primary trade-off), and output the following <template/>:
 
         <template>
-        <ase-tpl-bullet-normal/> **DISTILLED IDEA <N/>**: <option-N/>
+        <ase-tpl-bullet-normal/> **DISTILLED IDEA**: <option-N/>
         </template>
 
     4.  Finally, derive a single *recommended idea* - the highest-ranked

package/plugin/skills/ase-meta-brainstorm/help.md

@@ -7,6 +7,10 @@
 
 `ase-meta-brainstorm`
     [`--help`|`-h`]
+    [`--max-clarify=3`]
+    [`--min-ideas`|`-i=12`]
+    [`--min-rank=7`]
+    [`--max-shortlist=4`]
     *topic*
 
 ##  DESCRIPTION
@@ -15,23 +19,46 @@ The `ase-meta-brainstorm` skill guides a collaborative ideation
 session on a *topic* *before* any implementation begins. It first
 *clarifies intent* by exploring the project context and interviewing
 the user - one grounded, multiple-choice question at a time - about
-purpose, constraints, scope, and success criteria. It then *diverges*
-into a broad space of candidate ideas pursued from deliberately diverse
-angles (MVP-first, risk-first, UX-first, reuse-first, and wildcard),
-without judging them.
+purpose, constraints, scope, and success criteria (asking at most
+`--max-clarify`, default 3, questions). It then *diverges* into a broad
+space of candidate ideas (at least `--min-ideas`, default 12) pursued from
+deliberately diverse angles (MVP-first, risk-first, UX-first,
+reuse-first, and wildcard), without judging them.
 
 Next it *converges* by clustering the ideas into coherent themes,
 pruning speculative or out-of-scope ones via *YAGNI*, and scoring the
-survivors on a 0-10 fit scale (keeping only those ranked 7 or higher).
-Finally it distills a *shortlist* of the top 3-4 directions - drawn from
-distinct clusters wherever possible - and derives a single
-*RECOMMENDATION*, being either the highest-ranked option or a principled
-synthesis of the shortlist.
+survivors on a 0-10 fit scale (keeping only those ranked `--min-rank`,
+default 7, or higher). Finally it distills a *shortlist* of the top
+`--max-shortlist`, default 4, directions - drawn from distinct clusters
+wherever possible - and derives a single *RECOMMENDATION*, being either
+the highest-ranked option or a principled synthesis of the shortlist.
 
 On completion the skill offers a *next step*: stop, or hand the
 recommended direction off to the `ase-task-edit`, `ase-code-craft`, or
 `ase-task-preflight` skills.
 
+##  OPTIONS
+
+`--max-clarify=3`:
+    The *maximum* number of essential-unknown clarification questions
+    asked in the *clarify intent* phase (default: 3). Lower it for a
+    faster, leaner intake, raise it for more upfront grounding.
+
+`--min-ideas`|`-i=12`:
+    The *minimum* number of candidate ideas to generate in the *diverge*
+    phase before converging (default: 12). Raise it for a broader idea
+    space, lower it for a quicker, narrower session.
+
+`--min-rank=7`:
+    The *minimum* 0-10 fit rank an idea must score to survive the
+    *converge* phase (default: 7). Raise it for a stricter filter, lower
+    it to retain more ideas.
+
+`--max-shortlist=4`:
+    The *maximum* number of distilled options on the final *shortlist*
+    (default: 4). Lower it for a sharper focus, raise it for more
+    finalists.
+
 ##  ARGUMENTS
 
 *topic*:
@@ -46,6 +73,19 @@ Brainstorm an approach for a new feature:
 ❯ /ase-meta-brainstorm an offline-first sync layer for the mobile app
 ```
 
+Brainstorm with a broader idea space of at least 20 candidates:
+
+```text
+❯ /ase-meta-brainstorm --min-ideas 20 an offline-first sync layer
+```
+
+Brainstorm quickly with a single clarification, a stricter score floor,
+and a tighter shortlist:
+
+```text
+❯ /ase-meta-brainstorm --max-clarify 1 --min-rank 8 --max-shortlist 3 an offline-first sync layer
+```
+
 ##  SEE ALSO
 
 `ase-meta-evaluate`, `ase-meta-quorum`, `ase-meta-diaboli`

package/plugin/skills/ase-meta-chat/SKILL.md

@@ -28,7 +28,7 @@ Query foreign LLM for: <query>$ARGUMENTS</query>
 
     ```text
         Agent(
-            name:          "ase:ase-meta-chat",
+            name:          "ase-meta-chat",
             description:   "Query Foreign LLM for Chat",
             subagent_type: "ase:ase-meta-chat",
             prompt:        <query/>

package/plugin/skills/ase-meta-diaboli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-diaboli
-argument-hint: "[--help|-h] <thesis>"
+argument-hint: "[--help|-h] [--count|-c <count>] <thesis>"
 description: >
     Challenge a thesis by playing "Devil’s Advocate" (latin: "Advocatus
     Diaboli"). Use when the user wants a thesis or statement
@@ -12,25 +12,40 @@ effort: xhigh
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-diaboli">
     Play "Devil's Advocate"
 </skill>
 
+<expand name="getopt"
+    arg1="ase-meta-diaboli"
+    arg2="--count|-c=10">
+    $ARGUMENTS
+</expand>
+
 <objective>
     Play "Devil’s Advocate" (latin: "Advocatus Diaboli") by relentlessly
-    challenging or criticising the thesis: <thesis>$ARGUMENTS</thesis>
+    challenging or criticising the thesis: <thesis><getopt-arguments/></thesis>
 </objective>
 
-1.  **Repeat Thesis**:
+Determine the minimum number of *anti-theses* to surface: set <count/>
+to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
+*less than or equal to 0*, use the default *10* instead.
+
+<flow>
+
+1.  <step id="STEP 1: Restate Thesis">
 
     Output the thesis with the following <template/>:
 
     <template>
-    <ase-tpl-bullet-secondary/> **THESIS**: <thesis/>
+    <ase-tpl-bullet-normal/> **THESIS**: <thesis/>
     </template>
 
-2.  **Determine Anti-Theses**:
+    </step>
+
+2.  <step id="STEP 2: Determine Anti-Theses">
 
     Reason on the thesis in <thesis/> by playing *Devil's Advocate*
     (latin: *Advocatus Diaboli*) by relentlessly challenging or
@@ -103,11 +118,11 @@ effort: xhigh
     For each Anti-Thesis or Counter-Argument rank it on a Likert scale
     of 0 (weak) to 10 (strong). Repeat the process of finding more
     Anti-Theses or Counter-Arguments until you EITHER have found at
-    least 10 Anti-Theses or Counter-Arguments with at least a rank
-    of 7 OR you have already checked a total of 50 Anti-Theses or
-    Counter-Arguments.
+    least <count/> Anti-Theses or Counter-Arguments with at least a rank
+    of 7 OR you have already checked a total of <count/> x 5 Anti-Theses
+    or Counter-Arguments.
 
-    Then, for the top-10 highest-ranked Anti-Theses or
+    Then, for the top-<count/> highest-ranked Anti-Theses or
     Counter-Arguments, sort them by their rank from highest to lowest,
     store each in <antithesis-N/> with the format `**<aspect-N/>**
     (rank: <rank-N/>/10): <statement-N/>` (where <aspect-N/> is a short
@@ -120,7 +135,9 @@ effort: xhigh
     <ase-tpl-bullet-signal/> **ANTITHESIS**: <antithesis-N/>
     </template>
 
-3.  **Dialectical Reasoning**:
+    </step>
+
+3.  <step id="STEP 3: Dialectical Reasoning">
 
     Following the Hegelian dialectics of...
 
@@ -150,3 +167,9 @@ effort: xhigh
     <ase-tpl-bullet-normal/> **SYNTHESIS**: <synthesis/>
     </template>
 
+    Do not output any further explanations.
+
+    </step>
+
+</flow>
+

package/plugin/skills/ase-meta-diaboli/help.md

@@ -7,6 +7,7 @@
 
 `ase-meta-diaboli`
     [`--help`|`-h`]
+    [`--count`|`-c` *count*]
     *thesis*
 
 ##  DESCRIPTION
@@ -20,20 +21,31 @@ cases, *Reductio Ad Absurdum*, exposing hidden costs, and pre-mortem
 thinking - while targeting the claim rather than its proponent and
 yielding where the argument genuinely holds.
 
-The skill iterates until it has found at least ten anti-theses
+The skill iterates until it has found at least *count* anti-theses
 (counter-arguments) each ranked at least 7 on a 0 (weak) to 10
-(strong) Likert scale, reports the top ten sorted from strongest to
+(strong) Likert scale, reports the top *count* sorted from strongest to
 weakest, and finally applies *Hegelian dialectics* (*Thesis* +
 *Antithesis* → *Synthesis*) to derive a single-sentence *SYNTHESIS*
 that preserves what is true in both the thesis and its antitheses
 while discarding what is false.
 
+The `--count`/`-c` *count* option sets the minimum number of strong
+anti-theses to surface (default *10*), raising or lowering the floor of
+counter-arguments hunted for, sorted, and reported in the single
+challenge pass. A `0`, negative, or non-numeric value falls back to the
+default *10*.
+
 The intent is constructive: stress-testing the thesis in good faith to
 arrive at a better final decision, not obstructing or merely being
 contrarian.
 
 ##  ARGUMENTS
 
+`--count`, `-c` *count*:
+    Surface at least *count* strong anti-theses (default *10*) before
+    sorting and reporting the top *count* and deriving the *SYNTHESIS*. An
+    invalid or non-positive *count* reverts to the default *10*.
+
 *thesis*:
     The statement, claim, or position to be relentlessly challenged.
     It may be technical, factual, or opinion-based; the skill attacks
@@ -53,6 +65,12 @@ Stress-test a design decision:
 ❯ /ase-meta-diaboli We should rewrite the service in Rust.
 ```
 
+Surface at least fifteen anti-theses:
+
+```text
+❯ /ase-meta-diaboli --count 15 We should rewrite the service in Rust.
+```
+
 ##  SEE ALSO
 
 `ase-meta-why`, `ase-meta-evaluate`, `ase-meta-quorum`,

package/plugin/skills/ase-meta-diff/SKILL.md

@@ -306,7 +306,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             labels ultra short (basenames or module names only).
 
         2.  Dispatch the rendering to the `ase-meta-diagram` sub-agent by
-            calling the tool `Agent(name: "ase:ase-meta-diagram",
+            calling the tool `Agent(name: "ase-meta-diagram",
             description: "Diagram Rendering", subagent_type:
             "ase:ase-meta-diagram", prompt: "<mermaid-spec/>")` and capture
             its returned `text` field as <diagram/>.

package/plugin/skills/ase-meta-quorum/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-quorum
-argument-hint: "[--help|-h] <question>"
+argument-hint: "[--help|-h] [--models|-m <model>[,...]] <question>"
 description: >
     Query Multiple AIs for Quorum Answer.
 user-invocable: true
@@ -13,11 +13,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-quorum">
 Query Multiple AIs for Quorum Answer
 </skill>
 
+<expand name="getopt"
+    arg1="ase-meta-quorum"
+    arg2="--models|-m=(all|chatgpt|gemini|deepseek|grok|glm|qwen)...">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Find a *quorum answer* on an arbitrary question,
 by querying *multiple* AIs for an *optimal consensus*.
@@ -30,7 +37,7 @@ by querying *multiple* AIs for an *optimal consensus*.
     Prepare the LLM query by setting <query/> to the following <template/>:
 
     <template>
-    $ARGUMENTS.
+    <getopt-arguments/>.
     Please respond with facts and very concise and brief only,
     usually with just 1 to 7 corresponding bullet points and with short sentences.
     Optionally, mention potential cruxes which should be noticed.
@@ -53,12 +60,20 @@ by querying *multiple* AIs for an *optimal consensus*.
 
 2.  <step id="STEP 2: Query Foreign AIs">
 
+    The user-selectable foreign models are restricted by the
+    `--models`/`-m` option, parsed into <getopt-option-models/>
+    as a comma-separated list of model tokens. The default is
+    the single token `all`. If <getopt-option-models/> contains
+    the token `all`, you *MUST* treat it as the full list
+    `chatgpt,gemini,deepseek,grok,glm,qwen` (all models). Anthropic
+    Claude (yourself) is *always* included, independent of this option.
+
     <define name="agent">
     Call the `Agent` tool:
 
     ```text
         Agent(
-            name:          "ase:ase-meta-chat",
+            name:          "ase-meta-chat-<arg2/>",
             description:   "Query Foreign LLM: <arg1/>",
             subagent_type: "ase:ase-meta-chat",
             prompt:        "<arg2/> <query/>"
@@ -67,12 +82,28 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     </define>
 
+    Query only those foreign models whose token is contained in
+    <getopt-option-models/> (where `all` selects every model); silently
+    skip all others:
+
+    <if condition="<getopt-option-models/> contains `all` OR <getopt-option-models/> contains `chatgpt`">
     <expand name="agent" arg1="OpenAI ChatGPT" arg2="chatgpt"></expand>
+    </if>
+    <if condition="<getopt-option-models/> contains `all` OR <getopt-option-models/> contains `gemini`">
     <expand name="agent" arg1="Google Gemini"  arg2="gemini"></expand>
+    </if>
+    <if condition="<getopt-option-models/> contains `all` OR <getopt-option-models/> contains `deepseek`">
     <expand name="agent" arg1="DeepSeek"       arg2="deepseek"></expand>
+    </if>
+    <if condition="<getopt-option-models/> contains `all` OR <getopt-option-models/> contains `grok`">
     <expand name="agent" arg1="xAI Grok"       arg2="grok"></expand>
+    </if>
+    <if condition="<getopt-option-models/> contains `all` OR <getopt-option-models/> contains `glm`">
     <expand name="agent" arg1="Z.AI GLM"       arg2="glm"></expand>
+    </if>
+    <if condition="<getopt-option-models/> contains `all` OR <getopt-option-models/> contains `qwen`">
     <expand name="agent" arg1="Alibaba Qwen"   arg2="qwen"></expand>
+    </if>
 
     You *MUST* *NOT* output anything in this step.
 
@@ -116,7 +147,7 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     <template>
     **QUESTION**:
-    $ARGUMENTS
+    <getopt-arguments/>
 
     &#x25CF; **CONSENSUS ANSWER**:
     - [...]
@@ -153,7 +184,8 @@ by querying *multiple* AIs for an *optimal consensus*.
     - [...]
     </template>
 
-    In this output, remove the sections of those AIs which were not available.
+    In this output, remove the sections of those AIs which were not
+    queried (excluded via `--models`/`-m`) or were not available.
     You *MUST* *NOT* output any further explanations yourself.
 
     </step>

package/plugin/skills/ase-meta-quorum/help.md

@@ -7,6 +7,7 @@
 
 `ase-meta-quorum`
     [`--help`|`-h`]
+    [`--models`|`-m` *model*[,...]]
     *question*
 
 ##  DESCRIPTION
@@ -23,6 +24,17 @@ a Likert scale of `0..N` (where `N` is the number of available
 responders), and reports the consensus answer alongside the
 complete, unmodified individual responses.
 
+##  OPTIONS
+
+`--models`|`-m` *model*[,...]:
+    Restrict the *foreign* LLMs that are queried to the given
+    comma-separated list of *model* tokens. Recognized tokens are
+    `all`, `chatgpt`, `gemini`, `deepseek`, `grok`, `glm`, and `qwen`,
+    where `all` selects every model. The default is `all`. Models that
+    are not selected (or not available) are *silently skipped*.
+    Anthropic Claude (the skill itself) is *always* included,
+    independent of this option.
+
 ##  ARGUMENTS
 
 *question*:
@@ -36,6 +48,12 @@ Ask the quorum a factual question:
 ❯ /ase-meta-quorum What are the most common causes of memory leaks in Node.js?
 ```
 
+Ask only a subset of the foreign models:
+
+```text
+❯ /ase-meta-quorum --models chatgpt,gemini,grok Which sorting algorithm is fastest in practice?
+```
+
 ##  SEE ALSO
 
 `ase-meta-chat`, `ase-meta-search`, `ase-meta-evaluate`.

package/plugin/skills/ase-meta-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-review
-argument-hint: "[--help|-h]"
+argument-hint: "[--help|-h] [--severity|-S=(LOW|MEDIUM|HIGH)]"
 description: >
     Perform a holistic, human-reviewer-style critique of the currently
     staged Git changes and emit an approve/reject verdict with
@@ -17,11 +17,19 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-review">
 Review Staged Changes
 </skill>
 
+<expand name="getopt"
+    arg1="ase-meta-review"
+    arg2="--severity|-S=(LOW|MEDIUM|HIGH)">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Review the currently staged Git changes the way an *experienced human
 reviewer* would - judging them *holistically* against the change's *own
@@ -82,7 +90,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     ```text
         Agent(
-            name:          "ase:ase-meta-review",
+            name:          "ase-meta-review",
             description:   "Review Investigation",
             subagent_type: "ase:ase-meta-review",
             mode:          "plan",
@@ -98,7 +106,17 @@ explicitly requested by this procedure via outputs based on a <template/>!
     Then *derive* the overall <verdict/> from <findings/>: set
     <verdict/> to `REJECT - DEMANDS CHANGES` if *any* finding in
     <findings/> has a `severity` field of `HIGH`; otherwise set
-    <verdict/> to `APPROVE`.
+    <verdict/> to `APPROVE`. The verdict is derived *before* the
+    severity floor below, so a suppressed `HIGH` finding still drives the
+    verdict.
+
+    Then *apply the severity floor* selected via <getopt-option-severity/>
+    (default `LOW`): define the ordinal rank `LOW`=1, `MEDIUM`=2,
+    `HIGH`=3. *Keep* a finding in <findings/> if and only if its
+    `severity` field is `ACCEPTED` *or* `rank(severity)` is greater than
+    or equal to `rank(<getopt-option-severity/>)`; *silently drop* all
+    other findings. With the default floor `LOW`, all findings are kept.
+    `ACCEPTED` findings are *never* dropped.
 
     You *MUST* *NOT* output anything else in this STEP 2.
 

package/plugin/skills/ase-meta-review/help.md

@@ -6,6 +6,8 @@
 ##  SYNOPSIS
 
 `ase-meta-review`
+    [`--help`|`-h`]
+    [`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`)]
 
 ##  DESCRIPTION
 
@@ -51,10 +53,20 @@ inspects *logic and semantics*, `ase-meta-diff` narrates *what changed*
 `ase-meta-review` renders a *reviewer's judgement* on a concrete diff
 before it is committed.
 
+##  OPTIONS
+
+`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`):
+    Set the *severity floor* (default `LOW`): findings below the chosen
+    threshold are silently suppressed, ordered `LOW` < `MEDIUM` <
+    `HIGH`. The default `LOW` keeps all findings; `ACCEPTED` findings are
+    never suppressed. The floor only affects the rendered findings table;
+    the overall *verdict* is still derived from all findings, so a
+    suppressed `HIGH` finding still yields a *REJECT* verdict.
+
 ##  ARGUMENTS
 
-The `ase-meta-review` skill takes no arguments; it always reviews the
-currently *staged* Git changes.
+The `ase-meta-review` skill takes no positional arguments; it always
+reviews the currently *staged* Git changes.
 
 ##  EXAMPLES
 
@@ -64,6 +76,12 @@ Review the currently staged changes before committing:
 ❯ /ase-meta-review
 ```
 
+Review the staged changes, reporting only `MEDIUM` and `HIGH` findings:
+
+```text
+❯ /ase-meta-review -S MEDIUM
+```
+
 ##  SEE ALSO
 
 `ase-meta-diff`, `ase-meta-commit`, `ase-code-lint`, `ase-code-analyze`,