@rse/ase 0.0.55 → 0.0.57

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-preflight
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>] [<id>]"
 description: >
     Preflight the implementation of current or given task plan.
     Use when the user calls to "preflight", "dry-run" or "test-drive"
@@ -15,9 +15,6 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Preflight a Task Plan
-=====================
-
 <skill name="ase-task-preflight">
 Preflight a Task Plan
 </skill>
@@ -28,13 +25,10 @@ Preflight a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *implementation* of changes.
-</role>
-
+<objective>
 *Preflight* the implementation of a task plan by creating a draft
 for a corresponding, *complete source code change set*.
+</objective>
 
 Procedure
 ---------
@@ -59,8 +53,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <ase-task-id><instruction/></ase-task-id> (set task
             id to instruction) and <instruction></instruction> (set
-            instruction empty), call the `ase_task_id(id: <ase-task-id/>,
-            session: <ase-session-id/>)` tool from the `ase` MCP
+            instruction empty), call the `ase_task_id(id: "<ase-task-id/>",
+            session: "<ase-session-id/>")` tool from the `ase` MCP
             server to switch the task, and then only output the
             following <template/>:
 
@@ -76,8 +70,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <instruction></instruction> (set instruction to empty)
             and <ase-task-id><id/></ase-task-id> (set task id to
-            id) and call the `ase_task_id(id: <ase-task-id/>, session:
-            <ase-session-id/>)` tool from the `ase` MCP server to
+            id) and call the `ase_task_id(id: "<ase-task-id/>", session:
+            "<ase-session-id/>")` tool from the `ase` MCP server to
             switch the task, and then only output the following
             <template/>:
 
@@ -86,13 +80,30 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
             </if>
 
+        3.  else <if 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/>
+            and then immediately *STOP* processing the entire current skill:
+
+            <template>
+            ⧉ **ASE**: ☻ skill: **ase-task-preflight**, ▶ ERROR: expected single `[<id>]` argument
+            </template>
+            </if>
+
 2.  **Determine Operation:**
 
-    1.  Call the `ase_task_load(id: <ase-task-id/>)` tool of the `ase` MCP
-        server to load the current task plan content and set <content/> to
+    1.  Call the `ase_task_load(id: "<ase-task-id/>")` tool of the `ase` MCP
+        server to load the current task plan content and set <text/> to
         the `text` output field of the `ase_task_load` tool call.
 
-        Calculate the number of words <words/> of <content/>.
+        -   If <text/> starts with `ERROR:` or `WARNING:`:
+            Set <content></content> (set content to empty).
+            Set <words/> to "0".
+
+        -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
+            Set <content><text/></content> (set content to text).
+            Calculate the number of words <words/> of <content/>.
 
         Only output the following <template/>:
 
@@ -136,8 +147,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Do not output anything.
         </if>
 
-    4.  Finally, call the `ase_task_save(id: <ase-task-id/>,
-        text: <content/>)` of the `ase` MCP server to save the updated
+    4.  Finally, call the `ase_task_save(id: "<ase-task-id/>",
+        text: "<content/>")` of the `ase` MCP server to save the updated
         task plan content. Calculate the number of words <words/> of
         <content/>. Do not output anything related to this MCP tool call
         except the following <template/>:

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

@@ -0,0 +1,58 @@
+
+##  NAME
+
+`ase-task-preflight` - Preflight a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-preflight`
+    [`--help`|`-h`]
+    [`--next`|`-n` *option*]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-preflight` skill performs a *preflight* (dry-run,
+test-drive) of the *implementation* of a task plan by creating a
+draft for a corresponding, complete *artifact change set* in
+*unified diff* format. The draft is appended to the task plan as
+a `※ IMPLEMENTATION DRAFT` section (replacing any previous draft).
+No source files are modified.
+
+After the preflight, the user is asked whether to stop, hand
+off to `ase-task-edit`, or hand off to `ase-task-implement`,
+unless `--next` pre-selects this choice.
+
+##  OPTIONS
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step with
+    *option*, which can be either `none` (default, interactive
+    answer required), `DONE` (stop), `EDIT` (hand off to
+    `ase-task-edit`), or `IMPLEMENT` (hand off to
+    `ase-task-implement`).
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task whose plan should be
+    preflighted. If omitted, the *current* task id is used.
+
+##  EXAMPLES
+
+Preflight the current task plan:
+
+```text
+❯ /ase-task-preflight
+```
+
+Preflight a specific task and hand off to implementation when done:
+
+```text
+❯ /ase-task-preflight --next IMPLEMENT hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-implement`, `ase-task-reboot`,
+`ase-task-view`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-reboot
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>] [<id>]"
 description: >
     Reboot the current or given task plan by re-creating it from scratch.
     Use when the user calls to "reboot", "recreate" or "refresh"
