@rse/ase 0.0.55 → 0.0.57

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

@@ -0,0 +1,47 @@
+
+##  NAME
+
+`ase-task-delete` - Delete a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-delete`
+    [`--help`|`-h`]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-delete` skill deletes the *task plan* identified by
+*id*. If *id* is omitted, the *current* task id (inherited from the
+session context) is used. When the deleted task is the current task
+and not the `default` task, the current task id is automatically
+switched back to `default`.
+
+The task plan is stored in `.ase/tasks/`*id*`/plan.md` files of the
+project and can be alternatively deleted with the
+"`ase task delete` *id*" command from outside the agent tool.
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task plan to delete. If omitted,
+    the current task id is used.
+
+##  EXAMPLES
+
+Delete the current task plan:
+
+```text
+❯ /ase-task-delete
+```
+
+Delete a specific task plan:
+
+```text
+❯ /ase-task-delete hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-list`, `ase-task-view`,
+`ase-task-rename`, `ase-task-reboot`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-edit
-argument-hint: "[<id> | <id>: <instruction> | <instruction>]"
+argument-hint: "[--help|-h] [--plan|-p <option>] [--next|-n <option>] [<id> | <id>: <instruction> | <instruction>]"
 description: >
     Iteratively edit and refine a named plan for a task through a
     conversational loop. Each round, the current plan is shown and the
@@ -17,9 +17,6 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Iteratively Edit a Task Plan
-============================
-
 <skill name="ase-task-edit">
 Iteratively Edit a Task Plan
 </skill>
@@ -30,16 +27,12 @@ Iteratively Edit a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *planning* of changes
-through *iterative conversational refinement*.
-</role>
-
+<objective>
 Establish and refine the *task plan* purely through a *chat-driven
-loop*. The user steers each round via interactive dialog that offers
+loop*. The user steers each round via an interactive dialog that offers
 continued refinement, finalization, or hand-off to implementation or
 preflight.
+</objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
 
@@ -56,6 +49,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     1.  Set <instruction><getopt-arguments/></instruction> initially.
         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.  React on task and/or instruction:
@@ -65,8 +59,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/>:
 
@@ -82,8 +76,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/>:
 
@@ -99,8 +93,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <instruction><text/></instruction> (set instruction to
             text) 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
+            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/>:
 
@@ -133,7 +127,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Determine Plan:**
 
