@rse/ase 0.9.59 → 0.9.61

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

@@ -48,8 +48,9 @@ Procedure
 
 <if condition="<getopt-option-direct/> is not equal to 'true'">
 You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
-filesystem-modifying tool during this entire skill. The *only*
-permitted way to persist artifacts is via `ase_task_save(...)`.
+filesystem-modifying tool, nor execute any filesystem-modifying
+shell command, during this entire skill. The *only* permitted way
+to persist artifacts is via the `ase_task_save(...)` MCP tool.
 </if>
 <else>
 The `--direct`/`-D` mode applies the resolution *in place*, so STEP 4
@@ -257,11 +258,11 @@ resolution actually demands, and you *MUST* *NOT* call
         `ase` MCP server and use the `text` field of its response for
         <timestamp-created/> and <timestamp-modified/> information. Then
         insert the current <ase-task-id/>, <timestamp-created/>,
-        <timestamp-modified/>, and <task-kind/> information and calculate
-        the number of words <words/> of <task-content/>.
+        <timestamp-modified/>, and <task-kind/> information.
 
     3.  You then *MUST* *save* the resulting plan content with the
-        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.
+        `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`
+        MCP tool call only -- *NEVER* by executing a shell command.
 
     4.  If <problem-id/> is set (i.e. the <problem/> was retrieved from
         `ase_kv_get` in STEP 1.1 via key `ase-issue-<problem-id/>`),
@@ -273,7 +274,7 @@ resolution actually demands, and you *MUST* *NOT* call
     5.  Output a hint with the following <template/>:
 
         <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan created**
         </template>
 
     6.  Directly pass through control to the next skill:

package/plugin/skills/ase-help-skill/catalog.md

@@ -28,6 +28,7 @@
 ○   `ase-code-craft`:      Craft Source Code
 ○   `ase-code-refactor`:   Refactor Artifacts
 ○   `ase-code-resolve`:    Resolve Problem
+○   `ase-code-edit`:       Edit Source Code
 ○   `ase-sync-import`:     Import Foreign Sources into Artifact Set
 ○   `ase-sync-reconcile`:  Reconcile Artifact Set to Artifact Set
 ○   `ase-sync-export`:     Export Artifact Set to Side-by-Side Files

package/plugin/skills/ase-sync-import/SKILL.md

@@ -167,7 +167,8 @@ Procedure
 
         Apply the generation/update directly to the target artifacts via
         the `Write`/`Edit` tools. For a `TASK` target, apply it via the