@@ -15,9 +15,6 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Reboot a Task Plan
-==================
-
 <skill name="ase-task-reboot">
 Reboot a Task Plan
 </skill>
@@ -28,13 +25,10 @@ Reboot a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *planning* of changes.
-</role>
-
+<objective>
 *Reboot* the task plan by crafting it from scratch,
 based on the existing *WHAT* and *WHY*.
+</objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
 
@@ -56,28 +50,45 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     2.  React on task id:
 
-        <if condition="
-            <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
-        ">
-        Set <ase-task-id><instruction/></ase-task-id> (set task
-        id to instruction) and <instruction></instruction> (set
-        instruction empty), call the `ase_task_id(id: <ase-task-id/>,
-        session: <ase-session-id/>)` tool from the `ase` MCP
-        server to switch the task, and then only output the
-        following <template/>:
+        1.  <if condition="
+                <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+            ">
+            Set <ase-task-id><instruction/></ase-task-id> (set task
+            id to instruction) and <instruction></instruction> (set
+            instruction empty), call the `ase_task_id(id: "<ase-task-id/>",
+            session: "<ase-session-id/>")` tool from the `ase` MCP
+            server to switch the task, and then only output the
+            following <template/>:
 
-        <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
-        </template>
-        </if>
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
+            </template>
+            </if>
+
+        2.  else <if 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/>
+            and then immediately *STOP* processing the entire current skill:
+
+            <template>
+            ⧉ **ASE**: ☻ skill: **ase-task-reboot**, ▶ ERROR: expected single `[<id>]` argument
+            </template>
+            </if>
 
 2.  **Determine Operation:**
 
-    1.  Call the `ase_task_load(id: <ase-task-id/>)` tool of the `ase` MCP
-        server to load the current task plan content and set <content/> to
+    1.  Call the `ase_task_load(id: "<ase-task-id/>")` tool of the `ase` MCP
+        server to load the current task plan content and set <text/> to
         the `text` output field of the `ase_task_load` tool call.
 
-        Calculate the number of words <words/> of <content/>.
+        -   If <text/> starts with `ERROR:` or `WARNING:`:
+            Set <content></content> (set content to empty).
+            Set <words/> to "0".
+
+        -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
+            Set <content><text/></content> (set content to text).
+            Calculate the number of words <words/> of <content/>.
 
         Only output the following <template/>:
 
@@ -104,35 +115,39 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Set <instruction><text/></instruction> (set instruction to extracted text).
         </if>
 
-    4.  <if condition="<content/> contains '- **WHY**: <text/>'">
+    4.  <if condition="<content/> contains '- **WHY**: <text/>' and <instruction/> is empty">
+        Set <instruction><text/></instruction> (set instruction to extracted text).
+        </if>
+
+    5.  else <if condition="<content/> contains '- **WHY**: <text/>' and <instruction/> is NOT empty">
         Set <instruction><instruction/>, BECAUSE <text/></instruction>
         (append extracted text to instruction).
         </if>
 
-    5.  <if condition="<content/> contains 'created: **<text/>**'">
+    6.  <if condition="<content/> contains 'created: **<text/>**'">
         Set <timestamp-created><text/></timestamp-created> (set
         timestamp-created to extracted text)
         </if>
 
-    6.  Create a new plan from scratch and store the result as
+    7.  Create a new plan from scratch and store the result as
         <content/> by closely following the defined plan format
         <format/> and injecting into it all the information from
         the <instruction/> and all decisions you derived from the
         <instruction/>.
 
-    7.  Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+    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
         <ase-task-id/>, previous <timestamp-created/>, and refreshed
         <timestamp-modified/> information and calculate the number of
         words <words/> of <content/>.
 
-    8.  Call the `ase_task_save(id: <ase-task-id/>,
-        text: <content/>)` of the `ase` MCP server to save the updated
+    9.  Call the `ase_task_save(id: "<ase-task-id/>",
+        text: "<content/>")` of the `ase` MCP server to save the updated
         task plan content. Do not output anything related to this MCP
         call.
 
-    9.  Only output the following <template/> and continue processing:
+    10. Only output the following <template/> and continue processing:
 
         <template>
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan rebooted**

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