-    1.  Call the `ase_task_load(id: <ase-task-id/>)` tool of the `ase` MCP
+    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.
@@ -235,6 +229,28 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
             Only output the following <template/> and continue processing:
 
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan refined**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
+            </template>
+
+        -   If <result/> matches `OTHER: <text/>`:
+
+            Set <instruction><instruction/> <text/></instruction> (append
+            the user's free-text hint to the existing instruction).
+
+            Treat the <instruction/> as a *refinement instruction* for
+            the plan, and update <content/> in-place by *applying* the
+            requested <instruction/> to the *plan*. When refining the
+            plan this way, preserve the overall structure of the plan
+            and only modify what the user actually requested. Do *not*
+            rewrite unrelated sections of the plan.
+
+            Calculate the number of words <words/> of <content/>.
+            Set <content-dirty>true</content-dirty>.
+
+            Only output the following <template/> and continue processing:
+
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan refined**
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
@@ -273,9 +289,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 3.  **Iterative Plan Refinement Loop:**
 
-    *REPEAT* the following steps 3.1 to 3.4 in a *LOOP* until
-    the user selects `DONE`, `IMPLEMENT`, or `PREFLIGHT`, or
-    declines/cancels in the dialog of step 3.4:
+    *REPEAT* the following steps from 3.1 up to and including 3.4 in a
+    *LOOP* until the user selects `DONE`, `IMPLEMENT`, or `PREFLIGHT`,
+    or declines/cancels in the dialog of step 3.4:
 
     1.  *Update timestamp*:
         <if condition="<content/> contains '✎ modified:' AND <content-dirty/> is 'true'">
@@ -289,7 +305,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     2.  *Persist plan*:
         <if condition="<content-dirty/> is 'true'">
-        Call the `ase_task_save(id: <ase-task-id/>, text: <content/>)` tool
+        Call the `ase_task_save(id: "<ase-task-id/>", text: "<content/>")` tool
         of the `ase` MCP server to persist the current plan, and then
         set <content-dirty>false</content-dirty> again. Calculate the
         number of words <words/> of <content/>. Do not output anything
@@ -301,11 +317,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </if>
 
     3.  *Render plan*: Only output the following <template/>, so the user
-        can read the plan and react to it. If <content/> is longer than
-        90 lines and a `※ IMPLEMENTATION DRAFT` section exists, replace
-        the entire content of the `※ IMPLEMENTATION DRAFT` section with
-        `[...]`. Else, do *not* truncate, summarize, or partially show
-        the plan. Use the following <template/>:
+        can read the plan and react to it. If <content/> is longer
+        than 90 lines and a `※ IMPLEMENTATION DRAFT` section (from the
+        companion skill `ase-task-preflight`) exists, replace the entire
+        content of the `※ IMPLEMENTATION DRAFT` section with `[...]`.
+        Else, do *not* truncate, summarize, or partially show the plan.
+        Use the following <template/>:
 
         <template>
         ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(** `TASK-PLAN-BEGIN` **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
@@ -318,8 +335,17 @@ explicitly requested by this procedure via outputs based on a <template/>!
         -   If <getopt-option-next/> matches the regex `^(DONE|IMPLEMENT|PREFLIGHT|REFINE)$`:
             Honor the pre-selection what to do as the next step.
             Set <result><getopt-option-next/></result>.
-            Then *clear* <getopt-option-next/> by setting <getopt-option-next>none</getopt-option-next>
-            so that subsequent loop iterations fall back to the interactive dialog.
+
+            Then *clear* <getopt-option-next/> by setting
+            <getopt-option-next>none</getopt-option-next> so that
+            subsequent loop iterations fall back to the interactive
+            dialog.
+
+            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.
 
         -   If <getopt-option-next/> is equal to `none`:
             Let the *user interactively choose* what to do as the next step.
@@ -367,9 +393,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         -   If <result/> is `REFINE`:
 
-            Ask the user interactively, without a special tool, for
-            the refinement instruction with a single question `**What
-            is your instruction for refining the plan?**`. Then set
+            Ask the user interactively, without a special tool, for the
+            refinement instruction with a single question `**What is
+            your instruction for further refining the plan?**`. Then set
             <instruction/> to the response of the user.
 
             Treat the <instruction/> as a *refinement instruction* for
@@ -389,7 +415,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         -   If <result/> matches `OTHER: <text/>`:
 
-            Set <instruction><text/></instruction>.
+            Set <instruction><text/></instruction> (replace existing instruction).
 
             Treat the <instruction/> as a *refinement instruction* for
             the plan, and update <content/> in-place by *applying* the

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

@@ -0,0 +1,75 @@
+
+##  NAME
+
+`ase-task-edit` - Iteratively Edit a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-edit`
+    [`--help`|`-h`]
+    [`--plan`|`-p` *option*]
+    [`--next`|`-n` *option*]
+    [*id* | *id*: *instruction* | *instruction*]
+
+##  DESCRIPTION
+
+The `ase-task-edit` skill establishes and refines a *task plan* purely
+through a *chat-driven loop*. The user steers each round via an
+interactive dialog that offers continued refinement, finalization, or
+hand-off to implementation or preflight.
+
+The task plan is stored in `.ase/tasks/`*id*`/plan.md` files of the
+project and can be alternatively edited with the "`ase task edit` *id*"
+command from outside the agent tool.
+
+##  OPTIONS
+
+`--plan`|`-p` *option*:
+    Automatically answer the user dialog for the plan refinement
+    with *option*, which can be either `none` (default, interactive
+    answer required), `OVERWRITE` (overwrite an existing plan
+    with *instruction*), `REFINE` (refine the existing plan with
+    *instruction*), or `PRESERVE` (preserve the existing plan by
+    ignoring *instruction* and stopping skill processing).
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step (at the end
+    of this skill) with *option*, which can be either `none` (default,
+    interactive answer required), `DONE` (no next step), `IMPLEMENT`
+    (hand-over to `ase-task-implement`), `PREFLIGHT` (hand-over to
+    `ase-task-preflight`), or `REFINE` (refine the plan with subsequent
+    instruction).
+
+##  ARGUMENTS
+
+*id* | *id*: *instruction* | *instruction*:
+    Edit the task with the unique identifier *id* (default: `default`).
+    Optionally, *instruction* either gives instructions for creating a
+    new task or gives instructions for refining an existing task.
+
+##  EXAMPLES
+
+Edit the current task:
+
+```text
+❯ /ase-task-edit
+```
+
+Create a new task under id `hello`:
+
+```text
+❯ /ase-task-delete hello
+❯ /ase-task-edit hello: new "ase hello" CLI command which prints
+  a nice "Hello World!" to the terminal in color blue.
+```
+
+Further refine the task under id `hello`:
+
+```text
+❯ /ase-task-edit hello: change the color to red.
+```
+
+##  SEE ALSO
+
+`ase-task-reboot`, `ase-task-preflight`, `ase-task-implement`,
+`ase-task-view`, `ase-task-list`, `ase-task-rename`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-id
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [<id>]"
 description: >
     Get or set unique task id <id>.
     Use when user requests to work on a certain task
@@ -13,18 +13,19 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Task Configuration
-==================
-
 <skill name="ase-task-id">
 Configure Task Id
 </skill>
 
+<objective>
+*Get* or *set* the unique *task id* of the current session.
+</objective>
+
 1.  Determine request:
     <request>$ARGUMENTS</request>
 
 2.  <if condition="<request/> is empty">
-    -   Call the `ase_task_id(session: <ase-session-id/>)`
+    -   Call the `ase_task_id(session: "<ase-session-id/>")`
         tool from the `ase` MCP server and set
         <ase-task-id/> to its `text` output.
 
@@ -36,7 +37,7 @@ Configure Task Id
 
 3.  <if condition="<request/> is NOT empty">
     -   Set <ase-task-id><request/></ase-task-id> and
-        call the `ase_task_id(id: <ase-task-id/>, session: <ase-session-id/>)`
+        call the `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")`
         tool from the `ase` MCP server.
 
     -   Output:

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

@@ -0,0 +1,42 @@
+
+##  NAME
+
+`ase-task-id` - Configure Task Id
+
+##  SYNOPSIS
+
+`ase-task-id`
+    [`--help`|`-h`]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-id` skill gets or sets the unique *task id* for the
+current session. Without arguments, it reports the currently active
+task id. With an *id* argument, it switches the session to that
+task id via the `ase_task_id` MCP tool.
+
+##  ARGUMENTS
+
+*id*:
+    The new task id to activate. If omitted, the currently active
+    task id is reported.
+
+##  EXAMPLES
+
+Show the current task id:
+
+```text
+❯ /ase-task-id
+```
+
+Switch to a specific task:
+
+```text
+❯ /ase-task-id hello
+```
+
+##  SEE ALSO
+
+`ase-task-list`, `ase-task-edit`, `ase-task-view`,
+`ase-task-rename`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-implement
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>] [<id>]"
 description: >
     Implement current or given task plan.
     Use when the user calls to "implement", "realize" or "apply" the
@@ -15,9 +15,6 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Implement a Task Plan
-=====================
-
 <skill name="ase-task-implement">
 Implement a Task Plan
 </skill>
@@ -28,13 +25,10 @@ Implement a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *implementation* of changes.
-</role>
-
+<objective>
 *Implement* the task plan by modifying the *artifacts*
 with a corresponding, complete *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-implement**, ▶ 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/>:
 

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

@@ -0,0 +1,56 @@
+
+##  NAME
+
+`ase-task-implement` - Implement a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-implement`
+    [`--help`|`-h`]
+    [`--next`|`-n` *option*]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-implement` skill performs the *final implementation*
+of a task plan by modifying the corresponding *artifacts* with a
+complete *change set*. The plan is loaded from
+`.ase/tasks/`*id*`/plan.md`, and any optional `IMPLEMENTATION DRAFT`
+section produced by `ase-task-preflight` is used as a hint — the
+plain plan content always overrules the draft.
+
+After implementation, the user is asked whether to preserve or
+delete the task plan, 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` (preserve task plan and stop), or
+    `DELETE` (hand off to `ase-task-delete`).
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task whose plan should be
+    implemented. If omitted, the *current* task id is used.
+
+##  EXAMPLES
+
+Implement the current task plan:
+
+```text
+❯ /ase-task-implement
+```
+
+Implement a specific task and delete the plan when done:
+
+```text
+❯ /ase-task-implement --next DELETE hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-preflight`, `ase-task-reboot`,
+`ase-task-view`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-list
-argument-hint: "[-v|--verbose]"
+argument-hint: "[--help|-h] [--verbose|-v]"
 description: >
     List all available task ids.
     Use when user wants to see all tasks.
@@ -13,9 +13,6 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Task List
-=========
-
 <skill name="ase-task-list">
 List Task Plans
 </skill>
@@ -26,7 +23,11 @@ List Task Plans
     $ARGUMENTS
 </expand>
 
-1.  Call the `ase_task_list(verbose: <getopt-option-verbose/>)` tool from
+<objective>
+*List* all available *task plans* of the current project.
+</objective>
+
+1.  Call the `ase_task_list(verbose: "<getopt-option-verbose/>")` tool from
     the `ase` MCP server. The result is a structured object with a
     `tasks` array where each entry has an `id` field, and -- if
     <getopt-option-verbose/> is `true` -- additionally an `mtime` field

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

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-task-list` - List Task Plans
+
+##  SYNOPSIS
+
+`ase-task-list`
+    [`--help`|`-h`]
+    [`--verbose`|`-v`]
+
+##  DESCRIPTION
+
+The `ase-task-list` skill lists all available *task ids* in the
+current project by calling the `ase_task_list` MCP tool. In the
+default mode, only the task ids are rendered as a single-column
+Markdown table. In verbose mode, the last-modified timestamp of
+each task plan is rendered as an additional column.
+
+##  OPTIONS
+
+`--verbose`|`-v`:
+    Render an additional `Last Modified` column with the
+    `YYYY-MM-DD HH:MM` timestamp of each task plan.
+
+##  EXAMPLES
+
+List all task ids:
+
+```text
+❯ /ase-task-list
+```
+
+List all task ids together with their last-modified timestamps:
+
+```text
+❯ /ase-task-list --verbose
+```
+
+##  SEE ALSO
+
+`ase-task-id`, `ase-task-view`, `ase-task-edit`,
+`ase-task-rename`, `ase-task-delete`.