@rse/ase 0.9.7 → 0.9.9

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

@@ -21,7 +21,7 @@ Reboot a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-reboot"
-    arg2="--next|-n=(none|DONE|EDIT)...">
+    arg2="--next|-n=(none|DONE|EDIT|IMPLEMENT|PREFLIGHT)...">
     $ARGUMENTS
 </expand>
 
@@ -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-reboot**, ▶ ERROR: expected single `[<id>]` argument
             </template>
-            </if>
+            </elseif>
 
 2.  **Determine Operation:**
 
@@ -119,10 +119,10 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Set <instruction><text/></instruction> (set instruction to extracted text).
         </if>
 
-    5.  else <if condition="<content/> contains '-   **WHY**: <text/>' and <instruction/> is NOT empty">
+    5.  <elseif condition="<content/> contains '-   **WHY**: <text/>' and <instruction/> is NOT empty">
         Set <instruction><instruction/>, BECAUSE <text/></instruction>
         (append extracted text to instruction).
-        </if>
+        </elseif>
 
     6.  <if condition="<content/> contains 'Created:  <text/>'">
         Set <timestamp-created><text/></timestamp-created> (set
@@ -137,7 +137,10 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     8.  Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
         `ase` MCP server and use the `text` field of its response for
-        <timestamp-modified/> information. Then insert the current
+        <timestamp-modified/> information. If <timestamp-created/> is
+        still unset (because the previous <content/> had no `Created:`
+        line), set <timestamp-created><timestamp-modified/></timestamp-created>
+        (fall back to the modified timestamp). Then insert the current
         <ase-task-id/>, previous <timestamp-created/>, and refreshed
         <timestamp-modified/> information and calculate the number of
         words <words/> of <content/>.
@@ -178,9 +181,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.
@@ -198,13 +203,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `EDIT`:
-            Set <args></args> (empty).
+            Set <args>--int-reuse-task</args>.
             <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 updated plan. Immediately stop processing the current
             skill once the `Skill` tool was used.
@@ -214,13 +218,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `IMPLEMENT`:
-            Set <args></args> (empty).
+            Set <args>--int-reuse-task</args>.
             <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>
@@ -228,16 +231,24 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `PREFLIGHT`:
-            Set <args></args> (empty).
+            Set <args>--int-reuse-task</args>.
             <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 updated -- hand-off to pre-flight**
             </template>
 
+        -   If <result/> matches `OTHER: <text/>` or is any other
+            unrecognized value:
+            Treat it as `DONE` (the updated plan is already saved):
+            only output the following <template/> and then *STOP*.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- done**
+            </template>
+

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

@@ -58,5 +58,5 @@ Reboot a specific task and hand off to editing:
 
 ##  SEE ALSO
 
-`ase-task-edit`, `ase-task-preflight`, `ase-task-implement`,
-`ase-task-view`, `ase-task-delete`.
+[`ase-task-edit`](../ase-task-edit/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-delete`](../ase-task-delete/help.md).

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

@@ -33,8 +33,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
 1.  **Determine Task:**
 
     1.  Parse <arguments>$ARGUMENTS</arguments> into a whitespace-separated
-        list of tokens. Inherit the always existing <ase-task-id/> from
-        the current context. Do not output anything.
+        list of tokens. Inherit the always existing <ase-task-id/> and
+        <ase-session-id/> from the current context. Do not output anything.
 
     2.  <if condition="<arguments/> contains two tokens">
         Set <old/> to the first token of <arguments/>.
@@ -65,6 +65,7 @@ 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:`:
+            Set <renamed/> to `false`.
             Only output the following <template/>:
 
             <template>
@@ -72,13 +73,14 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
+            Set <renamed/> to `true`.
             Only output the following <template/>:
 
             <template>
             ⧉ **ASE**: ◉ task: **<new/>**, ▶ status: **task renamed**
             </template>
 
-    2.  <if condition="<old/> is equal <ase-task-id/>">
+    2.  <if condition="<renamed/> is `true` AND <old/> is equal <ase-task-id/>">
         Set <ase-task-id><new/></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 renamed task. Only output

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

@@ -40,5 +40,5 @@ Rename a specific task:
 
 ##  SEE ALSO
 
-`ase-task-list`, `ase-task-id`, `ase-task-edit`,
-`ase-task-view`, `ase-task-delete`.
+[`ase-task-list`](../ase-task-list/help.md), [`ase-task-id`](../ase-task-id/help.md), [`ase-task-edit`](../ase-task-edit/help.md),
+[`ase-task-view`](../ase-task-view/help.md), [`ase-task-delete`](../ase-task-delete/help.md).

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

@@ -7,15 +7,28 @@
 
 `ase-task-view`
     [`--help`|`-h`]
+    [`--full`|`-f`]
     [*id*]
 
 ##  DESCRIPTION
 
-The `ase-task-view` skill renders the *task plan* identified by *id*
-in full, without truncation or summarization. The plan is loaded via
-the `ase_task_load` MCP tool and shown between `TASK-PLAN-BEGIN` and
-`TASK-PLAN-END` markers. If *id* is omitted, the *current* task id
-(inherited from the session context) is used.
+The `ase-task-view` skill renders the *task plan* identified by *id*.
+The plan is loaded via the `ase_task_load` MCP tool and shown framed
+between a `( TASK )` header and footer rule. If *id* is omitted, the
+*current* task id (inherited from the session context) is used.
+
+By default, when the plan is longer than 90 lines and contains an
+`IMPLEMENTATION DRAFT` section (produced by `ase-task-preflight`), the
+content of that section is collapsed to `[...]` to keep the view
+compact. The `--full`|`-f` option suppresses this collapsing and renders
+the plan in full, without any truncation or summarization.
+
+##  OPTIONS
+
+`--full`|`-f`:
+    Render the plan in full, without collapsing the `IMPLEMENTATION
+    DRAFT` section. By default, that section is replaced with `[...]`
+    for plans longer than 90 lines.
 
 ##  ARGUMENTS
 
@@ -37,7 +50,13 @@ View a specific task plan:
 ❯ /ase-task-view hello
 ```
 
+View a plan in full, including its `IMPLEMENTATION DRAFT` section:
+
+```text
+❯ /ase-task-view --full hello
+```
+
 ##  SEE ALSO
 
-`ase-task-list`, `ase-task-edit`, `ase-task-id`,
-`ase-task-rename`, `ase-task-delete`.
+[`ase-task-list`](../ase-task-list/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-id`](../ase-task-id/help.md),
+[`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).