@rse/ase 0.9.6 → 0.9.8

package/plugin/skills/ase-code-refactor/SKILL.md

@@ -2,8 +2,8 @@
 name: ase-code-refactor
 argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <request>"
 description: >
-    Refactor Code Base:
-    Use when user wants to refactor the code base.
+    Refactor Code:
+    Use when user wants to "refactor", or "change" the code base.
 user-invocable: true
 disable-model-invocation: false
 effort: xhigh
@@ -69,20 +69,25 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         </template>
         </if>
 
-    2.  If <request/> has the format `<id/>: <text/>` where <id/> matches
-        the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
-        <request><text/></request> and <ase-task-id><id/></ase-task-id>
-        and call the `ase_task_id(id: "<ase-task-id/>", session:
-        "<ase-session-id/>")` tool from the `ase` MCP server to
-        implicitly switch the task. Do not output anything.
+    2.  <if condition="
+            <request/> has the format `<id/>: <text/>` AND
+            <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+        ">
+        Set <request><text/></request> and
+        <ase-task-id><id/></ase-task-id> and call the `ase_task_id(id:
+        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the
+        `ase` MCP server to implicitly switch the task. Do not output
+        anything.
+        </if>
 
-    3.  If <request/> is empty,
-        ask the user interactively, without a special tool, for the
+    3.  <if condition="<request/> is empty">
+        Ask the user interactively, without a special tool, for the
         initial request with a single question:
 
         `**No refactoring details known yet. What is the refactoring you want to request?**`
 
         Then set <request/> to the response of the user.
+        </if>
 
     4.  <if condition="
             <ase-task-id/> is equal `default` and
@@ -196,12 +201,12 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ● **APPROACH A<n/>**<annotation/>: *<summary/>*
-        ○ [...]
-        ○ [...]
-        ○ [...]
-        ⊕ *pro*: [...]
-        ⊖ *con*: [...]
+        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ○   [...]
+        ○   [...]
+        ○   [...]
+        ⊕   **PRO**: [...]
+        ⊖   **CON**: [...]
         <optional-diagram/>
         </template>
 
@@ -236,7 +241,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
 5.  **Choose Refactoring Approach**:
 
-    1.  If <getopt-option-auto/> is equal `false`:
+    1.  <if condition="<getopt-option-auto/> is not 'true'">
         Let the *user interactively choose* the preferred refactoring
         approach A<n/> with the help of the <user-dialog-tool/> tool.
         Use the header `Select Approach`, use `A<n/>: <short-summary/>`
@@ -245,14 +250,16 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         small *code change previews*. Mark your recommended refactoring
         approach with ` ⚝ **RECOMMENDATION** ⚝` here again. Except for
         the interactive selection, do not output anything in this step.
+        </if>
 
-    2.  If <getopt-option-auto/> is equal `true`:
+    2.  <else>
         Set <n/> to the number of the refactoring approach A<n/> you recommend.
         Output a hint with the following <template/>:
 
         <template>
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **auto-chosen approach A<n/>**
         </template>
+        </else>
 
 6.  **Compose Refactoring Plan**:
 
@@ -269,7 +276,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
-        You *MUST* completely omit the `## ※ VERIFICATION` section
+        You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
         <content/>.
         </if>
@@ -298,40 +305,40 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         Treat <getopt-option-next/> as a comma-separated chronological
         list of pre-selected next-step tokens. *Peek* the *first* token
         as <head/> (or `none` if the list is `none`/empty).
+        Set <args>--int-reuse-task</args>.
 
         1.  <if condition="<head/> is equal `IMPLEMENT`">
             Consume the head: set <getopt-option-next/> to the remaining
-            tokens (joined back with `,`, or `none` if empty). Set
-            <args></args> (empty).
+            tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
-            Call the tool `Skill(skill: "ase:ase-task-implement", args: <args/>)`
+            Call the tool `Skill(skill: "ase:ase-task-implement", args: "<args/>")`
             to *implement* the freshly composed plan, bypassing `ase-task-edit`.
             </if>
 
-        2.  <if condition="<head/> is equal `PREFLIGHT`">
+        2.  <elseif condition="<head/> is equal `PREFLIGHT`">
             Consume the head: set <getopt-option-next/> to the remaining
-            tokens (joined back with `,`, or `none` if empty). Set
-            <args></args> (empty).
+            tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
-            Call the tool `Skill(skill: "ase:ase-task-preflight", args: <args/>)`
+            Call the tool `Skill(skill: "ase:ase-task-preflight", args: "<args/>")`
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
-            </if>
+            </elseif>
 
