@rse/ase 0.9.44 → 0.9.45

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

@@ -4,7 +4,6 @@ argument-hint: "[--help|-h] <source-reference>"
 description: Review software architecture, including package cohesion and inter-package coupling
 user-invocable: true
 disable-model-invocation: false
-model: opus
 effort: high
 allowed-tools:
     - "Bash(wc *)"
@@ -252,7 +251,7 @@ interface quality, quality attributes, and architecture governance.
       - *god-package*: *incoming ≥ 5* and *outgoing ≥ 3* -
         coordinator dumping ground that should be split along its
         internal topical clusters
-      - *fragment*: 1–2 files under a sibling parent that share a
+      - *fragment*: 1-2 files under a sibling parent that share a
         *name prefix* or *imported interface* with that sibling -
         consolidation candidate
 
@@ -278,7 +277,7 @@ interface quality, quality attributes, and architecture governance.
       which operations sit *between* the specific acquire and
       release in source order.
 
-    - *Package-graph construction (SA19–SA21)*: parse each file's
+    - *Package-graph construction (SA19-SA21)*: parse each file's
       import (or equivalent language construct) statement, keep
       only first-party packages within the analyzed scope, and
       persist two intermediate structures: the per-package

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

@@ -2,7 +2,7 @@
 name: ase-code-craft
 argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <feature>"
 description: >
-    Craft Source:
+    Craft Source Code:
     Use when user wants to "create", "add", or "craft" a new feature from scratch.
 user-invocable: true
 disable-model-invocation: false
@@ -109,7 +109,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     7.  Ask the user for clarification if the goal of this crafting is too
         unclear.
 
-    8.  Do not output anything in this step, unless you asked the user.
+    8.  Do not output anything else in this step, unless you asked the user.
 
     </step>
 
@@ -231,18 +231,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         closely aligning to the existing architecture and the existing
         code base. Use the <format/> defined for a task plan and inject
         the information from feature A<n/> and all derived realization
-        decisions into it. Store the resulting task plan in <content/>.
+        decisions into it. Store the resulting task plan in <task-content/>.
 
         If a `CHANGELOG.md` file exists in the project (or in any
         affected sub-package), the plan *MUST* include, as part of its
-        `## ※ CHANGES` section, an explicit bullet point describing
+        `##  CHANGES` section, an explicit bullet point describing
         the addition of a corresponding new entry to that `CHANGELOG.md`
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
         You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
-        <content/>.
+        <task-content/>.
         </if>
 
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
@@ -253,10 +253,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <timestamp-created/> and <timestamp-modified/> information. Then
         insert the current <ase-task-id/>, <timestamp-created/>, and
         <timestamp-modified/> information and calculate the number of
-        words <words/> of <content/>.
+        words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
 
     4.  Output a hint with the following <template/>:
 

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

@@ -154,11 +154,14 @@ related to a set of code quality aspects.
         still perform substep 3 first. Never leave this marker active
         for a later, unrelated `Edit`.
 
-    2.  Iterate over all problems:
+    2.  Set <total/> to the number of problems in <problems/> and
+        <index/> to `0`. Then iterate over all problems:
 
         <for items="<problems/>">
 
-        1.  Set <aspect/>      to the `aspect`      field of <item/>.
+        1.  Increment <index/> by one (the 1-based position of the
+            current <item/> within <problems/>).
+            Set <aspect/>      to the `aspect`      field of <item/>.
             Set <severity/>    to the `severity`    field of <item/>.
             Set <description/> to the `description` field of <item/>.
             Set <change-set/>  to the `change-set`  field of <item/>.
@@ -193,6 +196,19 @@ related to a set of code quality aspects.
                     Set <new-text/>       to the `new_text`       field of <item/>.
                     Set <context-after/>  to the `context_after`  field of <item/>.
 
+                    Then *normalize* the hunk to its *minimal* form, so
+                    that the proposed diff shows exactly the lines the
+                    later `Edit` will actually change: while the *first*
+                    line of <old-text/> is identical to the *first* line
+                    of <new-text/>, *move* that line from both to the
+                    end of <context-before/> and increment <line/> by
+                    one; likewise, while the *last* line of <old-text/>
+                    is identical to the *last* line of <new-text/>,
+                    *move* that line from both to the front of
+                    <context-after/>. Finally, *trim* <context-before/>
+                    to its *last* two lines and <context-after/> to its
+                    *first* two lines.
+
                 2.  *Skip* this substep entirely when <ase-project-boxing/>
                     is equal `grey` - the full unified diff is suppressed
                     there, so none of the <hunk-body/>, <old-count/>,
@@ -288,7 +304,7 @@ related to a set of code quality aspects.
         4.  Report the problem with the following <template/>:
 
             <template>
-            <ase-tpl-bullet-signal/> **<aspect/> PROBLEM** (`<severity/>`): <context/>
+            <ase-tpl-bullet-signal/> [<index/>/<total/>]: **<aspect/> PROBLEM** (`<severity/>`): <context/>
 
             <description/>
 

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

