@rse/ase 0.9.10 → 0.9.11

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.9.10",
+    "version":                              "0.9.11",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.10",
+    "version":     "0.9.11",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.github/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.10",
+    "version":     "0.9.11",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.9.10",
+    "version":                              "0.9.11",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

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

@@ -101,14 +101,19 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-arch-analyze">
 Review Software Architecture
 </skill>
 
+<expand name="getopt" arg1="ase-arch-analyze">
+    $ARGUMENTS
+</expand>
+
 <objective>
 With the mindset of an *expert-level software architect*,
-*review* the *software architecture* of $ARGUMENTS, and its directly
+*review* the *software architecture* of <getopt-arguments/>, and its directly
 related source code, for *potential problems* across component
 boundaries, structural organization, architecture principles,
 interface quality, quality attributes, and architecture governance.

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

@@ -52,8 +52,8 @@ for the technology stack to *provide* the *needed functionality*
             Functionality: Which functionality should the components provide?
             <answer-1/>: (grounded candidate functionality 1)
             <answer-2/>: (grounded candidate functionality 2)
-            <answer-3/>: (grounded candidate functionality 2)
-            <answer-4/>: (grounded candidate functionality 3)
+            <answer-3/>: (grounded candidate functionality 3)
+            <answer-4/>: (grounded candidate functionality 4)
         </expand>
 
         Then use the <result/> and its corresponding grounded candidate

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

@@ -40,7 +40,8 @@ problems in *performance* and *efficiency*, or problems in *security*.
 
     <if condition="<getopt-option-performance/> is equal `true` and <getopt-option-security/> is equal `true`">
 
-    Only output the following <template/> and then *STOP* immediately:
+    Only output the following <template/> and then *STOP* the entire flow
+    (do not perform any further steps):
 
     <template>
     ⧉ **ASE**: ✪ skill: **ase-code-analyze**, ▶ ERROR: options `--performance` and `--security` are mutually exclusive
@@ -146,10 +147,12 @@ problems in *performance* and *efficiency*, or problems in *security*.
     than or equal to `rank(<getopt-option-severity/>)`; *silently drop*
     all other problems (they are neither reported nor persisted). With
     the default floor `LOW`, all problems are kept. `ACCEPTED` problems
-    are *never* dropped. Then renumber the surviving problems
-    contiguously as `P<n/>` with <n/> = 1, 2, ... in the original
-    ordering. If *all* problems are dropped, skip the per-problem report
-    but still emit the final hint <template/> below.
+    are *never* dropped.
+
+    Then renumber the surviving problems contiguously as `P<n/>` with
+    <n/> = 1, 2, ... in the original ordering. If *all* problems are
+    dropped, skip the per-problem report but still emit the final hint
+    <template/> below.
 
     In this STEP 3, for *EVERY* surviving problem, immediately report
     it with the following output <template/>, based on concise bullet
@@ -209,6 +212,10 @@ problems in *performance* and *efficiency*, or problems in *security*.
         justified trade-off that should remain on record but is never
         dropped by the severity floor (see STEP 3).
 
+    -   For <title/> ultra-compress the <description/> to a concise,
+        short, single sentence. Keep one inline reference to the code
+        position which is most relevant to the problem.
+
     -   <if condition="<getopt-option-performance/> is equal `true`">
         In <evidence/>, ground the finding by citing either the inferred
         *Big-O* time/space complexity (e.g. `O(n²)` reducible to `O(n)`)

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

@@ -343,11 +343,14 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             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).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>

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

@@ -14,13 +14,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-code-explain">
 Explain Source Code
 </skill>
 
+<expand name="getopt" arg1="ase-code-explain">
+    $ARGUMENTS
+</expand>
+
 <objective>
-*Analyze* the source code of $ARGUMENTS, and its directly related source
+*Analyze* the source code of <getopt-arguments/>, and its directly related source
 code and *explain* it in a *brief*, *standardized*, and *concise* way.
 </objective>
 

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

@@ -18,13 +18,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-code-insight">
 Project Insight
 </skill>
 
+<expand name="getopt" arg1="ase-code-insight">
+    $ARGUMENTS
+</expand>
+
 <objective>
-Give *insights* into the project through the source code of $ARGUMENTS.
+Give *insights* into the project through the source code of <getopt-arguments/>.
 </objective>
 
 <flow>

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

