@rse/ase 0.9.7 → 0.9.9

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

@@ -106,13 +106,15 @@ addressing surface-level symptoms.
 
             Ask <question/> and surface up to <width/> *distinct*,
             *non-overlapping* candidate sub-causes, each documented in <answer-k/>.
+            Let <count/> be the number of candidates you actually surfaced
+            (at least one, at most <width/>).
             Don't stop at symptoms, keep digging for systemic issues.
             Explore *different* candidates -- technical, domain-specific,
             process-related, or organizational causes -- and avoid restating
             the same cause in different words.
 
             Start with <k>1</k> (set candidate counter to one).
-            <while condition="<k/> is less than or equal to <width/>">
+            <while condition="<k/> is less than or equal to <count/>">
                 <template>
                 <ase-tpl-bullet-secondary/> **WHY <n/>.<k/>**: <answer-k/>
                 </template>
@@ -150,15 +152,19 @@ addressing surface-level symptoms.
     whole chain up to the original <problem/>).
 
     When <width/> is *greater than 1* and this backward validation *fails* at
-    some level -- i.e. the chosen sub-cause does *not* adequately explain the
-    fact above it -- *backtrack*: discard the chosen sub-cause from that level
-    downward, pick the next-best candidate from that level's <fallbacks/>, set
-    <question/> to it, and re-run the STEP 2 widened descent from there. Repeat
-    until a chain survives backward validation or that level's <fallbacks/> are
-    exhausted (then report the strongest chain found and note that no candidate
-    fully validated). This is the payoff of <width/> *greater than 1*: the
-    enumerated alternatives let the analysis *recover* from a wrong turn instead
-    of committing to a mis-rooted chain.
+    some level <m/> -- i.e. the chosen sub-cause does *not* adequately explain
+    the fact above it -- *backtrack*: discard the chosen sub-cause (and every
+    chosen sub-cause below it) from level <m/> downward, pick the next-best
+    candidate from level <m/>'s <fallbacks/>, and resume the STEP 2 widened
+    descent: set <n/> to <m/> (reset the iteration counter to the failed level),
+    set <question/> to the picked candidate, and re-enter STEP 2's
+    <while condition="<n/> is less than or equal to <depth/>"/> loop at that
+    level -- so the original <depth/> budget is honored from <m/> downward.
+    Repeat until a chain survives backward validation or level <m/>'s
+    <fallbacks/> are exhausted (then report the strongest chain found and note
+    that no candidate fully validated). This is the payoff of <width/> *greater
+    than 1*: the enumerated alternatives let the analysis *recover* from a wrong
+    turn instead of committing to a mis-rooted chain.
 
     Propose a solution that addresses and solves the validated root-cause.
     For the proposed solution, optionally directly propose corresponding source code changes.

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

@@ -77,4 +77,4 @@ committing early to the wrong root-cause:
 
 ##  SEE ALSO
 
