@rse/ase 0.0.39 → 0.0.41

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

@@ -99,7 +99,7 @@ allowed-tools:
     - "Skill"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Review Software Architecture
@@ -302,11 +302,13 @@ interface quality, quality attributes, and architecture governance.
     - For <style/>, name the detected architecture style or
       "*undeclared*" if none is documented.
 
-    - For <rendered-diagram-as-fenced-code-block/>, emit *Mermaid*
-      source for a `flowchart TB` of the high-level component or
-      layer structure and invoke the `ase-meta-diagram` skill via the
-      `Skill` tool to render it. Show layers / slices / major
-      components and their dependency direction.
+    - For <rendered-diagram-as-fenced-code-block/>, build a Mermaid
+      specification <mermaid-spec/> for a `flowchart TB` of the
+      high-level component or layer structure and invoke the
+      `ase-meta-diagram` skill by calling the tool `Skill(skill:
+      "ase:ase-meta-diagram", args: <mermaid-spec/>)` to render it.
+      Show layers / slices / major components and their dependency
+      direction.
 
     - Mark detected *anomalies* directly in the Mermaid source.
       Because `!` and `?` are Mermaid special characters, *always

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

@@ -9,13 +9,11 @@ disable-model-invocation: false
 effort: medium
 allowed-tools:
     - "Bash(npm search --json *)"
-    - "Bash(npm view --json *)"
     - "Skill"
     - "Agent"
-    - "WebFetch"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Discover Components
@@ -112,26 +110,6 @@ for the technology stack to *provide* the *needed functionality*
             (L=1-M). Merge the results into the already existing result
             set, but deduplicate entries.
 
-        -   For each discovered *NPM package* <component-K/> (K=1-N),
-            use the shell command `npm view --json "<package-K/>"
-            version time repository.url` to discover
-            its version <version-K/>, the publish time of that
-            version <updated-K/> (read from `time[<version-K/>]`),
-            its time created <created-K/> (read from `time.created`),
-            and its repository URL <repository-K/>.
-
-        -   If the <repository-K/> regexp-matches
-            `.+?//github\.com/([^/]+/[^/.]+).*` use the `WebFetch` tool
-            to fetch the URL `https://api.github.com/repos/$1` (`$1`
-            is the value matched by the first capturing parenthesis
-            in the regexp) and extract <stars-K/> from its JSON
-            `stargazers_count` field, else set <stars-K/> to `N.A.`.
-
-        -   For each discovered *NPM package* <component-K/>
-            (K=1-N), use the `WebFetch` tool on the URL
-            `https://api.npmjs.org/downloads/point/last-month/<package-K/>`
-            to extract the <downloads-K/> from the `downloads` field.
-
     -   If <stack/> is "Java" or "Kotlin":
 
         -   Based on the essential keywords <keyword-L/> (L=1-M),
@@ -139,25 +117,60 @@ for the technology stack to *provide* the *needed functionality*
             discover an initial set of a maximum of 12 *Java packages*
             <component-K/> and at least their real name <name-K/> and
             their unique package names <package-K/>.
+
+    -   Call the `component_info(stack: <stack/>, components:
+        [ <package-1/>, ..., <package-N/> ])` tool of the `ase` MCP
+        service *once* for the entire set of discovered packages.
+        The tool dispatches internally on <stack/> and fetches all
+        metadata in maximum parallel and returns an array of objects `{
+        name, version, time, repository, stars, downloads }`. For each
+        component <component-K/> (K=1-N) read from its corresponding
+        entry: <version-K/> from `version`, <updated-K/> from `updated`,
+        <created-K/> from `created`, <repository-K/> from `repository`,
+        <stars-K/> from `stars` (numeric or `N.A.`), <downloads-K/>
+        from `downloads` (numeric or `N.A.`) and <rank-K/> from `rank`
+        (numeric).
+
+    -   Sort, in descending order, the discovered components
+        <component-K/> (K=1-N) by their `rank` field and trim the result
+        list to just a maximum of 12 total components.
+
+    -   For each component <component-K/> (K=1-N), research and then
+        decide which *one* of *USP* (Unique Selling Point -- what makes
+        it unique), *Crux* (what you should notice), or *Gotcha* (what
+        you should not stumble over) is its single most distinguishing
+        perspective, and remember this as an <info-K/> (K=1-N) formatted
+        like `<type/>: <hint/>` where <type/> is one of `USP`, `Crux`,
+        or `Gotcha` and <hint/> is a 1-6 word hint. Do not output
+        anything.
     </step>
 
 4.  <step id="STEP 4: Report Components">
