@rse/ase 0.9.8 → 0.9.10

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
@@ -251,37 +259,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ●   **APPROACH A<n/>**<annotation/>: **<summary/>**
         ○   [...]
-        ○   [...]
-        ○   [...]
-        ⊕   **PRO**: [...]
-        ⊖   **CON**: [...]
-        <optional-diagram/>
+        ⊕   *PRO*: [...]
+        ⊖   *CON*: [...]
         </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,41 @@ 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`">
+
+        In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+        tool! Instead, you *MUST* just show a custom output, let the
+        user enter input, and then you set the result accordingly.
+
+        Let the user choose the preferred approach A<n/> by raising
+        a question with the following custom dialog, where per
+        approach A<n/>, you determine an ultra brief summary
+        <short-summary/> and then use the answer option `A<n/>:
+        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        recommended approach plus zero or more answer options `A<n/>:
+        <short-summary/>` for all other approaches:
+
+        <expand name="custom-dialog" arg1="--no-other">
+            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 +400,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:
 
@@ -126,7 +129,7 @@ Analyze documents for spelling, punctuation, or grammar errors
             ```diff
             --- <file/> (original)
             +++ <file/> (corrected)
-            @@ -<old-start/>,<n/> +<new-start/>,<m/> @@
+            @@ -<old-start/>,<old-count/> +<new-start/>,<new-count/> @@
              <context-before/>
             -<old-text/>
             +<new-text/>
@@ -140,10 +143,10 @@ Analyze documents for spelling, punctuation, or grammar errors
                 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 <old-count/> 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 <new-count/> is the total number of new-side hunk lines, i.e.,
                 the number of lines in <context-before/>, <new-text/>, and
                 <context-after/> combined.
 
@@ -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:
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog" arg1="--other">
                 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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-brainstorm
-argument-hint: "[--help|-h] [--max-clarify|-c=3] [--min-ideas|-i=12] [--min-rank|-r=7] [--max-shortlist|-s=4] <topic>"
+argument-hint: "[--help|-h] [--max-clarify|-c <num>] [--min-ideas|-i <num>] [--min-rank|-r <num>] [--max-shortlist|-s <num>] <topic>"
 description: >
     Collaboratively brainstorm a topic by diverging on ideas, converging
     through clustering and scoring, and distilling a shortlist with
@@ -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,13 @@ 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).
 
-            <expand name="user-dialog">
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
+
+            <expand name="custom-dialog" arg1="--other">
                 <facet-M/>: <question-M/>
                 <answer-M-1/>: (first grounded candidate answer)
                 <answer-M-2/>: (second grounded candidate answer)
@@ -212,15 +216,30 @@ Honor the following tenets throughout the brainstorming:
 
         <template>
         <ase-tpl-bullet-secondary/> **IDEA CLUSTER <C/>/<c/>**: <cluster-C/> - <cluster-summary-C/>,
-        **IDEAS**: <N/>, <M/>[, ...]
+        **IDEAS**: <idea-index-C/>
         </template>
 
+        Here, <idea-index-C/> is the comma-separated list of the indices
+        <N/> of those retained ideas <idea-N/> that belong to cluster
+        <cluster-C/> (e.g. `2, 5, 9`).
+
     2.  *Score*: for each retained idea <idea-N/> in the clusters, rank its *fit* against the
         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 <getopt-option-min-rank/>.
 
+        If *no* idea meets the <getopt-option-min-rank/> floor, the floor
+        filter would empty the set and leave the downstream steps without
+        any options. In this case, *disregard* the floor and instead keep
+        the up-to-<getopt-option-max-shortlist/> highest-ranked ideas, and
+        output the following <template/> to flag that even the strongest
+        ideas fall below the bar:
+
+        <template>
+        <ase-tpl-bullet-signal/> **NOTICE**: no idea reached the minimum rank of <getopt-option-min-rank/>/10 - shortlisting the highest-ranked ideas regardless.
+        </template>
+
     3.  From the scored ideas <idea-N/>, distill a *shortlist* of the top
         <getopt-option-max-shortlist/> options, sorted by rank from highest to lowest.
 

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

@@ -84,4 +84,4 @@ and a tighter shortlist:
 
 ##  SEE ALSO
 
-`ase-meta-evaluate`, `ase-meta-quorum`, `ase-meta-diaboli`
+[`ase-meta-evaluate`](../ase-meta-evaluate/help.md), [`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-meta-diaboli`](../ase-meta-diaboli/help.md)

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

@@ -30,4 +30,4 @@ Update the most recent ChangeLog section:
 
 ##  SEE ALSO
 
-`ase-meta-commit`, `ase-docs-proofread`.
+[`ase-meta-commit`](../ase-meta-commit/help.md), [`ase-docs-proofread`](../ase-docs-proofread/help.md).

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

@@ -42,4 +42,4 @@ Ask Gemini for a brief comparison:
 
 ##  SEE ALSO
 
-`ase-meta-quorum`, `ase-meta-search`.
+[`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-meta-search`](../ase-meta-search/help.md).

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

@@ -28,4 +28,4 @@ Craft a commit message for the currently staged changes:
 
 ##  SEE ALSO
 
-`ase-meta-changelog`.
+[`ase-meta-changelog`](../ase-meta-changelog/help.md).

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

@@ -2,7 +2,7 @@
 name: ase-meta-diaboli
 argument-hint: "[--help|-h] [--count|-c <count>] <thesis>"
 description: >
-    Challenge a thesis by playing "Devil’s Advocate" (latin: "Advocatus
+    Challenge a thesis by playing "Devil’s Advocate" (Latin: "Advocatus
     Diaboli"). Use when the user wants a thesis or statement
     relentlessly challenged or criticised.
 user-invocable: true
@@ -25,7 +25,7 @@ effort: xhigh
 </expand>
 
 <objective>
-    Play "Devil’s Advocate" (latin: "Advocatus Diaboli") by relentlessly
+    Play "Devil’s Advocate" (Latin: "Advocatus Diaboli") by relentlessly
     challenging or criticising the thesis: <thesis><getopt-arguments/></thesis>
 </objective>
 
@@ -48,7 +48,7 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
 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
+    (Latin: *Advocatus Diaboli*) by relentlessly challenging or
     criticising it with the help of the following tenets:
 
     -   **Steelmanning**:
@@ -88,7 +88,7 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
 
     -   **Push the Logic to its Conclusion**:
         Ask "If we accept this, then what?" and apply "Reduction to
-        Absurdity" (latin: "Reductio Ad Absurdum"), because this disproves
+        Absurdity" (Latin: "Reductio Ad Absurdum"), because this disproves
         the thesis by showing that accepting it leads to a logically
         absurd, contradictory, or impossible conclusion.
 

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

@@ -73,6 +73,6 @@ Surface at least fifteen anti-theses:
 
 ##  SEE ALSO
 
-`ase-meta-why`, `ase-meta-evaluate`, `ase-meta-quorum`,
-`ase-meta-persona`.
+[`ase-meta-why`](../ase-meta-why/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md), [`ase-meta-quorum`](../ase-meta-quorum/help.md),
+[`ase-meta-persona`](../ase-meta-persona/help.md).
 

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

@@ -109,7 +109,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         3.  For each discovered *intent group*, emit the following row
             <template/>, where <intent/> is the intent label, <changes/>
-            is the total number of lines changes per feature in format
+            is the total number of lines changed per feature in format
             `+N/-M`, <files/> is the list of affected file references,
             and <description/> is a *brief* one-to-two-sentence
             narrative of what changed and why:
@@ -169,7 +169,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Judge overall *coherence* from the flagged hunks: the diff
         is `COHERENT` when there are *no* `SCOPE-CREEP` and *no*
         `STRAY-DEBUG` deviations, otherwise it is `INCOHERENT`. Store
-        the result is <verdict/>.
+        the result in <verdict/>.
 
     4.  Emit the following header <template/>:
 

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

@@ -101,4 +101,4 @@ Summarize the staged changes and append a blast-radius map:
 
 ##  SEE ALSO
 
-`ase-meta-commit`, `ase-meta-changelog`, `ase-arch-analyze`.
+[`ase-meta-commit`](../ase-meta-commit/help.md), [`ase-meta-changelog`](../ase-meta-changelog/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).

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

@@ -48,5 +48,5 @@ Evaluate database options with hinted criteria:
 
 ##  SEE ALSO
 
-`ase-meta-quorum`, `ase-meta-search`, `ase-arch-discover`,
-`ase-meta-why`.
+[`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-arch-discover`](../ase-arch-discover/help.md),
+[`ase-meta-why`](../ase-meta-why/help.md).

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

@@ -47,4 +47,4 @@ Switch to the telegrapher persona:
 
 ##  SEE ALSO
 
-`ase-task-id`.
+[`ase-task-id`](../ase-task-id/help.md).

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

@@ -56,4 +56,4 @@ Ask only a subset of the foreign models:
 
 ##  SEE ALSO
 
-`ase-meta-chat`, `ase-meta-search`, `ase-meta-evaluate`.
+[`ase-meta-chat`](../ase-meta-chat/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md).

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

@@ -17,7 +17,6 @@ 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">

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

@@ -84,5 +84,5 @@ Review the staged changes, reporting only `MEDIUM` and `HIGH` findings:
 
 ##  SEE ALSO
 
-`ase-meta-diff`, `ase-meta-commit`, `ase-code-lint`, `ase-code-analyze`,
-`ase-meta-diaboli`.
+[`ase-meta-diff`](../ase-meta-diff/help.md), [`ase-meta-commit`](../ase-meta-commit/help.md), [`ase-code-lint`](../ase-code-lint/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md),
+[`ase-meta-diaboli`](../ase-meta-diaboli/help.md).

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

@@ -88,12 +88,20 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
         from the MCP server `search-exa`.
     </expand>
 
-    If the `websearch` backend is *selected*:
+    If the `websearch` backend is *selected* and the tool
+    `WebSearch` is available:
 
     <expand name="agent" arg1="websearch">
         Call the tool `WebSearch(query: "<query/>")`.
     </expand>
 
+    If the `websearch` backend is *selected* and the tool `web_search` is
+    available and the tool `WebSearch` is not available:
+
+    <expand name="agent" arg1="websearch">
+        Call the tool `web_search(query: "<query/>")`.
+    </expand>
+
     </step>
 
 2.  <step id="STEP 2: Consolidate Search Answers">

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

@@ -48,4 +48,4 @@ Search the Web using only the Brave and Exa backends:
 
 ##  SEE ALSO
 
-`ase-meta-chat`, `ase-meta-quorum`, `ase-arch-discover`.
+[`ase-meta-chat`](../ase-meta-chat/help.md), [`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-arch-discover`](../ase-arch-discover/help.md).

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

@@ -88,5 +88,5 @@ Strengthen across five iterative rounds:
 
 ##  SEE ALSO
 
-`ase-meta-diaboli`, `ase-meta-why`, `ase-meta-evaluate`,
-`ase-meta-quorum`.
+[`ase-meta-diaboli`](../ase-meta-diaboli/help.md), [`ase-meta-why`](../ase-meta-why/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md),
+[`ase-meta-quorum`](../ase-meta-quorum/help.md).

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

@@ -123,10 +123,12 @@ addressing surface-level symptoms.
 
             Then choose, among the <answer-k/>, the *most causally-significant*
             candidate -- the one most likely to lead to the true root-cause --
-            and *justify* the choice in one line (state explicitly *why* it
-            beats the other candidates, e.g. it alone also explains the timing,
-            scope, or magnitude of the level's fact). A bare "most significant"
-            is *not* sufficient; if no candidate clearly dominates, say so.
+            set <chosen-k/> to its candidate index (the <k/> of the chosen
+            <answer-k/>), and *justify* the choice in one line (state explicitly
+            *why* it beats the other candidates, e.g. it alone also explains the
+            timing, scope, or magnitude of the level's fact). A bare "most
+            significant" is *not* sufficient; if no candidate clearly dominates,
+            say so.
 
             <template>
             <ase-tpl-bullet-secondary/> **WHY <n/> → chosen <n/>.<chosen-k/>**: <justification/>

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

@@ -77,4 +77,4 @@ committing early to the wrong root-cause:
 
 ##  SEE ALSO
 
-`ase-code-analyze`, `ase-code-resolve`, `ase-arch-analyze`.
+[`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).