@@ -248,9 +248,15 @@ related to a set of code quality aspects.
             -   <if condition="<result/> starts with 'OTHER'">
                 Generate a *new* proposal for the *same* <item/>
                 (incorporating the user's free-text hint from <result/> if
-                provided via the "OTHER" prefix) and loop back to substep 2
-                of this iteration. There is *no* cap on refinement rounds -
-                keep refining until the user picks `ACCEPT` or `REJECT`.
+                provided via the "OTHER" prefix). *Reassign* <description/>
+                and <change-set/> to reflect this refined proposal (each
+                change-hunk's `old_text` stays anchored to the existing
+                text at its `file`:`line`; `new_text` carries the
+                refinement) so that the substep 2/3 rebuild renders the new
+                <diff/> and any `Edit` applies the new proposal rather than
+                the original. Then loop back to substep 2 of this iteration.
+                There is *no* cap on refinement rounds - keep refining until
+                the user picks `ACCEPT` or `REJECT`.
                 </if>
 
             -   <if condition="

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

@@ -332,11 +332,14 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             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).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>

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

@@ -60,14 +60,15 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     1.  If <problem/> matches the regexp `^[PT]\d+$` (i.e. a bare issue
         identifier like `P1`, `P2`, `T1`, `T2`, ...),
         set <problem-id><problem/></problem-id> and
-        <ase-task-id><problem/></ase-task-id>, call the `ase_task_id(id:
-        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the
-        `ase` MCP server to implicitly switch the task, and then
-        call the `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of
+        <ase-task-id><problem/></ase-task-id>, then call the
+        `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of
         the `ase` MCP server to retrieve the previously persisted
         problem description. If the returned `text` is non-empty, set
-        <problem><text/></problem>, otherwise complain to the user that
-        no analyzer result exists for <problem-id/> and stop processing.
+        <problem><text/></problem> 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, otherwise
+        complain to the user that no analyzer result exists for
+        <problem-id/> and stop processing.
 
     2.  <if condition="
             <problem/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
@@ -389,11 +390,14 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             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).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>

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

@@ -188,9 +188,15 @@ 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 *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`.
+                after the "OTHER:" prefix. *Reassign* <description/>,
+                <old-text/>, and <new-text/> to reflect this refined
+                proposal (<old-text/> stays anchored to the existing text
+                at <file/>:<line/>; <new-text/> and <description/> carry the
+                refinement) so the subsequent rendering and any `Edit` use
+                the new proposal rather than the original. Then *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

@@ -129,10 +129,9 @@ Honor the following tenets throughout the brainstorming:
 
             <expand name="custom-dialog" arg1="--other">
                 <facet-M/>: <question-M/>
-                <answer-M-1/>: (first grounded candidate answer)
-                <answer-M-2/>: (second grounded candidate answer)
-                <answer-M-3/>: (third grounded candidate answer)
-                <answer-M-4/>: (fourth grounded candidate answer)
+                <answer-M-1/>: (grounded candidate answer 1)
+                <answer-M-2/>: (grounded candidate answer 2)
+                [...]
             </expand>
 
         4.  Dispatch on the dialog <result/>:

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

@@ -16,11 +16,16 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-changelog">
 Update ChangeLog Entries
 </skill>
 
+<expand name="getopt" arg1="ase-meta-changelog">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Help to complete, consolidate and sort *ChangeLog* entries of the most
 recent *ChangeLog* section, based on underlying *Git* commits and staged
@@ -81,11 +86,17 @@ Processing
     the Git *commits* plus the currently already staged changes in the Git
     *index*, but *ignore* the Git *stash* and still unstaged changes.
 
-    For finding the corresponding Git *commits*, use the `N.M.K` from the
-    *second* level-2 header in the *ChangeLog* file as the corresponding
-    Git tag and then check all Git commits between `HEAD` and this tag
-    with the command `git log N.M.K..HEAD --numstat --pretty=format:'%h:
-    %s'`.
+    For finding the corresponding Git *commits*, first determine the
+    correct baseline Git tag. Take the `N.M.K` from the *first* (most
+    recent) level-2 header in the *ChangeLog* file and check whether a
+    corresponding Git tag already exists with the command `git tag --list
+    N.M.K`. If this command produces *no* output, the first section is
+    still in-progress/untagged, so use the `N.M.K` from the *second*
+    level-2 header as the baseline tag instead. If this command *does*
+    produce output, the first section is already released/tagged, so use
+    the `N.M.K` from the *first* level-2 header as the baseline tag. Then
+    check all Git commits between `HEAD` and this baseline tag with the
+    command `git log N.M.K..HEAD --numstat --pretty=format:'%h: %s'`.
 
     For finding the corresponding staged Git *changes* in the Git
     *index*, use the command `git diff --cached --numstat`, but silently

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

