@rse/ase 0.9.7 → 0.9.8

package/plugin/skills/ase-arch-discover/SKILL.md

@@ -86,6 +86,15 @@ for the technology stack to *provide* the *needed functionality*
     </step>
 
 3.  <step id="STEP 3: Discover Components">
+    -   If <stack/> is "Unknown", the technology stack could not be
+        determined and no component discovery backend is available.
+        Inform the user with just the following <template/> and then
+        *STOP* the entire flow (do not perform any further steps):
+
+        <template>
+        <ase-tpl-bullet-normal/> **RESULT**: technology stack could not be determined -- component discovery is only supported for JavaScript, TypeScript, Java, and Kotlin projects.
+        </template>
+
     -   From <stack/> and <functionality/>, derive essential keywords
         <keyword-L/> (L=1-M), which allow you to search for suitable
         components.
@@ -122,7 +131,7 @@ for the technology stack to *provide* the *needed functionality*
             their unique Maven coordinates <package-K/> of the form
             `groupId:artifactId`.
 
-        -   Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+<keyword-M/>&rows=<getopt-option-limit/>&wt=json'`
+        -   Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+[...]+<keyword-M/>&rows=<getopt-option-limit/>&wt=json'`
             to *specifically* discover an additional set of a maximum
             of <getopt-option-limit/> *Maven packages* <component-K/> and at least their
             unique Maven coordinates <package-K/> (i.e. `<g/>:<a/>` from
@@ -167,11 +176,11 @@ for the technology stack to *provide* the *needed functionality*
         <template>
         <ase-tpl-bullet-normal/> **COMPONENT HINTS**:
 
-        | ⚑ *Component*      | ▣ *Package*    | ⚖ *Hint*  |
-        | :----------------- | :------------- | :-------- |
-        | **<component-1/>** | `<package-1/>` | <info-1/> |
+        | ⚑ *Component* | ▣ *Package*    | ⚖ *Hint*  |
+        | :------------ | :------------- | :-------- |
+        | **<name-1/>** | `<package-1/>` | <info-1/> |
         [...]
-        | **<component-N/>** | `<package-N/>` | <info-N/> |
+        | **<name-N/>** | `<package-N/>` | <info-N/> |
         </template>
 
     -   Display the discovered components as a Markdown *table*
@@ -180,11 +189,11 @@ for the technology stack to *provide* the *needed functionality*
         <template>
         <ase-tpl-bullet-normal/> **COMPONENT RANKING**:
 
-        | ⚑ *Component*      | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
-        | :----------------- | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
-        | **<component-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
+        | ⚑ *Component* | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
+        | :------------ | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
+        | **<name-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
         [...]
-        | **<component-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
+        | **<name-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
         </template>
     </step>
 </flow>

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

@@ -202,9 +202,12 @@ problems in *performance* and *efficiency*, or problems in *security*.
         <template>(`<filename/>#<function-or-method/>`)</template>.
 
     -   In <description/>, classify the problem with a <severity/>
-        of <template>LOW</template>, <template>MEDIUM</template> or
-        <template>HIGH</template>, ranked by the estimated *impact* of the
-        problem.
+        of <template>LOW</template>, <template>MEDIUM</template>,
+        <template>HIGH</template>, or <template>ACCEPTED</template>,
+        ranked by the estimated *impact* of the problem. Use
+        <template>ACCEPTED</template> when the problem is a deliberate,
+        justified trade-off that should remain on record but is never
+        dropped by the severity floor (see STEP 3).
 
     -   <if condition="<getopt-option-performance/> is equal `true`">
         In <evidence/>, ground the finding by citing either the inferred
@@ -241,5 +244,3 @@ problems in *performance* and *efficiency*, or problems in *security*.
     </step>
 
 </flow>
-
-</output>

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

@@ -2,8 +2,8 @@
 name: ase-code-craft
 argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
 description: >
-    Craft Source Code:
-    Use when user wants to create or craft a new feature from scratch.
+    Craft Source:
+    Use when user wants to "create", "add", or "craft" a new feature from scratch.
 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 <feature/> has the format `<id/>: <text/>` where <id/> matches
-        the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`, then set
-        <feature><text/></feature> 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="
+            <feature/> has the format `<id/>: <text/>` AND
+            <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+        ">
+        Set <feature><text/></feature> 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 <feature/> is empty,
-        ask the user interactively, without a special tool, for the
+    3.  <if condition="<feature/> is empty">
+        Ask the user interactively, without a special tool, for the
         initial feature with a single question:
 
         `**No feature known yet. What is the feature you want to craft?**`
 
         Then set <feature/> to the response of the user.
+        </if>
 
     4.  <if condition="
             <ase-task-id/> is equal `default` and
@@ -210,8 +215,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ○   [...]
         ○   [...]
         ○   [...]
-        ⊕   *PRO*: [...]
-        ⊖   *CON*: [...]
+        ⊕   **PRO**: [...]
+        ⊖   **CON**: [...]
         <optional-diagram/>
         </template>
 
@@ -246,7 +251,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
 5.  **Choose Feature Crafting Approach**:
 
-    1.  If <getopt-option-auto/> is equal `false`:
+    1.  <if condition="<getopt-option-auto/> is equal `false`">
         Let the *user interactively choose* the preferred feature
         approach A<n/> with the help of the <user-dialog-tool/> tool.
         Use the header `Select Approach`, use `A<n/>: <short-summary/>`
@@ -254,14 +259,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 feature
         approach with ` ⚝ **RECOMMENDATION** ⚝` here again.
+        </if>
 
-    2.  If <getopt-option-auto/> is equal `true`:
+    2.  <else>
         Set <n/> to the number of the feature 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 Feature Crafting Plan**:
 
@@ -307,40 +314,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-explain/SKILL.md

@@ -71,7 +71,7 @@ code and *explain* it in a *brief*, *standardized*, and *concise* way.
     `sequenceDiagram` for actor/message flow, or `flowchart TB` for
     boxes-and-lines component layouts. Then dispatch the rendering to
     the `ase-meta-diagram` sub-agent by calling the tool `Agent(name:
-    "ase:ase-meta-diagram", description: "Diagram Rendering", subagent_type:
+    "ase-meta-diagram", description: "Diagram Rendering", subagent_type:
     "ase:ase-meta-diagram", prompt: <mermaid-spec/>)` and reproduce its
     returned fenced code block verbatim in the response text. Do *not*
     hand-draw.

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

@@ -70,7 +70,7 @@ Give *insights* into the project through the source code of $ARGUMENTS.
     Then run the following command...
 
     ```
-    git log --format=format: --name-only --since="1 year ago" | sort | uniq -c | sort -nr | head -10
+    git log --format=format: --name-only --since="1 year ago" | grep -v '^$' | sort | uniq -c | sort -nr | head -10
     ```
 
     ...and then display its result as a table with a table head and

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

@@ -101,7 +101,7 @@ related to a set of code quality aspects.
 3.  <step id="STEP 3: Correction">
 
     1.  You *MUST* call the MCP tool `ase_config_set(key: "agent.skill", val:
-        "ase-docs-proofread", scope: "session:<ase-session-id/>")` of the
+        "ase-code-lint", scope: "session:<ase-session-id/>")` of the
         `ase` MCP server. You *MUST* *NOT* output anything related to
         this.
 
@@ -150,7 +150,7 @@ related to a set of code quality aspects.
                 3.  Append the following <template/> to <diff-file/>:
 
                     <template>
-                    @@ -<line/>,<n/> +<line/>,<m/> @@
+                    @@ -<old-start/>,<n/> +<new-start/>,<m/> @@
                      <context-before/>
                     -<old-text/>
                     +<new-text/>
@@ -158,8 +158,16 @@ related to a set of code quality aspects.
                     </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.
 
                 </for>
 
@@ -190,7 +198,7 @@ related to a set of code quality aspects.
             </template>
 
             </if>
-            <if condition="<getopt-option-auto/> is 'true'">
+            <else>
 
             Report the solution with the following <template/>:
 
@@ -201,7 +209,7 @@ related to a set of code quality aspects.
 
             </template>
 
-            </if>
+            </else>
 
         6.  <if condition="<getopt-option-auto/> is not 'true'">
 
@@ -215,12 +223,12 @@ related to a set of code quality aspects.
 
             </if>
 
-            <if condition="<getopt-option-auto/> is 'true'">
+            <else>
 
             Set <result>ACCEPT</result>.
             You *MUST* *NOT* output anything else in this step 6.
 
-            </if>
+            </else>
 
         7.  Check <result/> and dispatch accordingly:
 

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
@@ -200,8 +205,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ○   [...]
         ○   [...]
         ○   [...]
-        ⊕   **PRO*: [...]
-        ⊖   **CON*: [...]
+        ⊕   **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**:
 
@@ -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-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
@@ -249,8 +255,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         ○   [...]
         ○   [...]
         ○   [...]
-        ⊕   *PRO*: [...]
-        ⊖   *CON*: [...]
+        ⊕   **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**:
 
@@ -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-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.