@rse/ase 0.9.8 → 0.9.9

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

@@ -53,7 +53,9 @@ You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
 filesystem-modifying tool during this entire skill. The *only*
 permitted way to persist artifacts is via `ase_task_save(...)`.
 
-1.  **Reason About Feature**:
+<flow>
+
+1.  <step id="STEP 1: Reason About Feature">
 
     1.  <if condition="
             <feature/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
@@ -114,7 +116,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     8.  Do not output anything in this step, unless you asked the user.
 
-2.  **Investigate Code Base**:
+    </step>
+
+2.  <step id="STEP 2: Investigate Code Base">
 
     1.  Check the existing source files for all code which is related to the
         requested new <feature/>.
@@ -122,9 +126,11 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  Check the architecture of the existing code base to understand the
         overall structures and dynamics.
 
-    3.  Do not output anything in this step.
+    3.  Do not output anything in this STEP 2.
 
-3.  **Internalize Crafting Tenets**:
+    </step>
+
+3.  <step id="STEP 3: Internalize Crafting Tenets">
 
     You *MUST* internalize and honor the following tenets when crafting the new feature.
     Do not output anything.
@@ -179,7 +185,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Honor the non-functional requirements Performance, Security,
             Scalability, Comprehensibility.
 
-4.  **Find Feature Crafting Approaches**:
+    </step>
+
+4.  <step id="STEP 4: Choose Feature Crafting Approaches">
 
     You *MUST* perform the following sub-steps *internally* and *without
     any output* until and including the recommendation decision. Only
@@ -208,16 +216,14 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         </template>
 
     5.  Now report each approach with the following <template/>,
-        inlining its pros/cons derived in sub-step 2:
+        inlining its pros/cons derived in sub-step 2, and do not output
+        anything else in this step:
 
         <template>
         ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
         ○   [...]
-        ○   [...]
-        ○   [...]
         ⊕   **PRO**: [...]
         ⊖   **CON**: [...]
-        <optional-diagram/>
         </template>
 
         Hints:
@@ -225,23 +231,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         -   Give a short one-sentence <summary/> of the feature
             approach plus *precise* and *ultra brief and concise*
             feature information. Try to keep the number of bullet points
-            (●) in the range of 1-4.
-
-        -   In case of a *complex feature situation* only, visualize
-            it with an optional diagram <optional-diagram/> by building
-            a Mermaid specification <mermaid-spec/> (e.g. `flowchart
-            TB`, `stateDiagram-v2`, `sequenceDiagram`, `classDiagram`,
-            or `erDiagram`, depending on intent) and dispatching the
-            rendering to the `ase-meta-diagram` sub-agent by calling
-            the tool `Agent(name: "ase-meta-diagram", description:
-            "Diagram Rendering", subagent_type: "ase:ase-meta-diagram",
-            prompt: <mermaid-spec/>)`, reproducing its returned fenced
-            code block verbatim. For *current vs. proposed* comparisons,
-            render each side as a *separate* `ase-meta-diagram`
-            invocation and stack the rendered blocks *vertically*
-            (labels `**Before:**` / `**After:**`); never side-by-side.
-            Omit <optional-diagram/> entirely for simple or purely local
-            situations.
+            (`○ [...]`) in the range of 1-4.
 
     6.  Indicate end of reporting by showing the following <template/>:
 
@@ -249,28 +239,40 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <ase-tpl-foot title="APPROACHES"/>
         </template>
 
-5.  **Choose Feature Crafting Approach**:
+    7.  <if condition="<getopt-option-auto/> is not equal `true`">
+
+        You *MUST* use the custom `custom-dialog` and *NOT* the
+        `AskUserQuestion`-based `user-dialog` to let the *user
+        interactively choose* the preferred approach A<n/>.
+
+        Per approach A<n/>, use the option `A<n/>: <short-summary/>`
+        where <short-summary/> is an ultra brief summary of the approach
+        A<n/>. For your recommended approach, use
+        `A<n/>: ⚝ **RECOMMENDATION** ⚝: <short-summary/>` instead.
+
+        Now raise the user dialog:
+
+        <expand name="custom-dialog">
+            Select Approach: Select your preferred crafting approach to follow?
+            A<n/>: <short-summary/>
+            [...]
+        </expand>
 
-    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/>`
-        for the option (where <short-summary/> is an ultra brief summary
-        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>
+        <else>
 
-    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**:
+    </step>
+
+5.  <step id="STEP 5: Compose Feature Crafting Plan">
 
     1.  *Compose a feature plan* for the chosen feature A<n/> by
         closely aligning to the existing architecture and the existing
@@ -300,7 +302,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <timestamp-modified/> information and calculate the number of
         words <words/> of <content/>.
 
-    3.  You *MUST* *save* the resulting plan content with the
+    3.  You then *MUST* *save* the resulting plan content with the
         `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
 
     4.  Output a hint with the following <template/>:
@@ -351,3 +353,6 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
             </else>
 
+    <step>
+
+</flow>

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

@@ -86,5 +86,5 @@ Craft a feature under a named task and directly hand off to implementation:
 
 ##  SEE ALSO
 
-`ase-code-refactor`, `ase-code-resolve`, `ase-task-edit`,
-`ase-task-preflight`, `ase-task-implement`.
+[`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-task-edit`](../ase-task-edit/help.md),
+[`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md).

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

@@ -40,4 +40,4 @@ Explain a specific function:
 
 ##  SEE ALSO
 
-`ase-code-insight`, `ase-code-analyze`, `ase-arch-analyze`.
+[`ase-code-insight`](../ase-code-insight/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).

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

@@ -40,4 +40,4 @@ Get insights into a specific subsystem:
 
 ##  SEE ALSO
 
-`ase-code-explain`, `ase-code-analyze`, `ase-arch-analyze`.
+[`ase-code-explain`](../ase-code-explain/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).

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

@@ -100,10 +100,12 @@ 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-code-lint", scope: "session:<ase-session-id/>")` of the
-        `ase` MCP server. You *MUST* *NOT* output anything related to
-        this.
+    1.  *Mark this skill as the active edit-capable skill* so that the
+        ASE `pre-tool-use` hook auto-approves the subsequent `Edit`
+        invocations on *any* invocation path (slash command *or* `Skill`
+        tool). Call the `ase_config_set(key: "agent.skill", val:
+        "ase-code-lint", scope: "session:<ase-session-id/>")` tool
+        from the `ase` MCP server. Do not output anything in this substep.
 
     2.  Iterate over all problems:
 
@@ -213,9 +215,11 @@ related to a set of code quality aspects.
 
         6.  <if condition="<getopt-option-auto/> is not 'true'">
 
-            Ask the user how to proceed via an interactive user dialog:
+            Let the *user interactively choose* what to do as the next
+            step. For this you *MUST* use the custom `custom-dialog` and
+            not the `AskUserQuestion` based `user-dialog`:
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog">
                 CORRECTION: How would you like to proceed with this proposed correction?
                 ACCEPT: Apply the proposed correction.
                 REJECT: Skip this proposed correction.
@@ -234,8 +238,11 @@ related to a set of code quality aspects.
 
             -   <if condition="<result/> is 'ACCEPT'">
                 Invoke the `Edit` tool to apply the changes exactly
-                as shown in the <diff/>. After applying the changes,
-                just continue with the next <item/>.
+                as shown in the <diff/>. The operation will be
+                auto-approved by the ASE `pre-tool-use` hook (which
+                tracks the active skill), so *no* interactive permission
+                prompt will appear. After applying the changes, just
+                continue with the next <item/>.
                 </if>
 
             -   <if condition="<result/> starts with 'OTHER'">
@@ -257,9 +264,11 @@ related to a set of code quality aspects.
 
         </for>
 
-    3.  You *MUST* call the MCP tool `ase_config_delete(key: "agent.skill",
-        scope: "session:<ase-session-id/>")` of the `ase` MCP server.
-        You *MUST* *NOT* output anything related to this.
+    3.  *Clear the active edit-capable skill marker* now that all `Edit`
+        invocations are done, so a later unrelated `Edit` is *not*
+        auto-approved. Call the `ase_config_delete(key: "agent.skill",
+        scope: "session:<ase-session-id/>")` tool from the `ase` MCP
+        server. Do not output anything in this substep.
 
     4.  You *MUST* *NOT* output any further additional explanations or
         summaries at the end of this skill processing, except for the

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

@@ -63,5 +63,5 @@ Lint a directory, reporting only `MEDIUM` and `HIGH` findings:
 
 ##  SEE ALSO
 
-`ase-code-analyze`, `ase-code-resolve`, `ase-code-refactor`,
-`ase-docs-proofread`.
+[`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-code-refactor`](../ase-code-refactor/help.md),
+[`ase-docs-proofread`](../ase-docs-proofread/help.md).

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

@@ -53,7 +53,9 @@ You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
 filesystem-modifying tool during this entire skill. The *only*
 permitted way to persist artifacts is via `ase_task_save(...)`.
 
-1.  **Reason About Refactoring**:
+<flow>
+
+1.  <step id="STEP 1: Reason About Refactoring">
 
     1.  <if condition="
             <request/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
@@ -114,7 +116,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     8.  Do not output anything in this step, unless you asked the user.
 
-2.  **Investigate Code Base**:
+    </step>
+
+2.  <step id="STEP 2: Investigate Code Base">
 
     1.  Check the existing source files for all code which is related to the
         refactoring <request/>.
@@ -122,9 +126,11 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  Check the architecture of the existing code base to understand the
         overall structures and dynamics.
 
-    3.  Do not output anything in this step.
+    3.  Do not output anything in this STEP 2.
 
-3.  **Internalize Refactoring Tenets**:
+    </step>
+
+3.  <step id="STEP 3: Internalize Refactoring Tenets">
 
     You *MUST* internalize and honor the following tenets when refactoring.
     Do not output anything.
@@ -168,7 +174,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Design clear interfaces, contracts, and data models --
             with high attention to boundaries and modularity.
 
-4.  **Find Refactoring Approaches**:
+    </step>
+
+4.  <step id="STEP 4: Choose Refactoring Approaches">
 
     You *MUST* perform the following sub-steps *internally* and *without
     any output* until and including the recommendation decision. Only
@@ -203,11 +211,8 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <template>
         ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
         ○   [...]
-        ○   [...]
-        ○   [...]
         ⊕   **PRO**: [...]
         ⊖   **CON**: [...]
-        <optional-diagram/>
         </template>
 
         Hints:
@@ -215,23 +220,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         -   Give a short one-sentence <summary/> of the refactoring
             approach plus *precise* and *ultra brief and concise*
             refactoring information. Try to keep the number of bullet
-            points (●) in the range of 1-4.
-
-        -   In case of a *complex refactoring situation* only,
-            visualize it with an optional diagram <optional-diagram/>
-            by building a Mermaid specification <mermaid-spec/>
-            (e.g. `flowchart TB`, `stateDiagram-v2`, `sequenceDiagram`,
-            `classDiagram`, or `erDiagram`, depending on intent) and
-            dispatching the rendering to the `ase-meta-diagram`
-            sub-agent by calling the tool `Agent(name: "ase-meta-diagram",
-            description: "Diagram Rendering", subagent_type:
-            "ase:ase-meta-diagram", prompt: <mermaid-spec/>)`, reproducing
-            its returned fenced code block verbatim. For *current
-            vs. proposed* comparisons, render each side as a *separate*
-            `ase-meta-diagram` invocation and stack the rendered blocks
-            *vertically* (labels `**Before:**` / `**After:**`); never
-            side-by-side. Omit <optional-diagram/> entirely for simple
-            or purely local situations.
+            points (`○ [...]`) in the range of 1-4.
 
     6.  Indicate end of reporting by showing the following <template/>:
 
@@ -239,29 +228,40 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <ase-tpl-foot title="APPROACHES"/>
         </template>
 
-5.  **Choose Refactoring Approach**:
-
-    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/>`
-        for the option (where <short-summary/> is an ultra brief summary
-        of the approach A<n/>), and *single-selection* only and provide
-        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.
+    7.  <if condition="<getopt-option-auto/> is not `true`">
+
+        You *MUST* use the custom `custom-dialog` and *NOT* the
+        `AskUserQuestion`-based `user-dialog` to let the *user
+        interactively choose* the preferred approach A<n/>.
+
+        Per approach A<n/>, use the option `A<n/>: <short-summary/>`
+        where <short-summary/> is an ultra brief summary of the approach
+        A<n/>. For your recommended approach, use
+        `A<n/>: ⚝ **RECOMMENDATION** ⚝: <short-summary/>` instead.
+
+        Now raise the user dialog:
+
+        <expand name="custom-dialog">
+            Select Approach: Select your preferred refactoring approach to follow?
+            A<n/>: <short-summary/>
+            [...]
+        </expand>
+
         </if>
+        <else>
 
-    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**:
+    </step>
+
+5.  <step id="STEP 5: Compose Refactoring Plan">
 
     1.  *Compose a refactoring plan* for the chosen refactoring A<n/> by
         closely aligning to the existing architecture and the existing
@@ -342,3 +342,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
             </else>
 
+    <step>
+
+</flow>
+

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

@@ -86,5 +86,5 @@ Refactor under a named task and directly hand off to implementation:
 
 ##  SEE ALSO
 
-`ase-code-craft`, `ase-code-resolve`, `ase-task-edit`,
-`ase-task-preflight`, `ase-task-implement`.
+[`ase-code-craft`](../ase-code-craft/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-task-edit`](../ase-task-edit/help.md),
+[`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md).

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

@@ -53,7 +53,9 @@ You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
 filesystem-modifying tool during this entire skill. The *only*
 permitted way to persist artifacts is via `ase_task_save(...)`.
 
-1.  **Reason About Problem**:
+<flow>
+
+1.  <step id="STEP 1: Reason About Problem">
 
     1.  If <problem/> matches the regexp `^[PT]\d+$` (i.e. a bare issue
         identifier like `P1`, `P2`, `T1`, `T2`, ...),
@@ -166,7 +168,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
           verbatim. Omit <optional-diagram/> entirely for simple or
           purely local situations.
 
-2.  **Investigate Code Base**:
+    </step>
+
+2.  <step id="STEP 2: Investigate Code Base">
 
     1.  Check the existing source files for all code which is related to the
         requested <problem/> resolution.
@@ -174,9 +178,11 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  Check the architecture of the existing code base to understand the
         overall structures and dynamics.
 
-    3.  Do not output anything in this step.
+    3.  Do not output anything in this STEP 2.
 
-3.  **Internalize Problem Resolution Tenets**:
+    </step>
+
+3.  <step id="STEP 3: Internalize Problem Resolution Tenets">
 
     You *MUST* internalize and honor the following tenets when resolving the problem.
     Do not output anything.
@@ -218,7 +224,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             *theoretical, fictive, or unexpected* errors *should* be
             handled more generally and in parent scopes.
 
-4.  **Find Problem Resolution Approaches**:
+    </step>
+
+4.  <step id="STEP 4: Choose Problem Resolution Approaches">
 
     You *MUST* perform the following sub-steps *internally* and *without
     any output* until and including the recommendation decision. Only
@@ -253,35 +261,16 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <template>
         ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
         ○   [...]
-        ○   [...]
-        ○   [...]
         ⊕   **PRO**: [...]
         ⊖   **CON**: [...]
-        <optional-diagram/>
         </template>
 
         Hints:
 
         -   Give a short one-sentence <summary/> of the resolution
             approach plus *precise* and *ultra brief and concise*
-            resolution information. Try to keep the number of bullet
-            points (●) in the range of 1-4.
-
-        -   In case of a *complex resolution situation* only,
-            visualize it with an optional diagram <optional-diagram/>
-            by building a Mermaid specification <mermaid-spec/>
-            (e.g. `flowchart TB`, `stateDiagram-v2`, `sequenceDiagram`,
-            `classDiagram`, or `erDiagram`, depending on intent) and
-            dispatching the rendering to the `ase-meta-diagram`
-            sub-agent by calling the tool `Agent(name: "ase-meta-diagram",
-            description: "Diagram Rendering", subagent_type:
-            "ase:ase-meta-diagram", prompt: <mermaid-spec/>)`, reproducing
-            its returned fenced code block verbatim. For *current
-            vs. proposed* comparisons, render each side as a *separate*
-            `ase-meta-diagram` invocation and stack the rendered blocks
-            *vertically* (labels `**Before:**` / `**After:**`); never
-            side-by-side. Omit <optional-diagram/> entirely for simple
-            or purely local situations.
+            resolution information. Try to keep the number of bullet points
+            (`○ [...]`) in the range of 1-4.
 
     6.  Indicate end of reporting by showing the following <template/>:
 
@@ -289,28 +278,40 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <ase-tpl-foot title="APPROACHES"/>
         </template>
 
-5.  **Choose Problem Resolution Approach**:
+    7.  <if condition="<getopt-option-auto/> is not `true`">
+
+        You *MUST* use the custom `custom-dialog` and *NOT* the
+        `AskUserQuestion`-based `user-dialog` to let the *user
+        interactively choose* the preferred approach A<n/>.
+
+        Per approach A<n/>, use the option `A<n/>: <short-summary/>`
+        where <short-summary/> is an ultra brief summary of the approach
+        A<n/>. For your recommended approach, use
+        `A<n/>: ⚝ **RECOMMENDATION** ⚝: <short-summary/>` instead.
+
+        Now raise the user dialog:
+
+        <expand name="custom-dialog">
+            Select Approach: Select your preferred resolution approach to follow?
+            A<n/>: <short-summary/>
+            [...]
+        </expand>
 
-    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/>`
-        for the option (where <short-summary/> is an ultra brief summary
-        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>
+        <else>
 
-    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**:
+    </step>
+
+5.  <step id="STEP 5: Compose Problem Resolution Plan">
 
     1.  *Compose a plan* with code references, a precise description of the
         problem, the chosen resolution approach, a preview of the *unified
@@ -398,3 +399,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
             </else>
 
+    <step>
+
+</flow>
+

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

@@ -92,6 +92,6 @@ Resolve a previously analyzed issue and hand off to implementation:
 
 ##  SEE ALSO
 
-`ase-code-craft`, `ase-code-refactor`, `ase-code-analyze`,
-`ase-arch-analyze`, `ase-task-edit`, `ase-task-preflight`,
-`ase-task-implement`.
+[`ase-code-craft`](../ase-code-craft/help.md), [`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md),
+[`ase-arch-analyze`](../ase-arch-analyze/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md),
+[`ase-task-implement`](../ase-task-implement/help.md).

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

@@ -72,5 +72,5 @@ Distill a pasted block of text:
 
 ##  SEE ALSO
 
-`ase-meta-search`, `ase-docs-proofread`, `ase-meta-why`.
+[`ase-meta-search`](../ase-meta-search/help.md), [`ase-docs-proofread`](../ase-docs-proofread/help.md), [`ase-meta-why`](../ase-meta-why/help.md).
 

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

@@ -89,9 +89,12 @@ Analyze documents for spelling, punctuation, or grammar errors
 
 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` MCP server.
+    1.  *Mark this skill as the active edit-capable skill* so that the
+        ASE `pre-tool-use` hook auto-approves the subsequent `Edit`
+        invocations on *any* invocation path (slash command *or* `Skill`
+        tool). Call the `ase_config_set(key: "agent.skill", val:
+        "ase-docs-proofread", scope: "session:<ase-session-id/>")` tool
+        from the `ase` MCP server. Do not output anything in this substep.
 
     2.  Iterate over all problems:
 
@@ -151,9 +154,11 @@ Analyze documents for spelling, punctuation, or grammar errors
 
         4.  <if condition="<getopt-option-auto/> is not 'true'">
 
-            Ask the user how to proceed via an interactive user dialog:
+            Let the *user interactively choose* what to do as the next
+            step. For this you *MUST* use the custom `custom-dialog` and
+            not the `AskUserQuestion` based `user-dialog`:
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog">
                 CORRECTION: How would you like to proceed with this proposed correction?
                 ACCEPT: Apply the proposed correction.
                 REJECT: Skip this proposed correction.
@@ -173,9 +178,9 @@ Analyze documents for spelling, punctuation, or grammar errors
 
                 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/>.
+                will be auto-approved by the ASE `pre-tool-use` hook (which
+                tracks the active skill), so *no* interactive permission
+                prompt will appear. Then continue with the next <item/>.
 
                 </if>
 
@@ -202,8 +207,11 @@ Analyze documents for spelling, punctuation, or grammar errors
 
         </for>
 
-    3.  You *MUST* call the MCP tool `ase_config_delete(key: "agent.skill",
-        scope: "session:<ase-session-id/>")` of the `ase` MCP server.
+    3.  *Clear the active edit-capable skill marker* now that all `Edit`
+        invocations are done, so a later unrelated `Edit` is *not*
+        auto-approved. Call the `ase_config_delete(key: "agent.skill",
+        scope: "session:<ase-session-id/>")` tool from the `ase` MCP
+        server. Do not output anything in this substep.
 
     4.  You *MUST* *NOT* output any further additional explanations or
         summaries at the end of this skill processing, except for the

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

@@ -51,4 +51,4 @@ Proofread an entire documentation directory automatically:
 
 ##  SEE ALSO
 
-`ase-code-lint`, `ase-meta-changelog`.
+[`ase-code-lint`](../ase-code-lint/help.md), [`ase-meta-changelog`](../ase-meta-changelog/help.md).

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

@@ -78,7 +78,7 @@ Honor the following tenets throughout the brainstorming:
 
 1.  <step id="STEP 1: Restate Topic">
 
-    Restate the topic to be brainstormed by output the following <template/>:
+    Restate the topic to be brainstormed by outputting the following <template/>:
 
     <template>
     <ase-tpl-bullet-secondary/> **TOPIC**: <topic/>
@@ -121,9 +121,11 @@ Honor the following tenets throughout the brainstorming:
             question <question-M/>, and let the user select the
             <answer-M/> out of the candidate answers <answer-M-K/> (leave
             out the answer lines of those candidate answers you have
-            not determined)
+            not determined). For this you *MUST* use the custom
+            `custom-dialog` and *NOT* the `AskUserQuestion` based
+            "user-dialog":
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog">
                 <facet-M/>: <question-M/>
                 <answer-M-1/>: (first grounded candidate answer)
                 <answer-M-2/>: (second grounded candidate answer)