-    -   Sort, in descending order, the discovered components
-        <component-K/> (K=1-N) first by their <downloads-K/> and second
-        by their <stars-K/> and trim the result list to just a maximum
-        of 12 total components.
+    -   Display the determined, individual components as a Markdown
+        *table* with just the following <template/> and do not output
+        anything else:
+
+        <template>
+        &#x1F535; **COMPONENT HINTS**:
+
+        | ⚑ *Component*      | ▣ *Package*    | ⚖ *Hint*  |
+        | :----------------- | :------------- | :-------- |
+        | **<component-1/>** | `<package-1/>` | <info-1/> |
+        [...]
+        | **<component-N/>** | `<package-N/>` | <info-N/> |
+        </template>
 
     -   Display the discovered components as a Markdown *table*
         with just the following <template/>:
 
         <template>
-        &#x1F535; **COMPONENTS**:
+        &#x1F535; **COMPONENT RANKING**:
 
-        | *Component*   | *Package*      | *Version*    | *Downloads*        | *Stars*        | *Updated*        | *Created*    |
-        | :------------ | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
-        | **<name-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
+        | ⚑ *Component*      | ▣ *Package*    | ❖ *Version*  | ↓ *Downloads*      | ⎈ *Stars*      | ⏲ *Updated*      | ☆ *Created*  |
+        | :----------------- | :------------- | -----------: | -----------------: | -------------: | :--------------- | :----------- |
+        | **<component-1/>** | `<package-1/>` | <version-1/> | **<downloads-1/>** | **<stars-1/>** | **<updated-1/>** | <created-1/> |
         [...]
-        | **<name-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
+        | **<component-N/>** | `<package-N/>` | <version-N/> | **<downloads-N/>** | **<stars-N/>** | **<updated-N/>** | <created-N/> |
         </template>
     </step>
 </flow>

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

@@ -10,7 +10,7 @@ allowed-tools:
     - "Agent"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Analyze Source Code

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

@@ -11,7 +11,7 @@ allowed-tools:
     - "Skill"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
@@ -186,14 +186,18 @@ permitted way to persist artifacts is via `task_save(...)`.
             *precise* and *brief* feature information. Try to keep the
             number of bullet points (●) in the range of 1-4.
 
-        -   In case of a *complex feature situation* only, visualize it with
-            an optional diagram <optional-diagram/> by invoking the
-            `ase-meta-diagram` skill via the `Skill` tool. For *current vs.
-            proposed* comparisons, render each side as a *separate*
-            `ase-meta-diagram` invocation and stack the rendered blocks
-            *vertically* (labels `**Before:**` / `**After:**`); never
-            side-by-side. Omit <optional-diagram/> entirely for simple or
-            purely local situation.
+        -   In case of a *complex feature situation* only, visualize
+            it with an optional diagram <optional-diagram/> by building
+            a Mermaid specification <mermaid-spec/> (e.g. `flowchart
+            TB`, `stateDiagram-v2`, `sequenceDiagram`, `classDiagram`,
+            or `erDiagram`, depending on intent) and invoking the
+            `ase-meta-diagram` skill by calling the tool `Skill(skill:
+            "ase:ase-meta-diagram", args: <mermaid-spec/>)`. For
+            *current vs. proposed* comparisons, render each side as
+            a *separate* `ase-meta-diagram` invocation and stack the
+            rendered blocks *vertically* (labels `**Before:**` /
+            `**After:**`); never side-by-side. Omit <optional-diagram/>
+            entirely for simple or purely local situation.
 
 5.  **Choose Feature Crafting Approach**:
 

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

@@ -12,7 +12,7 @@ allowed-tools:
     - "Agent"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Explain Source Code
@@ -72,10 +72,12 @@ code and *explain* it in *brief*, *standardized*, and *concise* way.
     Second, draw a diagram to show the control or data flow, code or
     data structure, or code or data relationships. What gives the best
     overall overview of the code?
