@rse/ase 0.9.44 → 0.9.46

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

@@ -0,0 +1,78 @@
+
+##  NAME
+
+`ase-meta-proximity` - Determine the Conceptual Proximity of a Topic
+
+##  SYNOPSIS
+
+`ase-meta-proximity`
+    [`--help`|`-h`]
+    [`--ground`|`-g`]
+    [`--loop`|`-l`]
+    *topic*
+
+##  DESCRIPTION
+
+The `ase-meta-proximity` skill determines the *conceptual proximity* of
+the supplied *topic* along three dimensions and reports the neighboring
+topics grouped into three labeled sections: *PARENT* (the single broader
+topic that *topic* specializes), *SIBLINGS* (the four most relevant
+topics on the same level, sharing the same parent), and *CHILDREN* (the
+four most relevant narrower topics that specialize *topic*).
+
+By default the proximity is derived from model knowledge only. With the
+`--ground`/`-g` option, the skill first searches the Internet/Web for
+facts about the topic via the `ase-meta-search` skill (dispatched in a
+sub-agent, querying all available search backends) and grounds the
+determination in the found facts.
+
+Without the `--loop`/`-l` option, the skill determines and prints the
+proximity of the given topic once and then stops. With the `--loop`/`-l`
+option, the skill instead presents the nine neighboring topics in an
+interactive dialog; selecting one of them makes it the new *current
+topic* and restarts the determination from the beginning, so the user
+can *navigate* the topic taxonomy up (parent), sideways (siblings), and
+down (children). Cancelling the dialog exits the loop. When `--loop` is
+combined with `--ground`, each newly selected topic is re-grounded via
+the `ase-meta-search` sub-agent before its proximity is re-determined.
+
+##  OPTIONS
+
+`--ground`|`-g`:
+    Ground the determination in Internet/Web facts gathered via the
+    `ase-meta-search` skill before determining the proximity. Without
+    this option, the determination is derived from model knowledge only.
+    When combined with `--loop`, every newly navigated-to topic is
+    re-grounded.
+
+`--loop`|`-l`:
+    Present the neighboring topics in an interactive dialog and, upon
+    selection, adopt the picked topic as the new current topic and
+    restart the determination. Without this option, the proximity of the
+    given topic is printed once and the skill stops.
+
+##  ARGUMENTS
+
+*topic*:
+    The topic whose conceptual proximity is to be determined. It may be
+    a technical concept, a phenomenon, or any other subject; the skill
+    determines its parent, sibling, and child topics.
+
+##  EXAMPLES
+
+Determine the proximity of a topic from model knowledge:
+
+```text
+❯ /ase-meta-proximity Fourier transform
+```
+
+Interactively navigate the conceptual neighborhood, grounded in
+Internet/Web facts:
+
+```text
+❯ /ase-meta-proximity --ground --loop Agentic Software Engineering
+```
+
+##  SEE ALSO
+
+[`ase-meta-eli5`](../ase-meta-eli5/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-code-explain`](../ase-code-explain/help.md).

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

@@ -2,13 +2,17 @@
 name: ase-meta-quorum
 argument-hint: "[--help|-h] [--models|-m <model>[,...]] <question>"
 description: >
-    Query Multiple AIs for Quorum Answer.
+    Query multiple foreign AIs in parallel and synthesize a consensus
+    ("quorum") answer with a consensus rating. Use when the user wants
+    a quorum, a consensus answer, or the opinions of multiple AIs on a
+    question.
 user-invocable: true
 disable-model-invocation: false
 effort: high
 allowed-tools:
     - "Agent"
     - "TaskCreate"
+    - "TaskUpdate"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -21,7 +25,7 @@ Query Multiple AIs for Quorum Answer
 
 <expand name="getopt"
     arg1="ase-meta-quorum"
-    arg2="--models|-m=(all|chatgpt|gemini|deepseek|grok|glm|qwen)...">
+    arg2="--models|-m=(all|chatgpt|gemini|deepseek|grok|glm|qwen|claude|codex|copilot)...">
     $ARGUMENTS
 </expand>
 
@@ -65,7 +69,8 @@ by querying *multiple* AIs for an *optimal consensus*.
     as a comma-separated list of model tokens. The getopt parser
     validates only the *first* token, so you *MUST* validate each
     remaining token yourself against the allowed set `all`, `chatgpt`,
-    `gemini`, `deepseek`, `grok`, `glm`, `qwen`. If any token is *not*
+    `gemini`, `deepseek`, `grok`, `glm`, `qwen`, `claude`, `codex`,
+    `copilot`. If any token is *not*
     in this set, bind <token/> to that offending token, then only output
     the following <template/> and then immediately *STOP* processing the
     entire current skill:
@@ -76,7 +81,10 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     The default is the single token `all`. If <getopt-option-models/>
     contains the token `all`, you *MUST* treat it as the full list
-    `chatgpt,gemini,deepseek,grok,glm,qwen` (all models). Anthropic
+    `chatgpt,gemini,deepseek,grok,glm,qwen` (all API-based models). The
+    harness-based models `claude`, `codex`, and `copilot` are *never*
+    part of `all` and are queried only when their token is given
+    *explicitly* (in addition to `all`, if wished). Anthropic
     Claude (yourself) is *always* included, independent of this option.
 
     <define name="agent">
@@ -116,6 +124,15 @@ by querying *multiple* AIs for an *optimal consensus*.
     <if condition="<getopt-option-models/> contains `all` OR <getopt-option-models/> contains `qwen`">
     <expand name="agent" arg1="Alibaba Qwen"   arg2="qwen"></expand>
     </if>
+    <if condition="<getopt-option-models/> contains `claude`">
+    <expand name="agent" arg1="Anthropic Claude (harness)" arg2="claude"></expand>
+    </if>
+    <if condition="<getopt-option-models/> contains `codex`">
+    <expand name="agent" arg1="OpenAI Codex"               arg2="codex"></expand>
+    </if>
+    <if condition="<getopt-option-models/> contains `copilot`">
+    <expand name="agent" arg1="GitHub Copilot"             arg2="copilot"></expand>
+    </if>
 
     You *MUST* *NOT* output anything in this step.
 
@@ -202,6 +219,18 @@ by querying *multiple* AIs for an *optimal consensus*.
     &#x25CB; **Alibaba Qwen**:
     - [...]
     - [...]
+
+    &#x25CB; **Anthropic Claude (harness)**:
+    - [...]
+    - [...]
+
+    &#x25CB; **OpenAI Codex**:
+    - [...]
+    - [...]
+
+    &#x25CB; **GitHub Copilot**:
+    - [...]
+    - [...]
     </template>
 
     In this output, when a quorum was *not* possible (see STEP 4),

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

@@ -109,7 +109,7 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
 
 2.  <step id="STEP 2: Consolidate Search Answers">
 
-    Consolidate all responses from the `ase:ase-meta-search` agents
+    Consolidate all responses from the `ase:ase-meta-search` agent
     calls above into a single response and output it without giving any
     further explanations.
 

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

@@ -15,7 +15,7 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-steelman">
-    Build the "Steelman" Argument
+Build the "Steelman" Argument
 </skill>
 
 <expand name="getopt"
@@ -25,8 +25,8 @@ effort: xhigh
 </expand>
 
 <objective>
-    Build the "Steelman" argument by constructing the strongest
-    possible case for the thesis: <thesis><getopt-arguments/></thesis>
+Build the "Steelman" argument by constructing the strongest
+possible case for the thesis: <thesis><getopt-arguments/></thesis>
 </objective>
 
 Determine the number of *rounds* to perform: set <rounds/> to

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

@@ -47,7 +47,7 @@ addressing surface-level symptoms.
 
 2.  <step id="STEP 2: Root-Cause Analysis">
 
-    Find the root-cause of <problem/> by following the following iteration cycle.
+    Find the root-cause of <problem/> by following this iteration cycle.
     Start with a <question/> set equal to the <problem/>.
 
     Determine the *maximum chain length* from <getopt-option-depth/>:

package/plugin/skills/ase-sync-export/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ase-sync-export
-argument-hint: "[--help|-h] [--source|-s <source>[,...]] [<filter>]"
+argument-hint: "[--help|-h] [--source|-s <source>[,...]] [<hint>]"
 description: >
     Export artifact content into side-by-side, ready-to-consume files,
     one per artifact that declares an export. Use when the user wants to
@@ -18,7 +18,7 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-sync-export">
-    Export Artifact Set to Side-by-Side Files
+Export Artifact Set to Side-by-Side Files
 </skill>
 
 <expand name="getopt"
@@ -28,11 +28,11 @@ allowed-tools:
 </expand>
 
 <objective>
-    *Export* the *source* artifact kinds (optionally filtered by
-    <hint/>) into side-by-side files, by reading the source artifacts
-    and materializing, for every artifact that declares an export,
-    the corresponding derived file next to the artifact itself.
-    <hint><getopt-arguments/></hint>.
+*Export* the *source* artifact kinds (optionally filtered by
+<hint/>) into side-by-side files, by reading the source artifacts
+and materializing, for every artifact that declares an export,
+the corresponding derived file next to the artifact itself.
+<hint><getopt-arguments/></hint>.
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-meta.md

package/plugin/skills/ase-sync-import/SKILL.md

@@ -17,7 +17,7 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-sync-import">
-    Import Foreign Sources into Artifact Set
+Import Foreign Sources into Artifact Set
 </skill>
 
 <expand name="getopt"
@@ -27,11 +27,11 @@ effort: xhigh
 </expand>
 
 <objective>
-    *Import* the information of the *foreign sources* (named by the
-    <hint/>) into the *target* artifact kinds, by reading the foreign
-    sources and generating or updating the target artifacts to faithfully
-    reflect the imported information:
-    <hint><getopt-arguments/></hint>.
+*Import* the information of the *foreign sources* (named by the
+<hint/>) into the *target* artifact kinds, by reading the foreign
+sources and generating or updating the target artifacts to faithfully
+reflect the imported information:
+<hint><getopt-arguments/></hint>.
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-meta.md
@@ -49,7 +49,7 @@ Procedure
 
     1.  The recognized artifact kinds are the seven tokens `TASK`,
         `SPEC`, `ARCH`, `CODE`, `DOCS`, `INFR`, and `OTHR`. Parse
-        <getopt-target/> as the comma-separated <target/> kind list.
+        <getopt-option-target/> as the comma-separated <target/> kind list.
         Upper-case and trim every parsed kind token. Do not output
         anything.
 
@@ -111,12 +111,15 @@ Procedure
 
 3.  <step id="STEP 3: Generate or Update Artifacts">
 
-    1.  For all kinds in <target/>, call the `ase_artifact_list(kind: [
-        ... ])` tool of the `ase` MCP server *once*, passing the
-        lower-cased `kind` tokens, and read the returned `artifacts`
-        array of `{ kind, files }` objects to obtain the project-relative
-        file list per kind. Read all *existing* target artifacts to
-        understand their current state.
+    1.  For all kinds in <target/> except `TASK`, call the
+        `ase_artifact_list(kind: [ ... ])` tool of the `ase` MCP server
+        *once*, passing the lower-cased `kind` tokens, and read the
+        returned `artifacts` array of `{ kind, files }` objects to
+        obtain the project-relative file list per kind. The `TASK` kind
+        is *not* resolvable via `ase_artifact_list` (task plans are
+        managed by the `ase_task_*` tools), so resolve and read it via
+        the `ase_task_id` and `ase_task_load` tools instead. Read all
+        *existing* target artifacts to understand their current state.
 
     2.  Internalize and honor the artifact-format conventions:
 
@@ -136,8 +139,8 @@ Procedure
         **ASE Tenets** when generating or updating in the following. Do
         not output anything.
 
-    4.  Once call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of
-        the `ase` MCP server to find out the current time and store it in
+    4.  Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+        `ase` MCP server *once* to find out the current time and store it in
         <timestamp-modified/>.
 
     5.  *Generate or update* the <target/> artifact files so that they
@@ -163,7 +166,8 @@ Procedure
         abstraction (a SPEC states intent, an ARCH states structure).
 
         Apply the generation/update directly to the target artifacts via
-        the `Write`/`Edit` tools.
+        the `Write`/`Edit` tools. For a `TASK` target, apply it via the
+        `ase_task_save` tool instead.
 
     6.  Report the performed changes with the following <template/>, listing
         one bullet line per generated or updated file (with <file/> its

package/plugin/skills/ase-sync-reconcile/SKILL.md

@@ -17,7 +17,7 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-sync-reconcile">
-    Reconcile Artifact Set to Artifact Set
+Reconcile Artifact Set to Artifact Set
 </skill>
 
 <expand name="getopt"
@@ -27,10 +27,10 @@ effort: xhigh
 </expand>
 
 <objective>
-    *Reconcile* the *target* artifact kinds to *reflect* the *current
-    state* of the *source* artifact kinds, by reading the source
-    artifacts and aligning the target artifacts accordingly:
-    <hint><getopt-arguments/></hint>.
+*Reconcile* the *target* artifact kinds to *reflect* the *current
+state* of the *source* artifact kinds, by reading the source
+artifacts and aligning the target artifacts accordingly:
+<hint><getopt-arguments/></hint>.
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-meta.md
@@ -48,8 +48,8 @@ Procedure
 
     1.  The recognized artifact kinds are the seven tokens `TASK`,
         `SPEC`, `ARCH`, `CODE`, `DOCS`, `INFR`, and `OTHR`. Parse
-        <getopt-target/> as the comma-separated <target/> kind list and
-        <getopt-source/> as the comma-separated <source/> kind list.
+        <getopt-option-target/> as the comma-separated <target/> kind list and
+        <getopt-option-source/> as the comma-separated <source/> kind list.
         Upper-case and trim every parsed kind token. Do not output
         anything.
 
@@ -81,7 +81,7 @@ Procedure
         ⧉ **ASE**: ☻ skill: **ase-sync-reconcile**, ▶ ERROR: unknown or unsupported artifact kind: **<kind/>**
         </template>
 
-    5.  <if condition="<getopt-bidirectional/> is not 'true'">
+    5.  <if condition="<getopt-option-bidirectional/> is not 'true'">
 
         Remove from <source/> any kind that is also present in <target/>
         (a kind is never its own source).
@@ -157,7 +157,7 @@ Procedure
         the `ase` MCP server to find out the current time and store it in
         <timestamp-modified/>.
 
-    4.  <if condition="<getopt-bidirectional/> is equal 'true'">
+    4.  <if condition="<getopt-option-bidirectional/> is equal 'true'">
 
         *Bidirectionally update* the <target/> and <source/> artifacts
         so that they faithfully *reflect the current state* of each

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

@@ -31,10 +31,21 @@ semantics exactly.
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md
 
 Procedure
 ---------
 
+<define name="handoff-args">
+Set <args></args> (set args to empty).
+<if condition="the condensed plan was saved via `ase_task_save` in step 3">
+    Set <args>--int-reuse-task</args>.
+</if>
+<if condition="<getopt-option-next/> is not equal `none`">
+    Set <args><args/> --next <getopt-option-next/></args>
+</if>
+</define>
+
 1.  **Determine Task:**
 
     1.  Set <id><getopt-arguments/></id> initially.
@@ -76,20 +87,21 @@ Procedure
         the `text` output field of the `ase_task_load` tool call.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
-            Set <content></content> (set content to empty).
+            Silently ignore the MCP error.
+            Set <task-content></task-content> (set task content to empty).
             Set <words/> to "0".
 
         -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
-            Set <content><text/></content> (set content to text).
-            Calculate the number of words <words/> of <content/>.
+            Set <task-content><text/></task-content> (set task content to text).
+            Calculate the number of words <words/> of <task-content/>.
 
         Set <words-before><words/></words-before> (remember the loaded
         word count for the strictly-smaller check in step 3).
 
-        <if condition="<content/> contains '⎈   Created:  <text/>'">
+        <if condition="<task-content/> contains '⎈   Created:  <text/>'">
         Set <timestamp-created><text/></timestamp-created> (extract the
         original creation timestamp so it can be re-inserted unchanged
-        into the condensed <content/> in step 3).
+        into the condensed <task-content/> in step 3).
         </if>
 
         Only output the following <template/>:
@@ -98,7 +110,7 @@ Procedure
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan loaded**
         </template>
 
-    2.  <if condition="<content/> is empty">
+    2.  <if condition="<task-content/> is empty">
         Complain and tell the user to use the `ase-code-resolve`,
         `ase-code-refactor`, `ase-code-craft`, or `ase-task-edit` skills
         first to create a task plan. Then immediately stop processing
@@ -107,8 +119,8 @@ Procedure
 
 3.  **Condense Task Plan:**
 
-    1.  *Apply the condense ruleset* to <content/>, producing a shorter
-        <content/>. The goal is to make the plan require as *little
+    1.  *Apply the condense ruleset* to <task-content/>, producing a shorter
+        <task-content/>. The goal is to make the plan require as *little
         reading* as possible while all semantics remain *fully preserved
         and unchanged*. Honor the following ruleset *strictly*:
 
@@ -148,25 +160,10 @@ Procedure
             longer wording*.
 
     2.  *Persist only if smaller*: calculate the number of words <words/>
-        of the condensed <content/>.
+        of the condensed <task-content/>.
 
         -   <if condition="<words/> is strictly smaller than <words-before/>">
-            Update <timestamp-modified/> with the current time in
-            ISO-style format, which has to be determined by calling
-            the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool
-            of the `ase` MCP server and use the `text` field of
-            its response. Keep the original <timestamp-created/>,
-            re-insert the current <ase-task-id/> and the refreshed
-            <timestamp-modified/> into <content/>.
-
-            Call the `ase_task_save(id: "<ase-task-id/>", text:
-            "<content/>")` tool of the `ase` MCP server to save the
-            condensed task plan content. Do not output anything related
-            to this MCP call except the following <template/>:
-
-            <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan condensed**
-            </template>
+            <expand name="task-save-content" arg1="plan condensed"></expand>
             </if>
 
         -   <if condition="<words/> is NOT strictly smaller than <words-before/>">
@@ -182,39 +179,15 @@ Procedure
 
     1.  *Determine next step*:
 
-        -   If <getopt-option-next/> is not equal to `none`:
-            Treat <getopt-option-next/> as a comma-separated chronological
-            list of pre-selected next-step tokens. *Split* it on `,`,
-            take the *first* token as <head/>, and store the remaining
-            tokens (joined back with `,`, or `none` if empty) into
-            <getopt-option-next/> so downstream skills can consume the tail.
-
-            -   If <head/> matches the regex `^(DONE|EDIT|IMPLEMENT|PREFLIGHT)$`:
-                Honor the pre-selected token.
-                Set <result><head/></result>.
-
-            -   else:
-                Only output the following <template/> and then immediately
-                *STOP* processing the entire current skill:
-
-                <template>
-                ⧉ **ASE**: ☻ skill: **ase-task-condense**, ▶ ERROR: invalid `--next` token: **<head/>**
-                </template>
-
-        -   If <getopt-option-next/> is equal to `none`:
-
-            In the following, you *MUST* *NOT* use your built-in
-            <user-dialog-tool/> tool! Instead, you *MUST* just show a
-            custom dialog according to the expanded `custom-dialog`
-            definition. You *MUST* closely follow this definition:
-
-            <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.
-                PREFLIGHT: Hand off plan to pre-flighting.
-                IMPLEMENT: Hand off plan to implementation.
-            </expand>
+        <expand name="task-next-select"
+            arg1="ase-task-condense"
+            arg2="DONE|EDIT|IMPLEMENT|PREFLIGHT">
+            Next Step: How would you like to proceed with the plan?
+            DONE: Stop processing.
+            EDIT: Hand off plan to editing.
+            PREFLIGHT: Hand off plan to pre-flighting.
+            IMPLEMENT: Hand off plan to implementation.
+        </expand>
 
     2.  Check the tool <result/> and dispatch accordingly:
 
@@ -226,13 +199,7 @@ Procedure
             </template>
 
         -   If <result/> is `EDIT`:
-            Set <args></args> (set args to empty).
-            <if condition="the condensed plan was saved via `ase_task_save` in step 3">
-                Set <args>--int-reuse-task</args>.
-            </if>
-            <if condition="<getopt-option-next/> is not equal `none`">
-                Set <args><args/> --next <getopt-option-next/></args>
-            </if>
+            <expand name="handoff-args"/>
             Only output the following <template/> and then call the
             tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`
             to invoke the `ase:ase-task-edit` skill in order to *edit*
@@ -244,13 +211,7 @@ Procedure
             </template>
 
         -   If <result/> is `IMPLEMENT`:
-            Set <args></args> (set args to empty).
-            <if condition="the condensed plan was saved via `ase_task_save` in step 3">
-                Set <args>--int-reuse-task</args>.
-            </if>
-            <if condition="<getopt-option-next/> is not equal `none`">
-                Set <args><args/> --next <getopt-option-next/></args>
-            </if>
+            <expand name="handoff-args"/>
             Only output the following <template/> and then call the
             `Skill(skill: "ase:ase-task-implement", args: "<args/>")` tool
             to *apply* the plan.
@@ -260,13 +221,7 @@ Procedure
             </template>
 
         -   If <result/> is `PREFLIGHT`:
-            Set <args></args> (set args to empty).
-            <if condition="the condensed plan was saved via `ase_task_save` in step 3">
-                Set <args>--int-reuse-task</args>.
-            </if>
-            <if condition="<getopt-option-next/> is not equal `none`">
-                Set <args><args/> --next <getopt-option-next/></args>
-            </if>
+            <expand name="handoff-args"/>
             Only output the following <template/> and then call the
             `Skill(skill: "ase:ase-task-preflight", args: "<args/>")` tool
             to *apply* the plan.