@rse/ase 0.9.6 → 0.9.8

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

@@ -30,7 +30,7 @@ hand-off to implementation or preflight.
     ignoring *instruction* and stopping skill processing).
 
 `--dry`|`-d`:
-    Generate any *new* plan *without* the `※ VERIFICATION` section.
+    Generate any *new* plan *without* the `##  VERIFICATION` section.
     Applies only to freshly generated plans, not to existing plans
     loaded from disk. When `ase-task-implement` later applies such
     a plan, it strictly skips the entire verification phase (no
@@ -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
 

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

@@ -22,7 +22,7 @@ Iteratively Grill a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-grill"
-    arg2="--next|-n=(none|DONE|EDIT)...">
+    arg2="--next|-n=(none|DONE|EDIT|IMPLEMENT|PREFLIGHT)... --int-reuse-task">
     $ARGUMENTS
 </expand>
 
@@ -36,9 +36,15 @@ task plan until reaching a shared understanding.
 Procedure
 ---------
 
+You *MUST* follow the following numbered items *strictly* *sequentially*!
+You *MUST* not skip any numbered item during processing!
+
+You *MUST* *NOT* output anything in this entire procedure, *except* when
+explicitly requested by this procedure via outputs based on a <template/>!
+
 1.  **Determine Task:**
 
-    1.  Set <id>$ARGUMENTS</id> initially.
+    1.  Set <id><getopt-arguments/></id> 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.
@@ -59,22 +65,34 @@ Procedure
             </template>
             </if>
 
-        2.  else <if condition="<id/> is NOT empty">
+        2.  <elseif condition="<id/> 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-grill**, ▶ **ERROR**: expected single `[<id>]` argument
+            ⧉ **ASE**: ☻ skill: **ase-task-grill**, ▶ ERROR: expected single `[<id>]` argument
             </template>
-            </if>
+            </elseif>
 
 2.  **Determine Task Plan:**
 
-    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.
+    1.  Determine the current task 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 the current 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. Set <status>plan loaded</status>.
+        </else>
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
             Output the following <template/> and then immediately *STOP*
@@ -91,7 +109,7 @@ Procedure
         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="<plan/> is empty">
@@ -107,6 +125,11 @@ Procedure
     *essential aspect* of the task plan in <plan/> *until* reaching a
     shared understanding and no decisions/questions are left open.
 
+    This especially means, you *MUST* clarify as many aspects as
+    necessary to ensure that for at least the most important decisions,
+    during a subsequent implementation, no essential freedom of choices
+    exist any longer.
+
     For this process, determine the <n/> essential aspects <aspect-N/>
     (a one or two word long short identifier like `Foo` or `Bar-Baz`)
     and the corresponding decision/question <question-N/> where a shared
@@ -138,7 +161,7 @@ Procedure
     decisions one-by-one. Ask the questions <question-N/> and determine
     corresponding answer <answer-N/>, one at a time.
 
-    1.  For each question <question-N/> in the iteration circle <N/>:
+    1.  For each question <question-N/> in the iteration cycle <N/>:
 
         1.  Output the following <template/>:
 
@@ -167,7 +190,12 @@ Procedure
                 <ase-tpl-bullet-normal/> ASPECT <N/>/<n/>: **<aspect-N/>**, ANSWER: **<answer-N/>**
                 </template>
 
-    3.  Finally, update the plan in <plan/> based on all answers <answer-N/>.
+    2.  Finally, update the plan in <plan/> based on all answers <answer-N/>.
+
+    3.  <if condition="<plan/> contains 'Created:  <text/>'">
+        Set <timestamp-created><text/></timestamp-created> (set
+        timestamp-created to extracted text)
+        </if>
 
     4.  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
@@ -224,20 +252,20 @@ Procedure
     2.  Check the tool <result/> and dispatch accordingly:
 
         -   If <result/> is `DONE` or `CANCEL`:
-            Only output the following <template/> and then *STOP*.
+            Only output the following <template/> and then *STOP*,
+            without output of any further information.
 
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- done**
             </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.
@@ -247,13 +275,12 @@ Procedure
             </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>
@@ -261,15 +288,23 @@ Procedure
             </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>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implementation**
             </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-id/SKILL.md

@@ -24,7 +24,16 @@ Configure Task Id
 1.  Determine request:
     <request>$ARGUMENTS</request>
 
-2.  <if condition="<request/> is empty">
+2.  <if condition="<request/> is NOT empty AND <request/> 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-id**, ▶ ERROR: given task id `<request/>` is not a valid id
+    </template>
+    </if>
+
+3.  <if condition="<request/> is empty">
     -   Call the `ase_task_id(session: "<ase-session-id/>")`
         tool from the `ase` MCP server and set
         <ase-task-id/> to its `text` output.
@@ -35,7 +44,7 @@ Configure Task Id
         </template>
     </if>
 
-3.  <if condition="<request/> is NOT empty">
+4.  <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/>")`
         tool from the `ase` MCP server.

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

@@ -21,7 +21,7 @@ Implement a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-implement"
-    arg2="--next|-n=(none|DONE|DELETE)...">
+    arg2="--next|-n=(none|DONE|DELETE)... --int-reuse-task">
     $ARGUMENTS
 </expand>
 
@@ -65,7 +65,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </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*
@@ -80,9 +80,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
             </template>
-            </if>
+            </elseif>
 
-        3.  else <if condition="<instruction/> is NOT empty">
+        3.  <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/>
@@ -91,13 +91,25 @@ explicitly requested by this procedure via outputs based on a <template/>!
             <template>
             ⧉ **ASE**: ☻ skill: **ase-task-implement**, ▶ ERROR: expected single `[<id>]` argument
             </template>
-            </if>
+            </elseif>
 
 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 <text/> to
-        the `text` output field of the `ase_task_load` tool call.
+    1.  Determine the current task 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 the current 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. Set <status>plan loaded</status>.
+        </else>
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
             Set <content></content> (set content to empty).
@@ -110,12 +122,13 @@ explicitly requested by this procedure via outputs based on a <template/>!
         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 the <content/> is still empty, complain and tell the user to
         use the `ase-code-resolve`, `ase-code-refactor`, `ase-code-craft`,
-        or `ase-task-edit` skills first to create a task plan.
+        or `ase-task-edit` skills first to create a task plan. Then
+        immediately stop processing this skill.
 
 3.  **Create Implementation:**
 
@@ -131,8 +144,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
         overrules the implementation draft in the `IMPLEMENTATION DRAFT`
         section of <content/>.
 
-        <if condition="<content/> does NOT contain a `## ※ VERIFICATION` section heading">
-        The task plan deliberately *omits* the `## ※ VERIFICATION`
+        <if condition="<content/> does NOT contain a `##  VERIFICATION` section heading">
+        The task plan deliberately *omits* the `##  VERIFICATION`
         section. You *MUST* therefore *strictly skip* the entire
         verification phase after modifying the source files: do *NOT*
         run any build, do *NOT* run any tests, do *NOT* run any linter,
@@ -189,11 +202,10 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
         -   If <result/> is `DELETE`:
-            Set <args></args> (empty).
-            <if condition="<getopt-option-next/> is not equal `none`">
-            Set <args>--next <getopt-option-next/></args> (forward
-            remaining list tokens to the downstream skill).
-            </if>
+            Set <args></args> (empty). Do *not* forward any remaining
+            `--next` list tokens, because the `ase:ase-task-delete`
+            skill accepts only an optional `[<id>]` argument and no
+            `--next` option; remaining tokens are intentionally discarded.
             Only output the following <template/> and then call the
             tool `Skill(skill: "ase:ase-task-delete", args: <args/>)`
             to invoke the `ase:ase-task-delete` skill in order to
@@ -204,3 +216,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented -- hand-off to delete task**
             </template>
 
+        -   If <result/> matches `OTHER: <text/>` or is any other
+            unrecognized value:
+            Treat it as `DONE` (the plan is already implemented):
+            only output the following <template/> and then *STOP*.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented -- done**
+            </template>
+

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

@@ -18,7 +18,7 @@ a task plan by modifying the corresponding *artifacts* with a complete
 section produced by `ase-task-preflight` is used as a hint - the plain
 plan content always overrules the draft.
 
-If the task plan deliberately *omits* the `※ VERIFICATION` section
+If the task plan deliberately *omits* the `##  VERIFICATION` section
 (as produced by `ase-code-craft`, `ase-code-refactor`,
 `ase-code-resolve`, or `ase-task-edit` when invoked with `--dry`),
 the entire verification phase is strictly skipped: no build, tests,

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

@@ -27,7 +27,7 @@ List Task Plans
 *List* all available *task plans* of the current project.
 </objective>
 
-1.  Call the `ase_task_list(verbose: "<getopt-option-verbose/>")` tool from
+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-preflight/SKILL.md

@@ -21,7 +21,7 @@ Preflight a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-preflight"
-    arg2="--next|-n=(none|DONE|EDIT|IMPLEMENT)...">
+    arg2="--next|-n=(none|DONE|EDIT|IMPLEMENT)... --int-reuse-task">
     $ARGUMENTS
 </expand>
 
@@ -65,7 +65,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </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*
@@ -80,9 +80,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
             <template>
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
             </template>
-            </if>
+            </elseif>
 
-        3.  else <if condition="<instruction/> is NOT empty">
+        3.  <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/>
@@ -91,13 +91,25 @@ explicitly requested by this procedure via outputs based on a <template/>!
             <template>
             ⧉ **ASE**: ☻ skill: **ase-task-preflight**, ▶ ERROR: expected single `[<id>]` argument
             </template>
-            </if>
+            </elseif>
 
 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 <text/> to
-        the `text` output field of the `ase_task_load` tool call.
+    1.  Determine the current task 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 the current 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. Set <status>plan loaded</status>.
+        </else>
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
             Set <content></content> (set content to empty).
@@ -110,12 +122,13 @@ explicitly requested by this procedure via outputs based on a <template/>!
         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 the <content/> is still empty, complain and tell the user to
         use the `ase-code-resolve`, `ase-code-refactor`, `ase-code-craft`,
-        or `ase-task-edit` skills first to create a task plan.
+        or `ase-task-edit` skills first to create a task plan. Then
+        immediately stop processing this skill.
 
 3.  **Create Implementation Draft:**
 
@@ -126,13 +139,13 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     2.  Append this artifact change set <unified-diff/> to the end
         of the <content/> with the following <template/>. If a section
-        named `## ※ IMPLEMENTATION DRAFT` already exists from a
+        named `##  IMPLEMENTATION DRAFT` already exists from a
         previous run of this skill, *replace* this entire existing
         section.
 
         <template>
 
-        ## ※ IMPLEMENTATION DRAFT
+        ##  IMPLEMENTATION DRAFT
 
         ```text
         <unified-diff/>
@@ -140,12 +153,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         </template>
 
-    3.  <if condition="<content/> contains '✎ modified:'">
+    3.  <if condition="<content/> contains '⚙   Modified:'">
         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>
 
@@ -202,13 +215,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.
@@ -218,13 +230,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
-            tool `Skill(skill: "ase:ase-task-implement", args: <args/>)`
+            tool `Skill(skill: "ase:ase-task-implement", args: "<args/>")`
             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.
@@ -233,3 +244,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implement**
             </template>
 
+        -   If <result/> matches `OTHER: <text/>` or is any other
+            unrecognized value:
+            Treat it as `DONE` (the plan is already preflighted):
+            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-preflight/help.md

@@ -16,7 +16,7 @@ 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).
+an `IMPLEMENTATION DRAFT` section (replacing any previous draft).
 No source files are modified.
 
 After the preflight, the user is asked whether to stop, hand