-    Choose the Mermaid diagram type per intent: `classDiagram` for
-    class/method structure, `sequenceDiagram` for actor/message flow,
-    or `flowchart TB` for boxes-and-lines component layouts.
-    Invoke the `ase-meta-diagram` skill via the `Skill` tool to render the
+    Build a Mermaid specification <mermaid-spec/>, choosing the Mermaid
+    diagram type per intent: `classDiagram` for class/method structure,
+    `sequenceDiagram` for actor/message flow, or `flowchart TB` for
+    boxes-and-lines component layouts. Then invoke the
+    `ase-meta-diagram` skill by calling the tool `Skill(skill:
+    "ase:ase-meta-diagram", args: <mermaid-spec/>)` to render the
     diagram. Do *not* hand-draw.
 
     Keep your explanation *brief* and *concise*.

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

@@ -14,7 +14,7 @@ allowed-tools:
     - "Skill"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Project Insight
@@ -90,11 +90,13 @@ Give *insights* into the project through the source code of $ARGUMENTS.
     🔵 **MODULE STRUCTURE**:
     </template>
 
-    Find all modules (or OOP classes) and draw a `flowchart TB`
-    diagram with all modules as boxes and the imports between modules
-    as the directed edges. Invoke the `ase-meta-diagram` skill via the
-    `Skill` tool to render the diagram. Do not display any further
-    explanation except for this diagram.
+    Find all modules (or OOP classes) and build a Mermaid specification
+    <mermaid-spec/> for a `flowchart TB` diagram with all modules as
+    boxes and the imports between modules as the directed edges. Then
+    invoke the `ase-meta-diagram` skill by calling the tool
+    `Skill(skill: "ase:ase-meta-diagram", args: <mermaid-spec/>)`
+    to render the diagram. Do not display any further explanation except
+    for this diagram.
     </step>
 </flow>
 

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

@@ -8,7 +8,7 @@ disable-model-invocation: false
 effort: medium
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Lint Source Code

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

@@ -11,7 +11,7 @@ allowed-tools:
     - "Skill"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
@@ -190,14 +190,18 @@ permitted way to persist artifacts is via `task_save(...)`.
             *precise* and *brief* refactoring information. Try to keep the
             number of bullet points (●) in the range of 1-4.
 
-        -   In case of a *complex refactoring situation* only, visualize it with
-            an optional diagram <optional-diagram/> by invoking the
-            `ase-meta-diagram` skill via the `Skill` tool. For *current vs.
-            proposed* comparisons, render each side as a *separate*
-            `ase-meta-diagram` invocation and stack the rendered blocks
-            *vertically* (labels `**Before:**` / `**After:**`); never
-            side-by-side. Omit <optional-diagram/> entirely for simple or
-            purely local situation.
+        -   In case of a *complex refactoring situation* only,
+            visualize it with an optional diagram <optional-diagram/>
+            by building a Mermaid specification <mermaid-spec/>
+            (e.g. `flowchart TB`, `stateDiagram-v2`, `sequenceDiagram`,
+            `classDiagram`, or `erDiagram`, depending on intent) and
+            invoking the `ase-meta-diagram` skill by calling the tool
+            `Skill(skill: "ase:ase-meta-diagram", args: <mermaid-spec/>)`.
+            For *current vs. proposed* comparisons, render each side as
+            a *separate* `ase-meta-diagram` invocation and stack the
+            rendered blocks *vertically* (labels `**Before:**` /
+            `**After:**`); never side-by-side. Omit <optional-diagram/>
+            entirely for simple or purely local situation.
 
 5.  **Choose Refactoring Approach**:
 

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

@@ -11,7 +11,7 @@ allowed-tools:
     - "Skill"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
@@ -150,7 +150,11 @@ permitted way to persist artifacts is via `task_save(...)`.
           transitions, etc), complex *data flow* (actors, messages, etc), or
           complex *data structure* (classes, entities, relationships, etc),
           visualize it with an optional diagram <optional-diagram/> by
-          invoking the `ase-meta-diagram` skill via the `Skill` tool. Omit
+          building a Mermaid specification <mermaid-spec/> (e.g. `flowchart
+          TB`, `stateDiagram-v2`, `sequenceDiagram`, `classDiagram`, or
+          `erDiagram`, depending on intent) and invoking the
+          `ase-meta-diagram` skill by calling the tool `Skill(skill:
+          "ase:ase-meta-diagram", args: <mermaid-spec/>)`. Omit
           <optional-diagram/> entirely for simple or purely local situation.
 
 2.  **Investigate Code Base**:
@@ -243,14 +247,18 @@ permitted way to persist artifacts is via `task_save(...)`.
             or unexpected* errors, they *should* be handled in parent scopes to
             avoid cluttering the source code with too much error handling at all.
 
-        -   In case of a *complex resolution situation* only, visualize it with
-            an optional diagram <optional-diagram/> by invoking the
-            `ase-meta-diagram` skill via the `Skill` tool. For *current vs.
-            proposed* comparisons, render each side as a *separate*
-            `ase-meta-diagram` invocation and stack the rendered blocks
-            *vertically* (labels `**Before:**` / `**After:**`); never
-            side-by-side. Omit <optional-diagram/> entirely for simple or
-            purely local situation.
+        -   In case of a *complex resolution situation* only,
+            visualize it with an optional diagram <optional-diagram/>
+            by building a Mermaid specification <mermaid-spec/>
+            (e.g. `flowchart TB`, `stateDiagram-v2`, `sequenceDiagram`,
+            `classDiagram`, or `erDiagram`, depending on intent) and
+            invoking the `ase-meta-diagram` skill by calling the tool
+            `Skill(skill: "ase:ase-meta-diagram", args: <mermaid-spec/>)`.
+            For *current vs. proposed* comparisons, render each side as
+            a *separate* `ase-meta-diagram` invocation and stack the
+            rendered blocks *vertically* (labels `**Before:**` /
+            `**After:**`); never side-by-side. Omit <optional-diagram/>
+            entirely for simple or purely local situation.
 
 5.  **Choose Problem Resolution Approach**:
 

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

@@ -14,7 +14,7 @@ allowed-tools:
     - "Edit"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Update ChangeLog Entries

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

@@ -18,7 +18,7 @@ allowed-tools:
     - "Agent"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Query Foreign LLMs for Chat

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

@@ -10,7 +10,7 @@ allowed-tools:
     - "Bash(git diff *)"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Git Commit

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

@@ -11,7 +11,7 @@ disable-model-invocation: false
 effort: high
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Evaluate Alternatives
@@ -152,13 +152,16 @@ multi-*criteria* decision matrix.
         from { -2, -1, 0, +1, +2 } (from worst, over neutral, to best). Do
         not output anything.
 
-    -   Then, for each alternative <alternative-K/> (K=1-N), calculate a
-        rating <rating-K/> (K=1-N) which is the product-sum of all weights
-        <weight-L/> (L=1-M) and the evaluation <eval-K-L/> (K=1-N, L=1-M).
-        The result is always a numerical value. Retain the *raw, unrounded*
-        <rating-K/> for use in STEP 5, but round <rating-K/> to 2 decimal
-        places *for display only* when emitting it in the table below. Do
-        not output anything.
+    -   Then, calculate the ratings <rating-K/> (K=1-N) for all
+        alternatives in a single call by invoking the `decision_matrix(matrix:
+        [ [ <weight-1/>, <eval-1-1/>, ..., <eval-1-N/> ], ..., [ <weight-M/>,
+        <eval-M-1/>, ..., <eval-M-N/> ] ])` tool of the `ase` MCP service.
+        The tool returns an array of N numerical values, where the K-th
+        entry is the product-sum of all weights <weight-L/> (L=1-M) and
+        the evaluation <eval-K-L/> (L=1-M) for alternative <alternative-K/>.
+        Retain the *raw, unrounded* <rating-K/> for use in STEP 5, but
+        round <rating-K/> to 2 decimal places *for display only* when
+        emitting it in the table below. Do not output anything.
 
     -   Output the resulting *Weighted Decision Matrix* as a Markdown
         *table* with just the following <template/> and do not output

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

@@ -49,4 +49,5 @@ Persona Configuration
 Apply Persona
 -------------
 
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md

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

@@ -11,7 +11,7 @@ allowed-tools:
     - "TaskCreate"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Query Multiple AIs for Quorum Answer

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

@@ -15,7 +15,7 @@ allowed-tools:
     - "Task"
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Search the Internet/Web

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