-`ase-code-analyze`, `ase-code-resolve`, `ase-arch-analyze`.
+[`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).

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

@@ -65,7 +65,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
             </if>
 
-        2.  else <if condition="<instruction/> is NOT empty">
+        2.  <elseif condition="<instruction/> 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/>
@@ -74,7 +74,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             <template>
             ⧉ **ASE**: ☻ skill: **ase-task-condense**, ▶ ERROR: expected single `[<id>]` argument
             </template>
-            </if>
+            </elseif>
 
 2.  **Determine Operation:**
 
@@ -114,9 +114,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
         and unchanged*. Honor the following ruleset *strictly*:
 
         1.  *Preserve-exactly (never alter)*: the plan <format/>
-            structure (the headings `#`/`##`, the `※`/`◉`/`✪` markers,
-            all three `## ※ CONTEXT`, `## ※ CHANGES`, and `## ※
-            VERIFICATION` sections, the `created:`/`modified:` line, and
+            structure (the headings `#`/`##`, all three `##  CONTEXT`,
+            `##  CHANGES`, and `##  VERIFICATION` sections, the
+            `Created:`/`Modified:` lines, and
             the `- **<aspect/>**:` bullet labels), all *code spans* and
             code blocks, technical terms, file paths, identifiers,
             numbers, severities (`LOW`/`MEDIUM`/`HIGH`/`ACCEPTED`), and
@@ -203,9 +203,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
                 </template>
 
         -   If <getopt-option-next/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next step.
+            Let the *user interactively choose* what to do as the next
+            step. For this you *MUST* use the custom `custom-dialog` and
+            *NOT* the `AskUserQuestion` based "user-dialog":
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog">
                 Next Step: How would you like to proceed with the plan?
                 DONE: Stop processing.
                 EDIT: Hand off plan to editing.
@@ -223,13 +225,15 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `EDIT`:
-            Set <args></args> (empty).
+            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>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Only output the following <template/> and then call the
-            tool `Skill(skill: "ase:ase-task-edit", args: <args/>)`
+            tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`
             to invoke the `ase:ase-task-edit` skill in order to *edit*
             the condensed plan. Immediately stop processing the current
             skill once the `Skill` tool was used.
@@ -239,13 +243,15 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `IMPLEMENT`:
-            Set <args></args> (empty).
+            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>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Only output the following <template/> and then call the
-            `Skill(skill: "ase:ase-task-implement", args: <args/>)` tool
+            `Skill(skill: "ase:ase-task-implement", args: "<args/>")` tool
             to *apply* the plan.
 
             <template>
@@ -253,15 +259,26 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `PREFLIGHT`:
-            Set <args></args> (empty).
+            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>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Only output the following <template/> and then call the
-            `Skill(skill: "ase:ase-task-preflight", args: <args/>)` tool
+            `Skill(skill: "ase:ase-task-preflight", args: "<args/>")` tool
             to *apply* the plan.
 
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan condensed -- hand-off to pre-flight**
             </template>
+
+        -   If <result/> matches `OTHER: <text/>` or is any other
+            unrecognized value:
+            Treat it as `DONE` (the condensed plan is already saved):
+            only output the following <template/> and then *STOP*.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan condensed -- done**
+            </template>

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

@@ -30,7 +30,7 @@ telegrapher-like even under the `writer` persona.
 
 The plan is saved *only* when condensing actually makes it smaller; if no
 further reduction is possible, the plan is left untouched (including its
-`✎ modified:` timestamp) and reported as *already condensed*.
+`⚙   Modified:` timestamp) and reported as *already condensed*.
 
 After condensing, the user is asked whether to stop or hand off to
 `ase-task-edit`, `ase-task-implement`, or `ase-task-preflight`, unless
@@ -73,5 +73,5 @@ Condense a specific task and hand off to editing:
 
 ##  SEE ALSO
 
-`ase-task-edit`, `ase-task-reboot`, `ase-task-view`,
-`ase-task-rename`, `ase-task-delete`.
+[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md), [`ase-task-view`](../ase-task-view/help.md),
+[`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).

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

@@ -35,6 +35,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
     1.  Set <id>$ARGUMENTS</id> initially, with any leading and trailing
         whitespace stripped.
         Inherit the always existing <ase-task-id/> from the current context.
+        Inherit the always existing <ase-session-id/> from the current context.
         Do not output anything.
 
     2.  <if condition="<id/> is empty">
@@ -59,20 +60,22 @@ explicitly requested by this procedure via outputs based on a <template/>!
         output anything related to this MCP tool call.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
-            Only output the following <template/>:
+            Set <deleted>false</deleted> and only output the following
+            <template/>:
 
             <template>
             ⧉ **ASE**: ◉ task: **<id/>**, ▶ status: **<text/>**
             </template>
 
         -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
-            Only output the following <template/>:
+            Set <deleted>true</deleted> and only output the following
+            <template/>:
 
             <template>
             ⧉ **ASE**: ◉ task: **<id/>**, ▶ status: **task deleted**
             </template>
 
-    2.  <if condition="<id/> is equal <ase-task-id/> AND <ase-task-id/> is not equal 'default'">
+    2.  <if condition="<deleted/> is equal 'true' AND <id/> is equal <ase-task-id/> AND <ase-task-id/> is not equal 'default'">
         Set <ase-task-id>default</ase-task-id>. Call the `ase_task_id(id:
         "<ase-task-id/>", session: "<ase-session-id/>")` tool from the `ase`
         MCP server to switch the task to the default task. Only output

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

@@ -39,5 +39,5 @@ Delete a specific task plan:
 
 ##  SEE ALSO
 
-`ase-task-edit`, `ase-task-list`, `ase-task-view`,
-`ase-task-rename`, `ase-task-reboot`.
+[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-list`](../ase-task-list/help.md), [`ase-task-view`](../ase-task-view/help.md),
+[`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md).

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