package/plugin/skills/ase-task-condense/SKILL.md

@@ -203,9 +203,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
                 </template>
 
         -   If <getopt-option-next/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next step.
 
-            <expand name="user-dialog">
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
+
+            <expand name="custom-dialog" arg1="--no-other">
                 Next Step: How would you like to proceed with the plan?
                 DONE: Stop processing.
                 EDIT: Hand off plan to editing.

package/plugin/skills/ase-task-condense/help.md

@@ -73,5 +73,5 @@ Condense a specific task and hand off to editing:
 
 ##  SEE ALSO
 
-`ase-task-edit`, `ase-task-reboot`, `ase-task-view`,
-`ase-task-rename`, `ase-task-delete`.
+[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md), [`ase-task-view`](../ase-task-view/help.md),
+[`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).

package/plugin/skills/ase-task-delete/help.md

@@ -39,5 +39,5 @@ Delete a specific task plan:
 
 ##  SEE ALSO
 
-`ase-task-edit`, `ase-task-list`, `ase-task-view`,
-`ase-task-rename`, `ase-task-reboot`.
+[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-list`](../ase-task-list/help.md), [`ase-task-view`](../ase-task-view/help.md),
+[`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md).

package/plugin/skills/ase-task-edit/SKILL.md

@@ -226,9 +226,12 @@ Set <content-dirty>true</content-dirty>.
             Set <result><getopt-option-plan/></result>.
 
         -   If <getopt-option-plan/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next step.
 
-            <expand name="user-dialog">
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
+
+            <expand name="custom-dialog" arg1="--other">
                 Previous Plan: Should the previous plan content be overwritten, refined, or preserved?
                 OVERWRITE: Continue operation, overwrite previous plan.
                 REFINE: Continue operation, refine previous plan.
@@ -374,9 +377,12 @@ Set <content-dirty>true</content-dirty>.
                 </template>
 
         -   If <getopt-option-next/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next step.
 
-            <expand name="user-dialog">
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
+
+            <expand name="custom-dialog" arg1="--other">
                 Next Step: How would you like to proceed with the plan?
                 DONE: Mark plan finalized, exit planning loop.
                 GRILL: Hand off plan to grilling.

package/plugin/skills/ase-task-edit/help.md

@@ -82,5 +82,5 @@ Further refine the task under id `hello`:
 
 ##  SEE ALSO
 
-`ase-task-reboot`, `ase-task-preflight`, `ase-task-implement`,
-`ase-task-view`, `ase-task-list`, `ase-task-rename`, `ase-task-delete`.
+[`ase-task-reboot`](../ase-task-reboot/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md),
+[`ase-task-view`](../ase-task-view/help.md), [`ase-task-list`](../ase-task-list/help.md), [`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).

package/plugin/skills/ase-task-grill/SKILL.md

@@ -239,9 +239,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
                 </template>
 
         -   If <getopt-option-next/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next step.
 
-            <expand name="user-dialog">
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
+
+            <expand name="custom-dialog" arg1="--no-other">
                 Next Step: How would you like to proceed with the plan?
                 DONE: Stop processing.
                 EDIT: Hand off plan to editing.

package/plugin/skills/ase-task-grill/help.md

@@ -70,6 +70,6 @@ Grill the current task plan and then hand off to editing:
 
 ##  SEE ALSO
 
-`ase-task-edit`, `ase-task-reboot`, `ase-task-preflight`,
-`ase-task-implement`, `ase-task-view`, `ase-task-list`,
-`ase-task-rename`, `ase-task-delete`.
+[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md),
+[`ase-task-implement`](../ase-task-implement/help.md), [`ase-task-view`](../ase-task-view/help.md), [`ase-task-list`](../ase-task-list/help.md),
+[`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).