@@ -18,7 +18,7 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-code-refactor">
-Refactor Artifacts
+Refactor Source Code
 </skill>
 
 <expand name="getopt"
@@ -109,7 +109,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     7.  Ask the user for clarification if the goal of this refactoring is
         too unclear.
 
-    8.  Do not output anything in this step, unless you asked the user.
+    8.  Do not output anything else in this step, unless you asked the user.
 
     </step>
 
@@ -231,18 +231,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         closely aligning to the existing architecture and the existing
         code base. Use the <format/> defined for a task plan and inject
         the information from refactoring A<n/> and all derived realization
-        decisions into it. Store the resulting task plan in <content/>.
+        decisions into it. Store the resulting task plan in <task-content/>.
 
         If a `CHANGELOG.md` file exists in the project (or in any
         affected sub-package), the plan *MUST* include, as part of its
-        `## ※ CHANGES` section, an explicit bullet point describing
+        `##  CHANGES` section, an explicit bullet point describing
         the addition of a corresponding new entry to that `CHANGELOG.md`
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
         You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
-        <content/>.
+        <task-content/>.
         </if>
 
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
@@ -253,10 +253,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <timestamp-created/> and <timestamp-modified/> information. Then
         insert the current <ase-task-id/>, <timestamp-created/>, and
         <timestamp-modified/> information and calculate the number of
-        words <words/> of <content/>.
+        words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
 
     4.  Output a hint with the following <template/>:
 

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

@@ -124,7 +124,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     8.  Ask the user for clarification if the goal of this resolution is
         too unclear.
 
-    9.  Do not output anything in this step, unless you asked the user.
+    9.  Do not output anything else in this step, unless you asked the user.
 
     10. Investigate and *figure out details* related to this problem.
         Report those details with the following <template/>:
@@ -285,18 +285,18 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         problem, the chosen resolution approach, a preview of the *unified
         diff* of the necessary code changes, and a possible way to verify
         the success of the resolution, by using the <format/> defined for a
-        task plan. Store the resulting task plan in <content/>.
+        task plan. Store the resulting task plan in <task-content/>.
 
         If a `CHANGELOG.md` file exists in the project (or in any
         affected sub-package), the plan *MUST* include, as part of its
-        `## ※ CHANGES` section, an explicit bullet point describing
+        `##  CHANGES` section, an explicit bullet point describing
         the addition of a corresponding new entry to that `CHANGELOG.md`
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
         You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
-        <content/>.
+        <task-content/>.
         </if>
 
         You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
@@ -307,10 +307,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         <timestamp-created/> and <timestamp-modified/> information. Then
         insert the current <ase-task-id/>, <timestamp-created/>, and
         <timestamp-modified/> information and calculate the number of
-        words <words/> of <content/>.
+        words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
 
     4.  If <problem-id/> is set (i.e. the <problem/> was retrieved from
         `ase_kv_get` in STEP 1.1 via key `ase-issue-<problem-id/>`),

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

@@ -17,7 +17,7 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-docs-distill">
-    Distill Key Points
+Distill Key Points
 </skill>
 
 <expand name="getopt"
@@ -27,11 +27,11 @@ effort: high
 </expand>
 
 <objective>
-    *Distill* the content `<getopt-arguments/>` into a *flat*,
-    *importance-ranked* list of its *key points* - each point an
-    *atomic* claim carrying a *0-10 salience rank*, a *one-line
-    rationale*, and a *verbatim, line-cited evidence* snippet - keeping
-    at most `<getopt-option-top/>` points.
+*Distill* the content `<getopt-arguments/>` into a *flat*,
+*importance-ranked* list of its *key points* - each point an
+*atomic* claim carrying a *0-10 salience rank*, a *one-line
+rationale*, and a *verbatim, line-cited evidence* snippet - keeping
+at most `<getopt-option-top/>` points.
 </objective>
 
 Procedure

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

@@ -135,11 +135,14 @@ Analyze documents for spelling, punctuation, or grammar errors
         still perform substep 3 first. Never leave this marker active
         for a later, unrelated `Edit`.
 
-    2.  Iterate over all problems:
+    2.  Set <total/> to the number of problems in <problems/> and
+        <index/> to `0`. Then iterate over all problems:
 
         <for items="<problems/>">
 
-        1.  Set <type/>           to the `type` field of <item/>.
+        1.  Increment <index/> by one (the 1-based position of the
+            current <item/> within <problems/>).
+            Set <type/>           to the `type` field of <item/>.
             Set <file/>           to the `file` field of <item/>.
             Set <line/>           to the `line` field of <item/>.
             Set <description/>    to the `description` field of <item/>.
@@ -148,10 +151,22 @@ Analyze documents for spelling, punctuation, or grammar errors
             Set <new-text/>       to the `new_text` field of <item/>.
             Set <context-after/>  to the `context_after` field of <item/>.
 