@@ -8,7 +8,7 @@ disable-model-invocation: false
 effort: medium
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Five-Whys Root-Cause Analysis

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

@@ -10,7 +10,7 @@ disable-model-invocation: false
 effort: low
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Delete a Task Plan

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

@@ -12,7 +12,7 @@ disable-model-invocation: false
 effort: high
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
@@ -344,8 +344,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
         -   If <result/> is `IMPLEMENT`:
 
             *Break* out of the *loop*, only output the following
-            <template/> and then use the `Skill` tool to invoke the
-            `ase:ase-task-implement` skill in order to *apply* the finalized
+            <template/> and then call the `Skill(skill:
+            "ase:ase-task-implement")` tool to *apply* the finalized
             plan.
 
             <template>
@@ -355,8 +355,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
         -   If <result/> is `PREFLIGHT`:
 
             *Break* out of the *loop*, only output the following
-            <template/> and then use the `Skill` tool to invoke the
-            `ase:ase-task-preflight` skill in order to *apply* the finalized
+            <template/> and then call the `Skill(skill:
+            "ase:ase-task-preflight")` tool to *apply* the finalized
             plan.
 
             <template>
@@ -412,3 +412,4 @@ explicitly requested by this procedure via outputs based on a <template/>!
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan refinement cancelled**
             </template>
+

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

@@ -10,7 +10,7 @@ disable-model-invocation: false
 effort: low
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 Task Configuration

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

@@ -10,7 +10,7 @@ disable-model-invocation: false
 effort: xhigh
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
@@ -149,10 +149,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `DELETE`:
-            Only output the following <template/> and then use the
-            `Skill` tool to invoke the `ase:ase-task-delete` skill in
-            order to *delete* the updated plan. Immediately stop
-            processing the current skill once the `Skill` tool was used.
+            Only output the following <template/> and then call the
+            tool `Skill(skill: "ase:ase-task-delete")` to invoke the
+            `ase:ase-task-delete` skill in order to *delete* the updated
+            plan. Immediately stop processing the current skill once the
+            `Skill` tool was used.
 
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented -- hand-off to delete task**

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

@@ -9,7 +9,7 @@ disable-model-invocation: false
 effort: low
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 

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

@@ -10,7 +10,7 @@ disable-model-invocation: false
 effort: xhigh
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
@@ -172,20 +172,22 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `EDIT`:
-            Only output the following <template/> and then use the
-            `Skill` tool to invoke the `ase:ase-task-edit` skill
-            in order to *edit* the updated plan. Immediately stop
-            processing the current skill once the `Skill` tool was used.
+            Only output the following <template/> and then call the
+            tool `Skill(skill: "ase:ase-task-edit")` to invoke the
+            `ase:ase-task-edit` skill in order to *edit* the updated
+            plan. Immediately stop processing the current skill once the
+            `Skill` tool was used.
 
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to edit**
             </template>
 
         -   If <result/> is `IMPLEMENT`:
-            Only output the following <template/> and then use the
-            `Skill` tool to invoke the `ase:ase-task-implement` skill
-            in order to *implement* the updated plan. Immediately stop
-            processing the current skill once the `Skill` tool was used.
+            Only output the following <template/> and then call the
+            tool `Skill(skill: "ase:ase-task-implement")` to invoke the
+            `ase:ase-task-implement` skill in order to *implement* the
+            updated plan. Immediately stop processing the current skill
+            once the `Skill` tool was used.
 
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implement**

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

@@ -10,7 +10,7 @@ disable-model-invocation: false
 effort: xhigh
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
@@ -164,10 +164,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `EDIT`:
-            Only output the following <template/> and then use the
-            `Skill` tool to invoke the `ase:ase-task-edit` skill
-            in order to *edit* the updated plan. Immediately stop
-            processing the current skill once the `Skill` tool was used.
+            Only output the following <template/> and then call the
+            tool `Skill(skill: "ase:ase-task-edit")` to invoke the
+            `ase:ase-task-edit` skill in order to *edit* the updated
+            plan. Immediately stop processing the current skill once the
+            `Skill` tool was used.
 
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to edit**

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

@@ -10,7 +10,7 @@ disable-model-invocation: false
 effort: low
 ---
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
 View a Task Plan