-        3.  <if condition="
-                <head/> is not equal `IMPLEMENT` AND
-                <head/> is not equal `PREFLIGHT`
-            ">
-            Forward the *entire* (unshifted) list to `ase-task-edit`, which
-            will consume its head itself. Set <args></args> (empty).
-            <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (append to args).
+        3.  <else>
+            Hand off to `ase-task-edit`.
+            <if condition="<head/> is equal `EDIT`">
+                Consume the head: set <getopt-option-next/> to the remaining
+                tokens (joined back with `,`, or `none` if empty).
             </if>
-            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            All remaining tokens are `ase-task-edit`'s own vocabulary
+            and are forwarded verbatim, so `ase-task-edit` consumes its
+            head itself.
+            <if condition="<getopt-option-next/> is not equal `none`">
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
+            </else>
 

package/plugin/skills/ase-code-refactor/help.md

@@ -34,7 +34,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     asking the user via the interactive dialog.
 
 `--dry`|`-d`:
-    Compose the plan *without* the `※ VERIFICATION` section. When
+    Compose the plan *without* the `##  VERIFICATION` section. When
     `ase-task-implement` later applies such a plan, it strictly skips
     the entire verification phase (no build, tests, linter,
     type-checker, or program execution) once the source files have
@@ -43,7 +43,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended refactoring approach, compose the plan *without* the
-    `※ VERIFICATION` section, immediately hand off to `ase-task-implement`,
+    `##  VERIFICATION` section, immediately hand off to `ase-task-implement`,
     and finally `ase-task-delete` the now-consumed plan. This gives a
     single, fast *one-shot* refactoring mode.
 

package/plugin/skills/ase-code-resolve/SKILL.md

@@ -3,7 +3,7 @@ name: ase-code-resolve
 argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <problem>"
 description: >
     Resolve Problem:
-    Use when user wants a bug fixed or problem resolved.
+    Use when user wants to "bugfix" or "fix" code or "resolve" a problem.
 user-invocable: true
 disable-model-invocation: false
 effort: xhigh
@@ -81,20 +81,26 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         </template>
         </if>
 
-    3.  If <problem/> has the format `<id/>: <text/>` where <id/> matches
-        the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
-        <problem><text/></problem> and <ase-task-id><id/></ase-task-id>
-        and call the `ase_task_id(id: "<ase-task-id/>", session:
-        "<ase-session-id/>")` tool from the `ase` MCP server to
-        implicitly switch the task. Do not output anything.
+    3.  <if condition="
+            <problem-id/> is not set AND
+            <problem/> has the format `<id/>: <text/>` AND
+            <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+        ">
+        Set <problem><text/></problem> and
+        <ase-task-id><id/></ase-task-id> and call the `ase_task_id(id:
+        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the
+        `ase` MCP server to implicitly switch the task. Do not output
+        anything.
+        </if>
 
-    4.  If <problem/> is empty,
-        ask the user interactively, without a special tool, for the
+    4.  <if condition="<problem/> is empty">
+        Ask the user interactively, without a special tool, for the
         initial problem with a single question:
 
         `**No problem details known yet. What is the problem you want to resolve?**`
 
         Then set <problem/> to the response of the user.
+        </if>
 
     5.  <if condition="
             <ase-task-id/> is equal `default` and
@@ -245,12 +251,12 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ● **APPROACH A<n/>**<annotation/>: *<summary/>*
-        ○ [...]
-        ○ [...]
-        ○ [...]
-        ⊕ *pro*: [...]
-        ⊖ *con*: [...]
+        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ○   [...]
+        ○   [...]
+        ○   [...]
+        ⊕   **PRO**: [...]
+        ⊖   **CON**: [...]
         <optional-diagram/>
         </template>
 
@@ -285,7 +291,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
 5.  **Choose Problem Resolution Approach**:
 
-    1.  If <getopt-option-auto/> is equal `false`:
+    1.  <if condition="<getopt-option-auto/> is not 'true'">
         Let the *user interactively choose* the preferred resolution
         approach A<n/> with the help of the <user-dialog-tool/> tool.
         Use the header `Select Approach`, use `A<n/>: <short-summary/>`
@@ -293,14 +299,16 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         of the approach A<n/>), and *single-selection* only and provide
         small *code change previews*. Mark your recommended resolution
         approach with ` ⚝ **RECOMMENDATION** ⚝` here again.
+        </if>
 
-    2.  If <getopt-option-auto/> is equal `true`:
+    2.  <else>
         Set <n/> to the number of the resolution approach A<n/> you recommend.
         Output a hint with the following <template/>:
 
         <template>
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **auto-chosen approach A<n/>**
         </template>
+        </else>
 
 6.  **Compose Problem Resolution Plan**:
 
@@ -317,7 +325,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
-        You *MUST* completely omit the `## ※ VERIFICATION` section
+        You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
         <content/>.
         </if>