@@ -0,0 +1,55 @@
+
+##  NAME
+
+`ase-task-reboot` - Reboot a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-reboot`
+    [`--help`|`-h`]
+    [`--next`|`-n` *option*]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-reboot` skill re-creates an existing task plan *from
+scratch* by extracting the original `**WHAT**` and `**WHY**` sections
+(if present) from the current plan, using them as the new instruction,
+preserving the original creation timestamp, and writing a fresh plan
+content via `ase_task_save`.
+
+After the reboot, the user is asked whether to stop or hand off to
+`ase-task-edit`, unless `--next` pre-selects this choice.
+
+##  OPTIONS
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step with
+    *option*, which can be either `none` (default, interactive
+    answer required), `DONE` (stop), or `EDIT` (hand off to
+    `ase-task-edit`).
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task whose plan should be rebooted.
+    If omitted, the *current* task id is used.
+
+##  EXAMPLES
+
+Reboot the current task plan:
+
+```text
+❯ /ase-task-reboot
+```
+
+Reboot a specific task and hand off to editing:
+
+```text
+❯ /ase-task-reboot --next EDIT hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-preflight`, `ase-task-implement`,
+`ase-task-view`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-rename
-argument-hint: "[<old>] <new>"
+argument-hint: "[--help|-h] [<old>] <new>"
 description: >
     Rename the current or given task plan.
     Use when the user calls to "rename", "move" or "relabel" the
@@ -13,18 +13,13 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Rename a Task Plan
-==================
-
 <skill name="ase-task-rename">
 Rename a Task Plan
 </skill>
 
-<role>
-Your role is an experienced, *expert-level assistant*.
-</role>
-
+<objective>
 *Rename* the task plan.
+</objective>
 
 Procedure
 ---------
@@ -64,7 +59,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Perform Operation**:
 
-    1.  Call the `ase_task_rename(old: <old/>, new: <new/>)` tool of the
+    1.  Call the `ase_task_rename(old: "<old/>", new: "<new/>")` tool of the
         `ase` MCP server to rename the task plan and set <text/> to the
         `text` output field of this `ase_task_rename` tool call. Do not
         output anything related to this MCP tool call.
@@ -85,7 +80,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     2.  <if condition="<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`
+        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the `ase`
         MCP server to switch the task to the renamed task. Only output
         the following <template/>:
 

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

@@ -0,0 +1,44 @@
+
+##  NAME
+
+`ase-task-rename` - Rename a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-rename`
+    [`--help`|`-h`]
+    [*old*] *new*
+
+##  DESCRIPTION
+
+The `ase-task-rename` skill renames a *task plan* from *old* to
+*new* via the `ase_task_rename` MCP tool. If only one argument is
+given, it is treated as *new* and *old* defaults to the *current*
+task id. When the renamed task is the current task, the current
+task id is automatically switched to *new*.
+
+##  ARGUMENTS
+
+[*old*] *new*:
+    The *old* task id to rename and the *new* task id to assign.
+    If only one token is given, *old* defaults to the current
+    task id.
+
+##  EXAMPLES
+
+Rename the current task:
+
+```text
+❯ /ase-task-rename hello-world
+```
+
+Rename a specific task:
+
+```text
+❯ /ase-task-rename old-id new-id
+```
+
+##  SEE ALSO
+
+`ase-task-list`, `ase-task-id`, `ase-task-edit`,
+`ase-task-view`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-view
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [<id>]"
 description: >
     View current or given task plan.
     Use when the user calls to "view", "show" or "see" the
@@ -13,17 +13,13 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-View a Task Plan
-================
-
 <skill name="ase-task-view">
 View a Task Plan
 </skill>
 
-<role>
-Your role is an experienced, *expert-level assistant*.
-</role>
+<objective>
 *View* the task plan.
+</objective>
 
 Procedure
 ---------
@@ -36,7 +32,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 1.  **Determine Task:**
 
-    1.  Set <id>$ARGUMENTS</id> initially.
+    1.  Set <id>$ARGUMENTS</id> initially, with any leading and trailing
+        whitespace stripped.
         Inherit the always existing <ase-task-id/> from the current context.
         Do not output anything.
 
@@ -45,9 +42,18 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Do not output anything.
         </if>
 
+    3.  <if condition="<id/> does NOT match the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`">
+        Only output the following <template/> and then immediately
+        *STOP* processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ☻ skill: **ase-task-view**, ▶ ERROR: expected single `[<id>]` argument
+        </template>
+        </if>
+
 2.  **Perform Operation**:
 
-    1.  Call the `ase_task_load(id: <id/>)` tool of the `ase` MCP
+    1.  Call the `ase_task_load(id: "<id/>")` tool of the `ase` MCP
         server to load the task 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.

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

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-task-view` - View a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-view`
+    [`--help`|`-h`]
+    [*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.
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task plan to view. If omitted,
+    the current task id is used.
+
+##  EXAMPLES
+
+View the current task plan:
+
+```text
+❯ /ase-task-view
+```
+
+View a specific task plan:
+
+```text
+❯ /ase-task-view hello
+```
+
+##  SEE ALSO
+
+`ase-task-list`, `ase-task-edit`, `ase-task-id`,
+`ase-task-rename`, `ase-task-delete`.