@@ -14,13 +14,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-chat">
 Query Foreign LLM for Chat
 </skill>
 
+<expand name="getopt" arg1="ase-meta-chat">
+    $ARGUMENTS
+</expand>
+
 <objective>
-Query foreign LLM for: <query>$ARGUMENTS</query>
+Query foreign LLM for: <query><getopt-arguments/></query>
 </objective>
 
 1.  You *MUST* *NOT* output anything in this step.

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

@@ -12,11 +12,16 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-commit">
 Git Commit
 </skill>
 
+<expand name="getopt" arg1="ase-meta-commit">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Help to *craft* a *concise commit message* for the
 currently staged Git changes.

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

@@ -120,7 +120,11 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
     Anti-Theses or Counter-Arguments until you EITHER have found at
     least <count/> Anti-Theses or Counter-Arguments with at least a rank
     of 7 OR you have already checked a total of <count/> x 5 Anti-Theses
-    or Counter-Arguments.
+    or Counter-Arguments. If the second condition is reached first and
+    fewer than <count/> Anti-Theses or Counter-Arguments reached a rank
+    of at least 7, nevertheless surface the <count/> highest-ranked ones
+    found so far, because <count/> is the *minimum* number of
+    Anti-Theses to surface.
 
     Then, for the top-<count/> highest-ranked Anti-Theses or
     Counter-Arguments, sort them by their rank from highest to lowest,

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 changed per feature in format
+            is the total number of lines changed per intent group 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:

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

@@ -13,11 +13,16 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-evaluate">
 Evaluate Alternatives
 </skill>
 
+<expand name="getopt" arg1="ase-meta-evaluate">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *Evaluate* *alternatives* through a weighted
 multi-*criteria* decision matrix.
@@ -25,7 +30,7 @@ multi-*criteria* decision matrix.
 
 <flow>
 1.  <step id="STEP 1: Determine Reason">
-    -   From the <request>$ARGUMENTS</request>, try to derive the overall
+    -   From the <request><getopt-arguments/></request>, try to derive the overall
         reason <reason/> for the evaluation. If no such reason can be
         derived, assume <reason>generic comparison</reason>.
 
@@ -38,7 +43,7 @@ multi-*criteria* decision matrix.
     </step>
 
 2.  <step id="STEP 2: Determine Alternatives">
-    -   From the <request>$ARGUMENTS</request> derive the two or more
+    -   From the <request><getopt-arguments/></request> derive the two or more
         alternatives <alternative-K/> (K=1-N) the user wants to be
         evaluated. Do not output anything.
 
@@ -105,7 +110,7 @@ multi-*criteria* decision matrix.
     </step>
 
 3.  <step id="STEP 3: Derive Criteria">
-    -   From the <request>$ARGUMENTS</request>, try to derive the criteria
+    -   From the <request><getopt-arguments/></request>, try to derive the criteria
         <criteria-L/> (L=1-M) for the evaluation. Do not output anything.
 
     -   For each criterion <criteria-L/> (L=1-M), decide on its <weight-L/>
@@ -222,23 +227,26 @@ multi-*criteria* decision matrix.
         ⚠ *Please give some hints on the criteria to ensure a single best alternative!*
         </template>
 
-    -   Otherwise, if <percentage/> is less than 0.10, stop the flow after
-        you output just the following <template/> and do not output anything
-        else:
+    -   Otherwise, if <rating-K/> is less than zero (i.e. all alternatives
+        rate negatively and the "best" is merely the least-bad), stop the
+        flow after you output just the following <template/> and do not
+        output anything else. This all-negative check is evaluated *before*
+        the small-distance check below, so that an all-negative alternative
+        set with a small winning gap surfaces the all-negative warning rather
+        than being masked by the small-distance branch:
 
         <template>
         <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
-        ⚠ *ATTENTION: small distance to second best alternative!*
+        ⚠ *ATTENTION: all alternatives rate negatively; this is the least-bad choice, not a strong winner!*
         </template>
 
