@rse/ase 0.9.5 → 0.9.7

package/plugin/skills/ase-code-refactor/SKILL.md

@@ -38,7 +38,7 @@ to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to
 <request><getopt-arguments/></request>
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------
@@ -196,12 +196,12 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ● **APPROACH A<n/>**<annotation/>: *<summary/>*
-        ○ [...]
-        ○ [...]
-        ○ [...]
-        ⊕ *pro*: [...]
-        ⊖ *con*: [...]
+        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ○   [...]
+        ○   [...]
+        ○   [...]
+        ⊕   **PRO*: [...]
+        ⊖   **CON*: [...]
         <optional-diagram/>
         </template>
 
@@ -269,7 +269,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
-        You *MUST* completely omit the `## ※ VERIFICATION` section
+        You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
         <content/>.
         </if>

package/plugin/skills/ase-code-refactor/help.md

@@ -34,7 +34,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     asking the user via the interactive dialog.
 
 `--dry`|`-d`:
-    Compose the plan *without* the `※ VERIFICATION` section. When
+    Compose the plan *without* the `##  VERIFICATION` section. When
     `ase-task-implement` later applies such a plan, it strictly skips
     the entire verification phase (no build, tests, linter,
     type-checker, or program execution) once the source files have
@@ -43,7 +43,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended refactoring approach, compose the plan *without* the
-    `※ VERIFICATION` section, immediately hand off to `ase-task-implement`,
+    `##  VERIFICATION` section, immediately hand off to `ase-task-implement`,
     and finally `ase-task-delete` the now-consumed plan. This gives a
     single, fast *one-shot* refactoring mode.
 

package/plugin/skills/ase-code-resolve/SKILL.md

@@ -38,7 +38,7 @@ to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to
 <problem><getopt-arguments/></problem>
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------
@@ -245,12 +245,12 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ● **APPROACH A<n/>**<annotation/>: *<summary/>*
-        ○ [...]
-        ○ [...]
-        ○ [...]
-        ⊕ *pro*: [...]
-        ⊖ *con*: [...]
+        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ○   [...]
+        ○   [...]
+        ○   [...]
+        ⊕   *PRO*: [...]
+        ⊖   *CON*: [...]
         <optional-diagram/>
         </template>
 
@@ -317,7 +317,7 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         file, aligned with its existing style and conventions.
 
         <if condition="<getopt-option-dry/> is equal `true`">
-        You *MUST* completely omit the `## ※ VERIFICATION` section
+        You *MUST* completely omit the `##  VERIFICATION` section
         (including its heading and all of its bullet points) from
         <content/>.
         </if>

package/plugin/skills/ase-code-resolve/help.md

@@ -39,7 +39,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
     asking the user via the interactive dialog.
 
 `--dry`|`-d`:
-    Compose the plan *without* the `※ VERIFICATION` section. When
+    Compose the plan *without* the `##  VERIFICATION` section. When
     `ase-task-implement` later applies such a plan, it strictly skips
     the entire verification phase (no build, tests, linter,
     type-checker, or program execution) once the source files have
@@ -48,7 +48,7 @@ plan via `ase_task_save` and then hands off to `ase-task-edit`,
 `--quick`|`-Q`:
     Shorthand alias for `-a -d -n IMPLEMENT,DELETE`: automatically pick
     the recommended resolution approach, compose the plan *without* the
-    `※ VERIFICATION` section, immediately hand off to `ase-task-implement`,
+    `##  VERIFICATION` section, immediately hand off to `ase-task-implement`,
     and finally `ase-task-delete` the now-consumed plan. This gives a
     single, fast *one-shot* resolution mode.
 

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

@@ -30,7 +30,7 @@ Condense a Task Plan
 semantics exactly.
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------

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

@@ -17,10 +17,6 @@ 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*:

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

@@ -34,7 +34,7 @@ continued refinement, finalization, or hand-off to implementation or
 preflight.
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------
@@ -73,7 +73,7 @@ that `CHANGELOG.md` file, aligned with its existing style
 and conventions.
 
 <if condition="<getopt-option-dry/> is equal `true`">
-You *MUST* completely omit the `## ※ VERIFICATION` section
+You *MUST* completely omit the `##  VERIFICATION` section
 (including its heading and all of its bullet points) from
 <content/>.
 </if>
@@ -271,7 +271,7 @@ Set <content-dirty>true</content-dirty>.
             </template>
         </if>
 