+            Then *normalize* the change to its *minimal* form, so
+            that the proposed diff shows exactly the lines the later
+            `Edit` will actually change: while the *first* line of
+            <old-text/> is identical to the *first* line of
+            <new-text/>, *move* that line from both to the end of
+            <context-before/> and increment <line/> by one; likewise,
+            while the *last* line of <old-text/> is identical to the
+            *last* line of <new-text/>, *move* that line from both to
+            the front of <context-after/>. Finally, *trim*
+            <context-before/> to its *last* two lines and
+            <context-after/> to its *first* two lines.
+
         2.  Report the problem with the following <template/>:
 
             <template>
-            <ase-tpl-bullet-signal/> **<type/> PROBLEM**: `<file/>`:<line/>:
+            <ase-tpl-bullet-signal/> [<index/>/<total/>]: **<type/> PROBLEM**: `<file/>`:<line/>:
 
             <description/>
             </template>

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

@@ -2,7 +2,7 @@
 name: ase-meta-changelog
 argument-hint: "[--help|-h]"
 description: >
-    Update changes entries in CHANGELOG.md files
+    Update ChangeLog entries in CHANGELOG.md files
 user-invocable: true
 disable-model-invocation: false
 effort: high
@@ -108,7 +108,10 @@ Processing
     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*
+    level-2 header as the baseline tag instead. If *no* second level-2
+    header exists (very first, still untagged release), skip the baseline
+    tag and check *all* Git commits with the command `git log HEAD
+    --numstat --pretty=format:'%h: %s'` 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

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

@@ -48,10 +48,10 @@ currently staged Git changes.
     of the `ase-meta-diff` and `ase-meta-changelog` skills) and their
     usual corresponding kind of change are:
 
-    -   `FEATURE`:     new functionality or configuration
-    -   `IMPROVEMENT`: improved functionality or configuration
-    -   `BUGFIX`:      corrected functionality or configuration
-    -   `UPDATE`:      updated functionality or configuration
+    -   `FEATURE`:     new        functionality or configuration
+    -   `IMPROVEMENT`: improved   functionality or configuration
+    -   `BUGFIX`:      corrected  functionality or configuration
+    -   `UPDATE`:      updated    functionality or configuration
     -   `CLEANUP`:     cleaned up functionality or configuration
     -   `REFACTOR`:    refactored functionality or configuration
 

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

@@ -40,8 +40,8 @@ value until STEP 6. Do not fabricate passes: a probe whose actual result
 differs from its expected result *MUST* be recorded as a *fail*.
 
 Notice that this skill intentionally does not strictly follow the ASE
-skill format, especially it does not include any meta skill information,
-etc.
+skill format; in particular, it does not include the usual meta skill
+information.
 
 Procedure
 ---------
@@ -107,7 +107,7 @@ Procedure
         Record <s/> as actual result for `control-flow/while-sum`.
 
     3.  *for-order*: Set <s></s>, then evaluate
-        `<for items="x y z"><s><s/>-<item/></for>`.
+        `<for items="x y z"><s><s/>-<item/></s></for>`.
         Record <s/> as actual result for `control-flow/for-order`.
 
     4.  *while-break*: Set <i>1</i> and <hit></hit>, then evaluate

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

@@ -103,8 +103,8 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
 
     -   **Argue in Good Faith**:
         Make clear you're just stress-testing the thesis, not
-        obstructing, because the goal of the objective is a better final
-        decision, not winning.
+        obstructing, because the goal is a better final decision, not
+        winning.
 
     -   **Know When to Yield**:
         Conceding when the argument holds is what makes the challenge

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

@@ -81,19 +81,16 @@ multi-*criteria* decision matrix.
     -   For each alternative <alternative-K/> (K=1-N), decide whether
         it is a genuine member of <class-of-alternatives/>. If any
         <alternative-K/> is *not* a member (i.e. the alternatives are not
-        mutually comparable within a single class), collect the subset
-        of non-member alternatives into the space-separated list
-        <non-members/> (the <alternative-K/> for which the membership
-        decision was negative), output the following <template/> and
-        *stop the entire flow* immediately without executing any further
-        steps:
+        mutually comparable within a single class), output the following
+        <template/> (repeating the `⚑` line once per non-member
+        alternative, i.e. once for each <alternative-K/> for which the
+        membership decision was negative) and *stop the entire flow*
+        immediately without executing any further steps:
 
         <template>
         <ase-tpl-bullet-signal/> **ERROR: INCOMPARABLE ALTERNATIVES**: *<class-of-alternatives/>*
 
-        <for items="<non-members/>">
-        ⚑ **<item/>** (*member of a different class*)
-        </for>
+        ⚑ **<alternative-K/>** (*member of a different class*)
         </template>
 
     -   Output the determined, individual alternatives as a Markdown

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