-    -   Otherwise, if <rating-K/> is less than zero (i.e. all alternatives
-        rate negatively and the "best" is merely the least-bad), stop the
-        flow after you output just the following <template/> and do not
-        output anything else:
+    -   Otherwise, if <percentage/> is less than 0.10, stop the flow after
+        you output just the following <template/> and do not output anything
+        else:
 
         <template>
         <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
-        ⚠ *ATTENTION: all alternatives rate negatively; this is the least-bad choice, not a strong winner!*
+        ⚠ *ATTENTION: small distance to second best alternative!*
         </template>
 
     -   Otherwise (<percentage/> is greater than or equal to 0.10), output

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

@@ -15,18 +15,23 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-persona">
 Persona Configuration
 </skill>
 
+<expand name="getopt" arg1="ase-meta-persona">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *Configure* the *persona style* of the agent to adjust the communication
 style and token usage intensity.
 </objective>
 
 1.  Determine request:
-    <request>$ARGUMENTS</request>
+    <request><getopt-arguments/></request>
     Do not output anything.
 
 2.  <if condition="<request/> is empty">

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

@@ -134,9 +134,17 @@ by querying *multiple* AIs for an *optimal consensus*.
 
 4.  <step id="STEP 4: Determine Consensus Rating">
 
-    Determine, on a Likert scale of 0..<n/>, the amount of the overall
-    consensus <c/> of all the responses. The <n/> is the *total number of
-    responders* (yourself plus all available foreign AIs above).
+    First, count the number of *available foreign AIs* (those queried in
+    STEP 2 which did *not* return an `ERROR:` response). If this count is
+    *zero* -- i.e., every foreign AI errored out or none were reachable
+    and only yourself (Anthropic Claude) remains -- a quorum is *not*
+    possible. In this case, set <c></c> and <n></n> to empty and instead
+    set <disagreement/> to `(no quorum: no foreign AIs were available)`,
+    then skip the rest of this step.
+
+    Otherwise, determine, on a Likert scale of 0..<n/>, the amount of the
+    overall consensus <c/> of all the responses. The <n/> is the *total
+    number of responders* (yourself plus all available foreign AIs above).
     If all responses disagree, the consensus <c/> is zero.
     If all responses agree, <c/> is <n/>.
 
@@ -165,6 +173,10 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     **CONSENSUS RATE**: **<c/>/<n/>** <disagreement/>
 
+    When a quorum was *not* possible (see STEP 4), render this line
+    instead as just `**CONSENSUS RATE**: *n/a* <disagreement/>` (omitting
+    the `<c/>/<n/>` fraction), as a single AI cannot form a consensus.
+
     &#x25CB; **Anthropic Claude**:
     - [...]
     - [...]

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

@@ -142,7 +142,11 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
     more Pro-Theses or Supporting-Arguments until you EITHER have found
     at least <count/> Pro-Theses or Supporting-Arguments with at least a
     rank of 7 OR you have already checked a total of <count/> x 5
-    Pro-Theses or Supporting-Arguments.
+    Pro-Theses or Supporting-Arguments. If the second condition is
+    reached first and fewer than <count/> Pro-Theses or
+    Supporting-Arguments reached a rank of at least 7, nevertheless
+    surface the <count/> highest-ranked ones found so far, because
+    <count/> is the *minimum* number of Pro-Theses to surface.
 
     Then, for the top-<count/> highest-ranked Pro-Theses or
     Supporting-Arguments, sort them by their rank from highest to lowest,

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

@@ -12,11 +12,16 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-task-delete">
 Delete a Task Plan
 </skill>
 
+<expand name="getopt" arg1="ase-task-delete">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *Delete* the task plan.
 </objective>
@@ -32,7 +37,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 1.  **Determine Task:**
 
-    1.  Set <id>$ARGUMENTS</id> initially, with any leading and trailing
+    1.  Set <id><getopt-arguments/></id> initially, with any leading and trailing
         whitespace stripped.
         Inherit the always existing <ase-task-id/> from the current context.
         Inherit the always existing <ase-session-id/> from the current context.

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

@@ -175,14 +175,32 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
             2.  Check the code base and your world knowledge and
                 use this information to find *up to three* grounded