-        `ase_task_save` tool instead.
+        `ase_task_save` MCP tool instead -- *NEVER* write a task plan
+        file via `Write`/`Edit` or by executing a shell command.
 
     6.  Report the performed changes with the following <template/>, listing
         one bullet line per generated or updated file (with <file/> its

package/plugin/skills/ase-sync-reconcile/SKILL.md

@@ -177,7 +177,9 @@ Procedure
         parts of an output artifact.
 
         Apply the update directly to the output artifacts via the
-        `Write`/`Edit` tools.
+        `Write`/`Edit` tools. For a `TASK` output, apply it via the
+        `ase_task_save` MCP tool instead -- *NEVER* write a task plan
+        file via `Write`/`Edit` or by executing a shell command.
 
         For each formatted output artifact kind, strictly honor its
         format contract.

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

@@ -64,8 +64,8 @@ Set <args></args> (set args to empty).
 
         <expand name="task-load-content"></expand>
 
-        Set <words-before><words/></words-before> (remember the loaded
-        word count for the strictly-smaller check in step 3).
+        Set <content-before><task-content/></content-before> (remember the
+        loaded plan content for the strictly-shorter check in step 3).
 
         <if condition="the frontmatter of <task-content/> carries a `Created: <text/>` key">
         Set <timestamp-created><text/></timestamp-created> (extract the
@@ -124,21 +124,21 @@ Set <args></args> (set args to empty).
             example. If a shortening would change meaning, *keep the
             longer wording*.
 
-    2.  *Persist only if smaller*: calculate the number of words <words/>
-        of the condensed <task-content/>.
+    2.  *Persist only if smaller*: compare the condensed <task-content/>
+        against <content-before/>, without counting words.
 
-        -   <if condition="<words/> is strictly smaller than <words-before/>">
+        -   <if condition="the condensed <task-content/> is strictly shorter than <content-before/>">
             <expand name="task-save-content" arg1="plan condensed"></expand>
             </if>
 
-        -   <if condition="<words/> is NOT strictly smaller than <words-before/>">
+        -   <if condition="the condensed <task-content/> is NOT strictly shorter than <content-before/>">
             Do *not* save and do *not* bump the timestamp. Set
-            <words><words-before/></words> (report the word count of the
-            *unchanged* stored plan, not of the discarded condensed one).
+            <task-content><content-before/></task-content> (keep the
+            *unchanged* stored plan, discard the condensed one).
             Only output the following <template/>:
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan already condensed**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan already condensed**
             </template>
             </if>
 
@@ -162,7 +162,7 @@ Set <args></args> (set args to empty).
             Only output the following <template/> and then *STOP*.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan condensed -- done**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan condensed -- done**
             </template>
 
         -   If <result/> is `EDIT`:
@@ -174,7 +174,7 @@ Set <args></args> (set args to empty).
             skill once the `Skill` tool was used.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan condensed -- hand-off to edit**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan condensed -- hand-off to edit**
             </template>
 
         -   If <result/> is `IMPLEMENT`:
@@ -184,7 +184,7 @@ Set <args></args> (set args to empty).
             to *apply* the plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan condensed -- hand-off to implementation**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan condensed -- hand-off to implementation**
             </template>
 
         -   If <result/> is `PREFLIGHT`:
@@ -194,5 +194,5 @@ Set <args></args> (set args to empty).
             to *apply* the plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan condensed -- hand-off to pre-flight**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan condensed -- hand-off to pre-flight**
             </template>

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

@@ -245,13 +245,14 @@ Procedure
 
         2.  Call the `ase_task_save(id: "<part-id/>", text:
             "<part-content/>")` tool of the `ase` MCP server to persist
-            the sub-task plan, and calculate the number of words
-            <part-words/> of <part-content/>. Do not output anything
-            related to this MCP tool call except the following
-            <template/>:
+            the sub-task plan -- this MCP tool call is the *only*
+            permitted way to persist it, *NEVER* write the plan file
+            via `Write`/`Edit` or by executing a shell command. Do not
+            output anything related to this MCP tool call except the
+            following <template/>:
 
             <template>
-            ⧉ **ASE**: ◉ task: **<part-id/>**, ✪ plan: **<part-words/>** words, ▶ status: **sub-task plan created**
+            ⧉ **ASE**: ◉ task: **<part-id/>**, ▶ status: **sub-task plan created**
             </template>
 
     4.  *Report the overall result* with the following <template/>:

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

@@ -48,7 +48,17 @@ 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 <task-content/>.
+<if condition="<task-content/> contains a `##  IMPLEMENTATION DRAFT`
+    section (from the companion skill `ase-task-preflight`) AND the
+    applied <instruction/> changed the plan text *outside* of that
+    section">
+The implementation draft was created for the *previous* plan text and
+hence is *stale* now. Remove the entire `##  IMPLEMENTATION DRAFT`
+section from <task-content/>, remove the value `preflighted` from the
+`Properties:` frontmatter key (dropping the whole key if it carries no
+values anymore), and set <draft-removed>true</draft-removed>.
+</if>
+
 Set <task-content-dirty>true</task-content-dirty>.
 </define>
 
@@ -76,8 +86,7 @@ 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 fresh <timestamp-created/> and <timestamp-modified/>
 information. Then insert the current <ase-task-id/>,
-<timestamp-created/>, and <timestamp-modified/> information
-and calculate the number of words <words/> of <task-content/>.
+<timestamp-created/>, and <timestamp-modified/> information.
 Set <task-content-dirty>true</task-content-dirty>.
 </define>
 
@@ -205,21 +214,20 @@ Set <args></args> (set args to empty).
         </else>
 
         Set <task-content-dirty>false</task-content-dirty>.
+        Set <draft-removed>false</draft-removed>.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
             Silently ignore the MCP error.
             Set <task-content/> to empty.
             Set <task-render/> to empty.
-            Set <words/> to "0".
             Do not output anything.
 
         -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
             Set <task-content><text/></task-content> (set task content to text).
-            Calculate the number of words <words/> of <task-content/>.
             Only output the following <template/>:
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<status/>**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **<status/>**
             </template>
 
     2.  <if condition="<task-content/> is empty AND <instruction/> is empty">
@@ -267,7 +275,7 @@ Set <args></args> (set args to empty).
             *STOP* processing this skill:
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan preserved**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan preserved**
             </template>
 
         -   If <result/> is `OVERWRITE`:
@@ -277,7 +285,7 @@ Set <args></args> (set args to empty).
             Only output the following <template/> and continue processing:
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan overwritten**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan overwritten**
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
             </template>
 
@@ -288,7 +296,7 @@ Set <args></args> (set args to empty).
             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/>**, ▶ status: **plan refined**
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
             </template>
 
@@ -302,7 +310,7 @@ Set <args></args> (set args to empty).
             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/>**, ▶ status: **plan refined**
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
             </template>
         </if>
@@ -321,7 +329,7 @@ Set <args></args> (set args to empty).
 
         <template>
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan generated**
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan generated**
         </template>
         </if>
 
@@ -349,18 +357,32 @@ Set <args></args> (set args to empty).
         persist the current plan -- <task-content/> always is the
         *authoring form* of the plan and hence is persisted *as is* --
         and then set <task-content-dirty>false</task-content-dirty>
-        again. Finally, set <task-render/> to the `text` *output* field
+        again. This `ase_task_save` MCP tool call is the *only*
+        permitted way to persist the plan -- *NEVER* write the plan
+        file via `Write`/`Edit` or by executing a shell command.
+        Finally, set <task-render/> to the `text` *output* field
         of this `ase_task_save` tool call -- the rendering-prepared form
         of the just-persisted plan, which is for *display only* and
         *MUST NOT* be confused with the `text` *argument* passed into
         that call -- so the rendering in step 3.3 stays consistent across
-        all loop rounds. Calculate the number of words <words/> of
-        <task-content/>. Do not output anything related to this MCP tool
+        all loop rounds. Do not output anything related to this MCP tool
         call except the following <template/>:
 
         <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan saved**
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan saved**
         </template>
+
+        <if condition="<draft-removed/> is equal `true`">
+        Directly *after* this <template/>, reset
+        <draft-removed>false</draft-removed> and give the corrective
+        hint by expanding the following (which, depending on the
+        configured <ase-guidance-level/>, may expand into nothing and
+        hence emit no output at all):
+
+        <ase-tpl-hint level="minimal">
+        The `IMPLEMENTATION DRAFT` section became stale through the plan change and was removed -- run `/ase-task-preflight` again to re-create the draft for the changed plan.
+        </ase-tpl-hint>
+        </if>
         </if>
 
     3.  *Render plan*:
@@ -459,7 +481,7 @@ Set <args></args> (set args to empty).
             and then *STOP*. Do *not* implement the plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan finalized -- done**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan finalized -- done**
             </template>
 
         -   If <result/> is `GRILL`:
@@ -471,7 +493,7 @@ Set <args></args> (set args to empty).
             to *grill* the finalized plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan finalized -- hand-off to grilling**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan finalized -- hand-off to grilling**
             </template>
 
         -   If <result/> is `PREFLIGHT`:
@@ -483,7 +505,7 @@ Set <args></args> (set args to empty).
             to *apply* the finalized plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan finalized -- hand-off to pre-flight**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan finalized -- hand-off to pre-flight**
             </template>
 
         -   If <result/> is `IMPLEMENT`:
@@ -495,7 +517,7 @@ Set <args></args> (set args to empty).
             to *apply* the finalized plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan finalized -- hand-off to implementation**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan finalized -- hand-off to implementation**
             </template>
 
         -   If <result/> matches `OTHER: <text/>`:
@@ -517,6 +539,6 @@ Set <args></args> (set args to empty).
             and then *STOP*. Do *not* implement the plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan refinement cancelled**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan refinement cancelled**
             </template>
 

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

@@ -19,6 +19,13 @@ 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.
 
+When a refinement changes the plan text while an `IMPLEMENTATION
+DRAFT` section (produced by `ase-task-preflight`) exists, that section
+became *stale* and is *removed* -- together with the `preflighted`
+value of the `Properties:` frontmatter key -- and a hint is emitted
+that `ase-task-preflight` has to be run again to re-create the draft
+for the changed plan.
+
 ##  OPTIONS
 
 `--plan`|`-p` *option*:

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

@@ -193,7 +193,7 @@ Set <args>--int-reuse-task</args>.
             without output of any further information.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- done**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan updated -- done**
             </template>
 
         -   If <result/> is `EDIT`:
@@ -205,7 +205,7 @@ Set <args>--int-reuse-task</args>.
             skill once the `Skill` tool was used.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to edit**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan updated -- hand-off to edit**
             </template>
 
         -   If <result/> is `PREFLIGHT`:
@@ -215,7 +215,7 @@ Set <args>--int-reuse-task</args>.
             to *apply* the plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to pre-flight**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan updated -- hand-off to pre-flight**
             </template>
 
         -   If <result/> is `IMPLEMENT`:
@@ -225,5 +225,5 @@ Set <args>--int-reuse-task</args>.
             to *apply* the plan.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implementation**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan updated -- hand-off to implementation**
             </template>

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

@@ -162,13 +162,21 @@ Procedure
         by modifying the *artifacts* with a corresponding, complete
         *change set*.
 
-        For this, primarily follow and honor the task plan in <task-content/>.
+        <if condition="<task-content/> contains an `##  IMPLEMENTATION DRAFT` section (from skill `ase-task-preflight`)">
+        Take over the implementation draft of this section *1:1* as
+        the change set: the draft is assumed to have been *reviewed*
+        by the user, so you *MUST* *NOT* create a fresh implementation
+        from scratch. Apply the draft *verbatim* and *adjust* only
+        those parts which actually *fail* -- because a hunk no longer
+        applies to meanwhile drifted artifacts, or because the
+        verification phase rejects the result. For such adjusted parts,
+        and for aspects the draft does not cover at all, follow the
+        task plan in <task-content/>.
+        </if>
 
-        Secondarily, derive hints from the optionally existing
-        `IMPLEMENTATION DRAFT` section (from skill `ase-task-preflight`)
-        in <task-content/>. But the specification text in <task-content/> always
-        overrules the implementation draft in the `IMPLEMENTATION DRAFT`
-        section of <task-content/>.
+        <if condition="<task-content/> contains NO `##  IMPLEMENTATION DRAFT` section">
+        Follow and honor the task plan in <task-content/>.
+        </if>
 
         <if condition="<worktree-dir/> is not empty">
         The change set *MUST* land *exclusively inside* the worktree
@@ -224,12 +232,15 @@ Procedure
 
         Finally call the `ase_task_save(id: "<ase-task-id/>", text:
         "<task-content/>")` tool of the `ase` MCP server to persist the
-        updated task plan. Do not output anything in this sub-step.
+        updated task plan. This `ase_task_save` MCP tool call is the
+        *only* permitted way to persist the plan -- *NEVER* write the
+        plan file via `Write`/`Edit` or by executing a shell command.
+        Do not output anything in this sub-step.
 
     3.  Only output the following <template/>:
 
         <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented**
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan implemented**
         </template>
 
     4.  <if condition="<worktree-dir/> is not empty">
@@ -260,7 +271,7 @@ Procedure
             Only output the following <template/> and then *STOP*.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented -- done**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan implemented -- done**
             </template>
 
         -   If <result/> is `DELETE`:
@@ -275,6 +286,6 @@ Procedure
             current skill once the `Skill` tool was used.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented -- hand-off to delete task**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan implemented -- hand-off to delete task**
             </template>
 

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

@@ -16,8 +16,10 @@
 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. Afterwards the plan's
+section produced by `ase-task-preflight` is taken over *1:1* as the
+change set -- the draft is assumed to be user-reviewed, so no fresh
+implementation is created and only parts which actually fail are
+adjusted, guided by the plain plan content. Afterwards the plan's
 `Properties:` frontmatter key gains the value `implemented` (plus
 `verified`, if the verification phase actually ran and succeeded), and
 its `Status:` key becomes `COMPLETED` if the change set was applied

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

@@ -72,6 +72,18 @@ Procedure
         which *would* fully implement the task plan <task-content/>. Store
         this artifact change set in *unified diff* format in <unified-diff/>.
 
+        Create this draft with the *same rigor* as the final
+        implementation of the companion skill `ase-task-implement`,
+        because that skill later takes the draft over *1:1* -- the user
+        is assumed to review the draft in between. Hence *read* the
+        current content of *every* artifact the draft touches before
+        drafting its hunks, so all context lines match the artifacts
+        *exactly* and the diff would apply *cleanly*, and honor the
+        task plan and the internalized tenets just as the final
+        implementation would. Only the actual modification of the
+        artifacts and the verification phase are deferred to
+        `ase-task-implement`.
+
     2.  Append this artifact change set <unified-diff/> to the end
         of the <task-content/> with the following <template/>. If a section
         named `##  IMPLEMENTATION DRAFT` already exists from a
@@ -112,12 +124,14 @@ Procedure
 
     4.  Finally, call the `ase_task_save(id: "<ase-task-id/>",
         text: "<task-content/>")` tool of the `ase` MCP server to save the updated
-        task plan content. Calculate the number of words <words/> of
-        <task-content/>. Do not output anything related to this MCP tool call
+        task plan content. This `ase_task_save` MCP tool call is the
+        *only* permitted way to persist the plan -- *NEVER* write the
+        plan file via `Write`/`Edit` or by executing a shell command.
+        Do not output anything related to this MCP tool call
         except the following <template/>:
 
         <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated**
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan updated**
         </template>
 
 4.  **Decide Next Step:**
@@ -139,7 +153,7 @@ Procedure
             Only output the following <template/> and then *STOP*.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- done**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan updated -- done**
             </template>
 
         -   If <result/> is `EDIT`:

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

@@ -18,7 +18,11 @@ draft for a corresponding, complete *artifact change set* in
 *unified diff* format. The draft is appended to the task plan as
 an `IMPLEMENTATION DRAFT` section (replacing any previous draft) and
 the plan's `Properties:` frontmatter key gains the value `preflighted`.
-No source files are modified.
+No source files are modified. The draft is produced under the *same
+tenets* and with the *same rigor* as a final implementation, because
+`ase-task-implement` later takes it over *1:1* after user review --
+only the actual artifact modification and the verification phase
+are deferred.
 
 The *kind of change* stated by the plan's `Kind:` frontmatter key
 (`CRAFTING`, `REFACTORING`, or `RESOLVING`) selects which

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

@@ -139,7 +139,7 @@ Procedure
             Only output the following <template/> and then *STOP*.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan rebooted -- done**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **plan rebooted -- done**
             </template>
 
         -   If <result/> is `EDIT`:

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

@@ -71,11 +71,10 @@ Procedure
 
         -   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
             Set <task-content><text/></task-content> (set task content to text).
-            Calculate the number of words <words/> of <task-content/>.
             Only output the following <template/>:
 
             <template>
-            ⧉ **ASE**: ◉ task: **<id/>**, ✪ plan: **<words/>** words, ▶ status: **plan loaded**
+            ⧉ **ASE**: ◉ task: **<id/>**, ▶ status: **plan loaded**
             </template>
 
     2.  <if condition="<task-content/> is not empty">