@@ -336,7 +344,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
 
     4.  If <problem-id/> is set (i.e. the <problem/> was retrieved from
-        `ase_kv_get` in STEP 1.3 via key `ase-issue-<problem-id/>`),
+        `ase_kv_get` in STEP 1.1 via key `ase-issue-<problem-id/>`),
         you *MUST* additionally call the `ase_kv_delete(key:
         "ase-issue-<problem-id/>")` tool of the `ase` MCP
         server to remove the now-resolved analyzer result from the
@@ -353,40 +361,40 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         Treat <getopt-option-next/> as a comma-separated chronological
         list of pre-selected next-step tokens. *Peek* the *first* token
         as <head/> (or `none` if the list is `none`/empty).
+        Set <args>--int-reuse-task</args>.
 
         1.  <if condition="<head/> is equal `IMPLEMENT`">
             Consume the head: set <getopt-option-next/> to the remaining
-            tokens (joined back with `,`, or `none` if empty). Set
-            <args></args> (empty).
+            tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
-            Call the tool `Skill(skill: "ase:ase-task-implement", args: <args/>)`
+            Call the tool `Skill(skill: "ase:ase-task-implement", args: "<args/>")`
             to *implement* the freshly composed plan, bypassing `ase-task-edit`.
             </if>
 
-        2.  <if condition="<head/> is equal `PREFLIGHT`">
+        2.  <elseif condition="<head/> is equal `PREFLIGHT`">
             Consume the head: set <getopt-option-next/> to the remaining
-            tokens (joined back with `,`, or `none` if empty). Set
-            <args></args> (empty).
+            tokens (joined back with `,`, or `none` if empty).
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
-            Call the tool `Skill(skill: "ase:ase-task-preflight", args: <args/>)`
+            Call the tool `Skill(skill: "ase:ase-task-preflight", args: "<args/>")`
             to *preflight* the freshly composed plan, bypassing `ase-task-edit`.
-            </if>
+            </elseif>
 
-        3.  <if condition="
-                <head/> is not equal `IMPLEMENT` AND
-                <head/> is not equal `PREFLIGHT`
-            ">
-            Forward the *entire* (unshifted) list to `ase-task-edit`, which
-            will consume its head itself. Set <args></args> (empty).
-            <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (append to args).
+        3.  <else>
+            Hand off to `ase-task-edit`.
+            <if condition="<head/> is equal `EDIT`">
+                Consume the head: set <getopt-option-next/> to the remaining
+                tokens (joined back with `,`, or `none` if empty).
             </if>
-            Then call the tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`.
+            All remaining tokens are `ase-task-edit`'s own vocabulary
+            and are forwarded verbatim, so `ase-task-edit` consumes its
+            head itself.
+            <if condition="<getopt-option-next/> is not equal `none`">
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
+            Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
+            </else>
 

package/plugin/skills/ase-code-resolve/help.md

@@ -39,7 +39,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     asking the user via the interactive dialog.
 
 `--dry`|`-d`:
-    Compose the plan *without* the `※ VERIFICATION` section. When
+    Compose the plan *without* the `##  VERIFICATION` section. When
     `ase-task-implement` later applies such a plan, it strictly skips
     the entire verification phase (no build, tests, linter,
     type-checker, or program execution) once the source files have
@@ -48,7 +48,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended resolution approach, compose the plan *without* the
-    `※ VERIFICATION` section, immediately hand off to `ase-task-implement`,
+    `##  VERIFICATION` section, immediately hand off to `ase-task-implement`,
     and finally `ase-task-delete` the now-consumed plan. This gives a
     single, fast *one-shot* resolution mode.
 

package/plugin/skills/ase-docs-distill/SKILL.md

@@ -122,7 +122,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         only*: keep at most `min(<getopt-option-top/>, number of salient
         points)` points and *never pad* the list with filler to reach
         the bound. If <getopt-option-top/> is *non-numeric* or *less