-    4.  <if condition="<content/> does not contain '# ✪ TASK PLAN:' 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>.
@@ -318,18 +318,19 @@ Set <content-dirty>true</content-dirty>.
         </template>
         </if>
 
-    3.  *Render plan*: Only output the following <template/>, so the user
+    3.  *Render plan*: Treat <content/> as *verbatim* Markdown.
+        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 (from the
+        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 `[...]`.
+        content of the `##  IMPLEMENTATION DRAFT` section with `[...]`.
         Else, do *not* truncate, summarize, or partially show the plan.
         Use the following <template/>:
 
         <template>
-        <ase-tpl-head title="TASK-PLAN"/>
+        <ase-tpl-head title="TASK"/>
         <content/>
-        <ase-tpl-foot title="TASK-PLAN"/>
+        <ase-tpl-foot title="TASK"/>
         </template>
 
     4.  *Determine next step*:

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

@@ -19,10 +19,6 @@ 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*:
@@ -34,7 +30,7 @@ command from outside the agent tool.
     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

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

@@ -31,7 +31,7 @@ Interview the user relentlessly about every essential aspect of the
 task plan until reaching a shared understanding.
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------
@@ -107,6 +107,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 much 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
@@ -224,7 +229,8 @@ 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**

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

@@ -27,10 +27,6 @@ lets the user pick via an interactive dialog. It honors checks for
 updated and persisted, and the user is offered a hand-off to editing,
 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
 
 `--next`|`-n` *option*[,...]:

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

@@ -30,7 +30,7 @@ Implement a Task Plan
 with a corresponding, complete *change set*.
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------
@@ -131,8 +131,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,

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

@@ -12,14 +12,13 @@
 
 ##  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.
-
-If the task plan deliberately *omits* the `※ VERIFICATION` section
+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 and any optional `IMPLEMENTATION DRAFT`
+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
 (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-preflight/SKILL.md

@@ -30,7 +30,7 @@ Preflight a Task Plan
 for a corresponding, *complete source code change set*.
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------
@@ -126,13 +126,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/>

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

@@ -30,7 +30,7 @@ Reboot a Task Plan
 based on the existing *WHAT* and *WHY*.
 </objective>
 
-@${CLAUDE_SKILL_DIR}/../../meta/ase-format-plan.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 
 Procedure
 ---------
@@ -107,24 +107,24 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     1.  Start with <instruction></instruction> (set instruction to empty).
 
-    2.  <if condition="<content/> contains neither '- **WHAT**:' nor '- **WHY**:'">
+    2.  <if condition="<content/> contains neither '-   **WHAT**:' nor '-   **WHY**:'">
         Set <instruction><content/></instruction> (set instruction to content).
         </if>
 
-    3.  <if condition="<content/> contains '- **WHAT**: <text/>'">
+    3.  <if condition="<content/> contains '-   **WHAT**: <text/>'">
         Set <instruction><text/></instruction> (set instruction to extracted text).
         </if>
 
-    4.  <if condition="<content/> contains '- **WHY**: <text/>' and <instruction/> is empty">
+    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">
+    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>
 
-    6.  <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>

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-view
-argument-hint: "[--help|-h] [<id>]"
+argument-hint: "[--help|-h] [--full|-f] [<id>]"
 description: >
     View current or given task plan.
     Use when the user calls to "view", "show" or "see" the
@@ -12,11 +12,18 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-task-view">
 View a Task Plan
 </skill>
 
+<expand name="getopt"
+    arg1="ase-task-view"
+    arg2="--full|-f">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *View* the task plan.
 </objective>
@@ -32,7 +39,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 1.  **Determine Task:**
 
-    1.  Set <id>$ARGUMENTS</id> initially, with any leading and trailing
+    1.  Set <id><getopt-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.
@@ -76,15 +83,19 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
     2.  <if condition="<content/> is not empty">
-        *Render plan*: Only output the following <template/>, so the user
-        can read the plan and react to it. Do *not* truncate, summarize,
-        or partially show the plan -- always show the complete plan
-        <content/> here.
+        Treat <content/> as *verbatim* Markdown.
+        *Render plan*: Only output the following <template/>. If
+        <getopt-option-full/> is *not* `true`, <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-tpl-head title="TASK-PLAN"/>
+        <ase-tpl-head title="TASK"/>
         <content/>
-        <ase-tpl-foot title="TASK-PLAN"/>
+        <ase-tpl-foot title="TASK"/>
         </template>
         </if>