-                alternative answers <answer-N-K/> (K={2,3,4}).
-
-            3.  Use an interactive user dialog
-                with header <aspect-N/> and question <question-N/>, and
-                let the user select the <answer-N/> out of <answer-N-K/>
-                (K={1..4}). In this dialog, mark the <answer-N-1/> by
-                appending ` ⚝ **CURRENT PLAN** ⚝` to its option name (not the
-                description).
+                alternative answers <answer-N-K/> (K={2,3,4}), so there
+                are between two and four answer options in total.
+
+            3.  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 select the <answer-N/> out of the answer
+                alternatives <answer-N-K/> by raising a question with the
+                following custom dialog, where per alternative <answer-N-K/>
+                you determine a brief label <answer-N-K-label/> and a
+                description <answer-N-K-description/>, and you mark the
+                <answer-N-1/> by prefixing its description with
+                `⚝ **CURRENT PLAN** ⚝ `. Emit only the answer lines for the
+                alternatives <answer-N-K/> you actually determined in the
+                previous step (between two and four lines in total):
+
+                <expand name="custom-dialog" arg1="--other">
+                    <aspect-N/>: <question-N/>
+                    <answer-N-1-label/>: ⚝ **CURRENT PLAN** ⚝ <answer-N-1-description/>
+                    <answer-N-K-label/>: <answer-N-K-description/>
+                    [...]
+                </expand>
+
+                Set <answer-N/> to the selected <result/>.
 
             4.  Output the following <template/>:
 
@@ -199,7 +217,10 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     4.  Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
         `ase` MCP server and use the `text` field of its response for
-        <timestamp-modified/> information. Then insert the current
+        <timestamp-modified/> information. If <timestamp-created/> is
+        still unset (because the previous <plan/> had no `Created:`
+        line), set <timestamp-created><timestamp-modified/></timestamp-created>
+        (fall back to the modified timestamp). Then insert the current
         <ase-task-id/>, previous <timestamp-created/>, and refreshed
         <timestamp-modified/> information and calculate the number of
         words <words/> of <plan/>.

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

@@ -12,17 +12,23 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-task-id">
 Configure Task Id
 </skill>
 
+<expand name="getopt" arg1="ase-task-id">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *Get* or *set* the unique *task id* of the current session.
 </objective>
 
 1.  Determine request:
-    <request>$ARGUMENTS</request>
+    <request><getopt-arguments/></request>
+    Inherit the always existing <ase-session-id/> from the current context.
 
 2.  <if condition="<request/> is NOT empty AND <request/> does NOT match the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`">
     Only output the following <template/> and then immediately
@@ -35,8 +41,9 @@ Configure Task Id
 
 3.  <if condition="<request/> is empty">
     -   Call the `ase_task_id(session: "<ase-session-id/>")`
-        tool from the `ase` MCP server and set
-        <ase-task-id/> to its `text` output.
+        tool from the `ase` MCP server and set <text/> to its
+        `text` output. Check the response as mandated above; only
+        on a clean response set <ase-task-id><text/></ase-task-id>.
 
     -   Output:
         <template>

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

@@ -119,10 +119,10 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Set <instruction><text/></instruction> (set instruction to extracted text).
         </if>
 
-    5.  <elseif condition="<content/> contains '-   **WHY**: <text/>' and <instruction/> is NOT empty">
+    5.  <if condition="<content/> contains '-   **WHY**: <text/>' and <instruction/> is NOT empty">
         Set <instruction><instruction/>, BECAUSE <text/></instruction>
         (append extracted text to instruction).
-        </elseif>
+        </if>
 
     6.  <if condition="<content/> contains 'Created:  <text/>'">
         Set <timestamp-created><text/></timestamp-created> (set

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

@@ -12,11 +12,16 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-task-rename">
 Rename a Task Plan
 </skill>
 
+<expand name="getopt" arg1="ase-task-rename">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *Rename* the task plan.
 </objective>
@@ -32,7 +37,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 1.  **Determine Task:**
 
-    1.  Parse <arguments>$ARGUMENTS</arguments> into a whitespace-separated
+    1.  Parse <arguments><getopt-arguments/></arguments> into a whitespace-separated
         list of tokens. Inherit the always existing <ase-task-id/> and
         <ase-session-id/> from the current context. Do not output anything.
 
@@ -57,6 +62,15 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </template>
         </if>
 
+    5.  <if condition="<old/> does NOT match the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$` OR <new/> does NOT match the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`">
+        Only output the following <template/> and then immediately
+        *STOP* processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ☻ skill: **ase-task-rename**, ▶ ERROR: invalid task id (expected `^[a-zA-Z][a-zA-Z0-9_-]*$`)
+        </template>
+        </if>
+
 2.  **Perform Operation**:
 
     1.  Call the `ase_task_rename(old: "<old/>", new: "<new/>")` tool of the