-        than or equal to 0*, use the default *10* instead.
+        than or equal to 0*, use the default *5* instead.
 
     You *MUST* *NOT* output anything in this STEP 2.
 

package/plugin/skills/ase-docs-distill/help.md

@@ -32,15 +32,15 @@ one block per point, each showing its *LOCATION*, *EVIDENCE*,
 ranking is *auditable* rather than an opaque ordering.
 
 The `--top`/`-t` *N* option is a *length dial* that bounds the list to at
-most *N* points (default *10*). It is an *upper bound only*: when the
+most *N* points (default *5*). It is an *upper bound only*: when the
 document has fewer salient points than *N*, the skill emits only the
 points it found and *never pads* the list with filler; a `0`, negative, or
-non-numeric value falls back to the default *10*.
+non-numeric value falls back to the default *5*.
 
 ##  ARGUMENTS
 
 `--top`, `-t` *N*:
-    Bound the ranked list to at most *N* key points (default *10*). The
+    Bound the ranked list to at most *N* key points (default *5*). The
     bound is a *cap*, never a *quota* - fewer points are emitted when the
     document does not contain *N* salient ones, and an invalid or
     non-positive *N* reverts to the default.

package/plugin/skills/ase-docs-proofread/SKILL.md

@@ -116,8 +116,8 @@ Analyze documents for spelling, punctuation, or grammar errors
 
         3.  <if condition="<getopt-option-auto/> is not 'true'">
 
-            Render the proposed correction as a *unified diff* with *one*
-            line of context in a fenced block based on the following <template/>:
+            Render the proposed correction as a *unified diff* with *up to
+            two* lines of context in a fenced block based on the following <template/>:
 
             <template>
 