@@ -23,7 +23,7 @@ Iteratively Edit a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-edit"
-    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --dry|-d --next|-n=(none|DONE|GRILL|PREFLIGHT|IMPLEMENT)...">
+    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --dry|-d --next|-n=(none|DONE|GRILL|PREFLIGHT|IMPLEMENT)... --int-reuse-task">
     $ARGUMENTS
 </expand>
 
@@ -67,7 +67,7 @@ the <instruction/> and all decisions you derived from the
 
 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
+its `##  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.
@@ -111,7 +111,7 @@ Set <content-dirty>true</content-dirty>.
             </template>
             </if>
 
-        2.  else <if condition="
+        2.  <elseif condition="
                 <instruction/> has the format `<id/>: <text/>` where
                 <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$` and
                 <text/> is *empty*
@@ -126,9 +126,9 @@ Set <content-dirty>true</content-dirty>.
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
             </template>
-            </if>
+            </elseif>
 
-        3.  else <if condition="
+        3.  <elseif condition="
                 <instruction/> has the format `<id/>: <text/>` where
                 <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$` and
                 <text/> is *not empty*
@@ -144,9 +144,9 @@ Set <content-dirty>true</content-dirty>.
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
             </template>
-            </if>
+            </elseif>
 
-        4.  else <if condition="
+        4.  <elseif condition="
                 <instruction/> is not empty
             ">
             Only output the following <template/>:
@@ -155,9 +155,9 @@ Set <content-dirty>true</content-dirty>.
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task inherited**
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
             </template>
-            </if>
+            </elseif>
 
-        5.  else <if condition="
+        5.  <elseif condition="
                 <instruction/> is empty
             ">
             Only output the following <template/>:
@@ -165,14 +165,26 @@ Set <content-dirty>true</content-dirty>.
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task inherited**
             </template>
-            </if>
+            </elseif>
 
 2.  **Determine Plan:**
 
-    1.  Call the `ase_task_load(id: "<ase-task-id/>")` tool of the `ase` MCP
-        server to load any existing plan content and set <text/> to
-        the `text` output field of this `ase_task_load` tool call.
-        Do not output anything related to this MCP tool call.
+    1.  Determine any existing plan content:
+
+        <if condition="<getopt-option-int-reuse-task/> is equal `true`">
+            Set <text/> to the `text` argument of the most recent
+            `ase_task_save(id: '<ase-task-id/>', ...)` tool call,
+            *without* calling `ase_task_load` again. Set <status>plan
+            reused</status>. Do not output anything.
+        </if>
+        <else>
+            Call the `ase_task_load(id: "<ase-task-id/>")` tool of the
+            `ase` MCP server to load any existing plan content and set
+            <text/> to the `text` output field of this `ase_task_load`
+            tool call. Do not output anything related to this MCP tool
+            call. Set <status>plan loaded</status>.
+        </else>
+
         Set <content-dirty>false</content-dirty>.
 
         -   If <text/> starts with `ERROR:`:
@@ -187,7 +199,7 @@ Set <content-dirty>true</content-dirty>.
             Only output the following <template/>:
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan loaded**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<status/>**
             </template>
 
     2.  <if condition="<content/> is empty AND <instruction/> is empty">
@@ -214,9 +226,11 @@ Set <content-dirty>true</content-dirty>.
             Set <result><getopt-option-plan/></result>.
 
         -   If <getopt-option-plan/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next step.
+            Let the *user interactively choose* what to do as the next
+            step. For this you *MUST* use the custom `custom-dialog` and
+            *NOT* the `AskUserQuestion` based "user-dialog":
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog">
                 Previous Plan: Should the previous plan content be overwritten, refined, or preserved?
                 OVERWRITE: Continue operation, overwrite previous plan.
                 REFINE: Continue operation, refine previous plan.
@@ -271,7 +285,7 @@ Set <content-dirty>true</content-dirty>.
             </template>
         </if>
 
-    4.  <if condition="<content/> does not contain '# ✪ TASK' AND <instruction/> is empty">
+    4.  <if condition="<content/> does not contain '#   TASK' AND <instruction/> is empty">
         Set <instruction><content/></instruction> (set instruction to content).
         Set <content></content> (set content to empty).
         Set <content-dirty>true</content-dirty>.
@@ -296,12 +310,12 @@ Set <content-dirty>true</content-dirty>.
     `PREFLIGHT`, or declines/cancels in the dialog of step 3.4:
 
     1.  *Update timestamp*:
-        <if condition="<content/> contains '✎ modified:' AND <content-dirty/> is 'true'">
+        <if condition="<content/> contains '⚙   Modified:' AND <content-dirty/> is 'true'">
         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. Update
-        <content/> with the new `✎ modified: **<timestamp-modified/>**`.
+        <content/> with the new `Modified: <timestamp-modified/>`.
         Do not output anything.
         </if>
 
@@ -350,8 +364,8 @@ Set <content-dirty>true</content-dirty>.
                 Set <instruction></instruction> (clear the instruction, as
                 any instruction carried in via the arguments was already
                 applied to the plan in step 2 before this loop), so that a
-                pre-selected `REFINE` correctly asks the user for a *fresh*
-                refinement instruction below.
+                later `OTHER: <text/>` refinement correctly starts from a
+                *fresh* refinement instruction below.
 
             -   else:
                 Only output the following <template/> and then immediately
@@ -362,9 +376,11 @@ Set <content-dirty>true</content-dirty>.
                 </template>
 
         -   If <getopt-option-next/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next step.
+            Let the *user interactively choose* what to do as the next
+            step. For this you *MUST* use the custom `custom-dialog` and
+            *NOT* the `AskUserQuestion` based "user-dialog":
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog">
                 Next Step: How would you like to proceed with the plan?
                 DONE: Mark plan finalized, exit planning loop.
                 GRILL: Hand off plan to grilling.
@@ -385,13 +401,16 @@ Set <content-dirty>true</content-dirty>.
 
         -   If <result/> is `GRILL`:
 
-            *Break* out of the *loop*. Set <args></args> (empty).
+            *Break* out of the *loop*.
+            Set <args></args> (set args to empty).
+            <if condition="the plan was saved via `ase_task_save` in step 3.2">
+                Set <args>--int-reuse-task</args>.
+            </if>
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Only output the following <template/> and then call the
-            `Skill(skill: "ase:ase-task-grill", args: <args/>)` tool
+            `Skill(skill: "ase:ase-task-grill", args: "<args/>")` tool
             to *grill* the finalized plan.
 
             <template>
@@ -400,13 +419,16 @@ Set <content-dirty>true</content-dirty>.
 
         -   If <result/> is `PREFLIGHT`:
 
-            *Break* out of the *loop*. Set <args></args> (empty).
+            *Break* out of the *loop*.
+            Set <args></args> (set args to empty).
+            <if condition="the plan was saved via `ase_task_save` in step 3.2">
+                Set <args>--int-reuse-task</args>.
+            </if>
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Only output the following <template/> and then call the
-            `Skill(skill: "ase:ase-task-preflight", args: <args/>)` tool
+            `Skill(skill: "ase:ase-task-preflight", args: "<args/>")` tool
             to *apply* the finalized plan.
 
             <template>
@@ -415,13 +437,16 @@ Set <content-dirty>true</content-dirty>.
 
         -   If <result/> is `IMPLEMENT`:
 
-            *Break* out of the *loop*. Set <args></args> (empty).
+            *Break* out of the *loop*.
+            Set <args></args> (set args to empty).
+            <if condition="the plan was saved via `ase_task_save` in step 3.2">
+                Set <args>--int-reuse-task</args>.
+            </if>
             <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
+                Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Only output the following <template/> and then call the
-            `Skill(skill: "ase:ase-task-implement", args: <args/>)` tool
+            `Skill(skill: "ase:ase-task-implement", args: "<args/>")` tool
             to *apply* the finalized plan.
 
             <template>

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

@@ -48,8 +48,8 @@ hand-off to implementation or preflight.
     `none` (default, interactive answer required), `DONE` (no next
     step), `GRILL` (hand-over to `ase-task-grill`), `PREFLIGHT`
     (hand-over to `ase-task-preflight`), or `IMPLEMENT` (hand-over to
-    `ase-task-implement`). Example: `--next GRILL,DONE` first refines
-    once, then exits the loop without asking.
+    `ase-task-implement`). Example: `--next GRILL,DONE` hands the plan
+    off to grilling and forwards `DONE` so grilling exits without asking.
 
 ##  ARGUMENTS
 
@@ -82,5 +82,5 @@ Further refine the task under id `hello`:
 
 ##  SEE ALSO
 
-`ase-task-reboot`, `ase-task-preflight`, `ase-task-implement`,
-`ase-task-view`, `ase-task-list`, `ase-task-rename`, `ase-task-delete`.
+[`ase-task-reboot`](../ase-task-reboot/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-implement`](../ase-task-implement/help.md),
+[`ase-task-view`](../ase-task-view/help.md), [`ase-task-list`](../ase-task-list/help.md), [`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).