@rse/ase 0.9.43 → 0.9.45

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

@@ -48,19 +48,21 @@ The intent is constructive: building the best honest case for the
 thesis to arrive at a better final decision, not overselling or merely
 cheerleading.
 
-##  ARGUMENTS
+##  OPTIONS
 
-`--count`, `-c` *count*:
+`--count`|`-c` *count*:
     Surface at least *count* strong pro-theses (default *10*) per defense
     pass before sorting and reporting the top *count* and deriving the
     *FORTIFICATION*. An invalid or non-positive *count* reverts to the
     default *10*.
 
-`--rounds`, `-r` *rounds*:
+`--rounds`|`-r` *rounds*:
     Run *rounds* iterative defense rounds (default *1*), feeding each
     round's *FORTIFICATION* in as the next round's *thesis*. An invalid
     or non-positive *rounds* reverts to the default *1*.
 
+##  ARGUMENTS
+
 *thesis*:
     The statement, claim, or position to be charitably strengthened.
     It may be technical, factual, or opinion-based; the skill defends

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/>:
@@ -66,7 +66,7 @@ addressing surface-level symptoms.
 
         <while condition="<n/> is less than or equal to <depth/>">
 
-            Ask <question/> and document the answer in <answer/> with the following template:
+            Ask <question/> and document the answer in <answer/> with the following template.
             Don't stop at symptoms, keep digging for systemic issues.
             Consider technical, domain-specific, process-related, or organizational causes.
 

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

@@ -29,7 +29,7 @@ wrong sub-cause. After identifying (and validating) the root cause it
 proposes a *SOLUTION* that addresses it, optionally including concrete
 source code changes.
 
-##  ARGUMENTS
+##  OPTIONS
 
 `--depth`|`-d` *N*:
     The *maximum* number of "why" iterations (the Five-Whys chain
@@ -49,6 +49,8 @@ source code changes.
     single, but better-justified, root-cause. A non-numeric or non-positive
     value falls back to the default.
 
+##  ARGUMENTS
+
 *fact*:
     The observed *fact* (symptom, problem, or surprising outcome)
     whose root cause should be investigated. The skill implicitly

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
@@ -48,7 +48,7 @@ Procedure
 
     1.  The recognized artifact kinds are the seven tokens `TASK`,
         `SPEC`, `ARCH`, `CODE`, `DOCS`, `INFR`, and `OTHR`. Parse
-        <getopt-source/> as the comma-separated <source/> kind list.
+        <getopt-option-source/> as the comma-separated <source/> kind list.
         Upper-case and trim every parsed kind token. Do not output
         anything.
 
@@ -84,11 +84,13 @@ Procedure
 
     1.  Do not output anything in this STEP 2.
 
-    2.  For all kinds in <source/>, 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.
+    2.  For all kinds in <source/> 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) and declares no export, so *silently skip* it.
 
     3.  <if condition="<hint/> is not empty">
 
@@ -139,11 +141,12 @@ Procedure
 
         -   *Determine* the side-by-side target file name
             <export-filename/>
-            as `<basedir/>/<artifact-set-id/>-<artifact-no/>-<artifact-id/>-<artifact-slug/>-<export-name/>.<export-ext/>`
+            as `<artifact-set-id/>-<artifact-no/>-<artifact-id/>-<artifact-slug/>-<export-name/>.<export-ext/>`
             and resolve it to a project-relative path inside the
-            artifact's own base directory by calling the
-            `ase_artifact_name(filename: "<file-name/>", kind:
-            "<export-filename/>")` tool of the `ase` MCP server.
+            artifact's own base directory (`<basedir/>`) by calling the
+            `ase_artifact_name(filename: "<export-filename/>", kind:
+            "<artifact-kind/>")` tool of the `ase` MCP server, with
+            <artifact-kind/> the artifact's own lower-cased kind.
 
         -   *Write* the derived rendering to that resolved path via the
             `Write` tool, overwriting any pre-existing export file of the

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-import/help.md

@@ -61,7 +61,7 @@ Import a foreign requirements document into the specification:
 ❯ /ase-sync-import -t SPEC docs/legacy/requirements.txt
 ```
 
-Import an external design write-up into the architecture, defaulting
+Import an external design write-up into the architecture, defaulting to
 both specification and architecture as targets:
 
 ```text
@@ -78,4 +78,4 @@ Import a pasted feature description into a task plan:
 
 [`ase-sync-reconcile`](../ase-sync-reconcile/help.md),
 [`ase-sync-export`](../ase-sync-export/help.md),
-[`ase-task-implement`](../ase-task-implement/help.md)
+[`ase-task-implement`](../ase-task-implement/help.md).

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.
 
@@ -78,10 +78,10 @@ Procedure
         *STOP* processing the entire current skill:
 
         <template>
-        ⧉ **ASE**: ☻ skill: **ase-sync-reconcile**, ▶ ERROR: unknown artifact kind: **<kind/>**
+        ⧉ **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-sync-reconcile/help.md

@@ -86,4 +86,4 @@ each other, limited to the authentication aspect:
 ##  SEE ALSO
 
 [`ase-meta-changelog`](../ase-meta-changelog/help.md),
-[`ase-task-implement`](../ase-task-implement/help.md)
+[`ase-task-implement`](../ase-task-implement/help.md).

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

@@ -31,13 +31,24 @@ 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 <instruction><getopt-arguments/></instruction> initially.
+    1.  Set <id><getopt-arguments/></id> initially.
         Inherit the always existing <ase-task-id/> from the current context.
         Inherit the always existing <ase-session-id/> from the current context.
         Do not output anything.
@@ -45,11 +56,10 @@ Procedure
     2.  React on task id:
 
         1.  <if condition="
-                <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+                <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
             ">
-            Set <ase-task-id><instruction/></ase-task-id> (set task
-            id to instruction) and <instruction></instruction> (set
-            instruction empty), call the `ase_task_id(id: "<ase-task-id/>",
+            Set <ase-task-id><id/></ase-task-id> (set task id) and
+            call the `ase_task_id(id: "<ase-task-id/>",
             session: "<ase-session-id/>")` tool from the `ase` MCP
             server to switch the task, and then only output the
             following <template/>:
@@ -59,7 +69,7 @@ Procedure
             </template>
             </if>
 
-        2.  <elseif condition="<instruction/> is NOT empty">
+        2.  <elseif condition="<id/> is NOT empty">
             The argument is neither empty nor a valid task id. As this
             skill only accepts an optional `[<id>]` argument and *never*
             a free-text instruction, only output the following <template/>
@@ -77,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/>:
@@ -99,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
@@ -108,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*:
 
@@ -149,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/>">
@@ -183,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.
-                IMPLEMENT: Hand off plan to implementation.
-                PREFLIGHT: Hand off plan to pre-flighting.
-            </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:
 
@@ -227,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*
@@ -245,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.
@@ -261,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.

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

@@ -51,7 +51,7 @@ Procedure
         </template>
         </if>
 
-2.  **Perform Operation**:
+2.  **Perform Operation:**
 
     1.  Call the `ase_task_delete(id: "<id/>")` tool of the `ase` MCP
         server to delete the task plan content and set <text/> to the