@@ -126,7 +126,7 @@ Analyze documents for spelling, punctuation, or grammar errors
             ```diff
             --- <file/> (original)
             +++ <file/> (corrected)
-            @@ -<line/>,<n/> +<line/>,<m/> @@
+            @@ -<old-start/>,<n/> +<new-start/>,<m/> @@
              <context-before/>
             -<old-text/>
             +<new-text/>
@@ -136,8 +136,16 @@ Analyze documents for spelling, punctuation, or grammar errors
             </template>
 
             Hints:
-            -   The <n/> is the number of lines in <old-text/>.
-            -   The <m/> is the number of lines in <new-text/>.
+            -   The <old-start/> is the line of the first hunk line, i.e.,
+                the line of <context-before/> (one before <line/>).
+            -   The <new-start/> is the same as <old-start/> (the unchanged
+                <context-before/> line shares the same start in both files).
+            -   The <n/> is the total number of old-side hunk lines, i.e.,
+                the number of lines in <context-before/>, <old-text/>, and
+                <context-after/> combined.
+            -   The <m/> is the total number of new-side hunk lines, i.e.,
+                the number of lines in <context-before/>, <new-text/>, and
+                <context-after/> combined.
 
             </if>
 
@@ -153,20 +161,21 @@ Analyze documents for spelling, punctuation, or grammar errors
 
             </if>
 
-            <if condition="<getopt-option-auto/> is 'true'">
+            <else>
 
             Set <result>ACCEPT</result>.
 
-            </if>
+            </else>
 
         5.  Check <result/> and dispatch accordingly:
 
             -   <if condition="<result/> is 'ACCEPT'">
 
-                Invoke the `Edit` tool to apply the change exactly as shown
-                in the diff. The operation will be auto-approved because of
-                the active proofread marker, so *no* interactive permission
-                prompt will appear. Then continue with the next <item/>.
+                Invoke the `Edit` tool to apply the change by replacing
+                <old-text/> with <new-text/> at <file/>:<line/>. The operation
+                will be auto-approved because of the active proofread marker,
+                so *no* interactive permission prompt will appear. Then
+                continue with the next <item/>.
 
                 </if>
 
@@ -174,8 +183,8 @@ Analyze documents for spelling, punctuation, or grammar errors
 
                 Generate a *new* proposal for the *same* <item/>,
                 incorporating the user's free-text hint from <result/>
-                after the "OTHER:" prefix, and loop back to substep 2 of
-                this iteration. There is *no* cap on refinement rounds -
+                after the "OTHER:" prefix, and *go back* to substep 2 of
+                this `for`-iteration. There is *no* cap on refinement rounds -
                 keep refining until the user picks `ACCEPT` or `REJECT`.
 
                 </if>

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

@@ -113,15 +113,15 @@ Honor the following tenets throughout the brainstorming:
             <ase-tpl-bullet-signal/> FACET <M/>/<m/>: **<facet-M/>**, QUESTION: **<question-M/>**
             </template>
 
-        2.  Determine *up to 4* grounded candidate answers
+        2.  Determine *2 to 4* grounded candidate answers
             <answer-M-K/> (K={1,2,3,4}) from the code base, the documented
             context, and your world knowledge.
 
         3.  Use an interactive user dialog with header <facet-M/> and
             question <question-M/>, and let the user select the
-            <answer-M/> out of the candidate answers <answer-M-K/> (just
-            leave out all answers in case you have determined less than
-            4 potential answers)
+            <answer-M/> out of the candidate answers <answer-M-K/> (leave
+            out the answer lines of those candidate answers you have
+            not determined)
 
             <expand name="user-dialog">
                 <facet-M/>: <question-M/>
@@ -131,7 +131,26 @@ Honor the following tenets throughout the brainstorming:
                 <answer-M-4/>: (fourth grounded candidate answer)
             </expand>
 
-        4.  Output the following <template/>:
+        4.  Dispatch on the dialog <result/>:
+
+            -   If <result/> is `CANCEL`:
+                Skip the remaining sub-steps of this iteration cycle and
+                continue directly with sub-step 2 below (cancellation handling).
+
+            -   If <result/> starts with `ERROR:`:
+                Ask the user interactively, without a special tool, the
+                question <question-M/> directly and set <answer-M/> to the
+                response of the user.
+
+            -   If <result/> matches `OTHER: <text/>`:
+                Set <answer-M><text/></answer-M> (take the user's free-text answer).
+
+            -   Otherwise:
+                Set <answer-M><result/></answer-M> (take the selected candidate answer).
+
+            Do not output anything in this sub-step.
+
+        5.  Output the following <template/>:
 
             <template>
             <ase-tpl-bullet-normal/> FACET <M/>/<m/>: **<facet-M/>**, ANSWER: **<answer-M/>**
@@ -182,7 +201,7 @@ Honor the following tenets throughout the brainstorming:
     set and finally into a recommendation.
 
     1.  *Cluster*: group the candidate ideas into <c/> coherent clusters
-        <cluster-C/> (a short 1-4 word label, C=1...</c>), collapsing
+        <cluster-C/> (a short 1-4 word label, C=1...<c/>), collapsing
         near-duplicates and discarding ideas pruned by *You Aren't Gonna
         Need It (YAGNI)* (speculative, out-of-scope, or contradicting
         documented context).

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

@@ -7,10 +7,10 @@
 
 `ase-meta-brainstorm`
     [`--help`|`-h`]
-    [`--max-clarify=3`]
+    [`--max-clarify`|`-c=3`]
     [`--min-ideas`|`-i=12`]
-    [`--min-rank=7`]
-    [`--max-shortlist=4`]
+    [`--min-rank`|`-r=7`]
+    [`--max-shortlist`|`-s=4`]
     *topic*
 
 ##  DESCRIPTION
@@ -33,13 +33,9 @@ default 7, or higher). Finally it distills a *shortlist* of the top
 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`:
+`--max-clarify`|`-c=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.
@@ -49,12 +45,12 @@ recommended direction off to the `ase-task-edit`, `ase-code-craft`, or
     phase before converging (default: 12). Raise it for a broader idea
     space, lower it for a quicker, narrower session.
 
-`--min-rank=7`:
+`--min-rank`|`-r=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`:
+`--max-shortlist`|`-s=4`:
     The *maximum* number of distilled options on the final *shortlist*
     (default: 4). Lower it for a sharper focus, raise it for more
     finalists.

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

@@ -11,9 +11,9 @@ disable-model-invocation: false
 effort: high
 allowed-tools:
     - "Bash(git diff *)"
-    - "Bash(git grep:*)"
-    - "Bash(git ls-files:*)"
-    - "Bash(grep:*)"
+    - "Bash(git grep *)"
+    - "Bash(git ls-files *)"
+    - "Bash(grep *)"
     - "Agent"
 ---
 
@@ -98,7 +98,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
             </template>
 
-        2.  Render a *two-column table* with one row per discovered
+        2.  Render a *three-column table* with one row per discovered
             *intent group* present in the <diff/>. Output the following
             table header <template/>:
 
@@ -205,6 +205,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         | **<deviation/>** | <location/> | <reason/>                         |
 
         </template>
+        </if>
     </step>
 
 4.  <step id="STEP 4: Score Against Risk Rubric"