@rse/ase 0.9.44 → 0.9.45

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

@@ -31,99 +31,30 @@ with a corresponding, complete *change set*.
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md
 
 Procedure
 ---------
 
 1.  **Determine Task:**
 
-    1.  Set <instruction><getopt-arguments/></instruction> initially.
+    1.  Set <instruction><getopt-arguments/></instruction> initially, with any
+        leading and trailing whitespace stripped.
         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 id:
 
-        1.  <if condition="
-                <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
-            ">
-            Set <ase-task-id><instruction/></ase-task-id> (set task
-            id to instruction) and <instruction></instruction> (set
-            instruction empty), call the `ase_task_id(id: "<ase-task-id/>",
-            session: "<ase-session-id/>")` tool from the `ase` MCP
-            server to switch the task, and then only output the
-            following <template/>:
+        <expand name="task-react-id" arg1="ase-task-implement"></expand>
 
-            <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
-            </template>
-            </if>
-
-        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*
-            ">
-            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
-            switch the task, and then only output the following
-            <template/>:
-
-            <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
-            </template>
-            </elseif>
-
-        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/>
-            and then immediately *STOP* processing the entire current skill:
-
-            <template>
-            ⧉ **ASE**: ☻ skill: **ase-task-implement**, ▶ ERROR: expected single `[<id>]` argument
-            </template>
-            </elseif>
-
-2.  **Determine Operation**:
+2.  **Determine Operation:**
 
     1.  Determine the current task plan content:
 
-        <if condition="
-            <getopt-option-int-reuse-task/> is equal `true`
-            *and* a `ase_task_save(id: '<ase-task-id/>', ...)` tool call
-            exists earlier in the current session
-        ">
-            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).
-            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/>:
-
-        <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<status/>**
-        </template>
+        <expand name="task-load-content"></expand>
 
-    2.  If the <content/> is still empty, complain and tell the user to
+    2.  If the <task-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. Then
         immediately stop processing this skill.
@@ -134,15 +65,15 @@ Procedure
         by modifying the *artifacts* with a corresponding, complete
         *change set*.
 
-        For this, primarily follow and honor the task plan in <content/>.
+        For this, primarily follow and honor the task plan in <task-content/>.
 
         Secondarily, derive hints from the optionally existing
         `IMPLEMENTATION DRAFT` section (from skill `ase-task-preflight`)
-        in <content/>. But the specification text in <content/> always
+        in <task-content/>. But the specification text in <task-content/> always
         overrules the implementation draft in the `IMPLEMENTATION DRAFT`
-        section of <content/>.
+        section of <task-content/>.
 
-        <if condition="<content/> does NOT contain a `##  VERIFICATION` section heading">
+        <if condition="<task-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*
@@ -162,37 +93,13 @@ Procedure
 
     1.  *Determine next step*:
 
-        -   If <getopt-option-next/> is not equal to `none`:
-            Treat <getopt-option-next/> as a comma-separated chronological
-            list of pre-selected next-step tokens. *Split* it on `,`,
-            take the *first* token as <head/>, and store the remaining
-            tokens (joined back with `,`, or `none` if empty) into
-            <getopt-option-next/> so downstream skills can consume the tail.
-
-            -   If <head/> matches the regex `^(DONE|DELETE)$`:
-                Honor the pre-selected token.
-                Set <result><head/></result>.
-
-            -   else:
-                Only output the following <template/> and then immediately
-                *STOP* processing the entire current skill:
-
-                <template>
-                ⧉ **ASE**: ☻ skill: **ase-task-implement**, ▶ ERROR: invalid `--next` token: **<head/>**
-                </template>
-
-        -   If <getopt-option-next/> is equal to `none`:
-
-            In the following, you *MUST* *NOT* use your built-in
-            <user-dialog-tool/> tool! Instead, you *MUST* just show a
-            custom dialog according to the expanded `custom-dialog`
-            definition. You *MUST* closely follow this definition:
-
-            <expand name="custom-dialog" arg1="--no-other">
-                Next Step: How would you like to proceed with the plan?
-                DONE: Stop processing and PRESERVE task plan.
-                DELETE: Stop processing and DELETE the task plan.
-            </expand>
+        <expand name="task-next-select"
+            arg1="ase-task-implement"
+            arg2="DONE|DELETE">
+            Next Step: How would you like to proceed with the plan?
+            DONE: Stop processing and PRESERVE task plan.
+            DELETE: Stop processing and DELETE the task plan.
+        </expand>
 
     2.  Check the tool <result/> and dispatch accordingly:
 

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

@@ -27,6 +27,9 @@ List Task Plans
 *List* all available *task plans* of the current project.
 </objective>
 
+Procedure
+---------
+
 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

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

@@ -31,112 +31,43 @@ for a corresponding, *complete source code change set*.
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md
 
 Procedure
 ---------
 
 1.  **Determine Task:**
 
-    1.  Set <instruction><getopt-arguments/></instruction> initially.
+    1.  Set <instruction><getopt-arguments/></instruction> initially, with any
+        leading and trailing whitespace stripped.
         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 id:
 
-        1.  <if condition="
-                <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
-            ">
-            Set <ase-task-id><instruction/></ase-task-id> (set task
-            id to instruction) and <instruction></instruction> (set
-            instruction empty), call the `ase_task_id(id: "<ase-task-id/>",
-            session: "<ase-session-id/>")` tool from the `ase` MCP
-            server to switch the task, and then only output the
-            following <template/>:
-
-            <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
-            </template>
-            </if>
-
-        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*
-            ">
-            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
-            switch the task, and then only output the following
-            <template/>:
-
-            <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
-            </template>
-            </elseif>
-
-        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/>
-            and then immediately *STOP* processing the entire current skill:
-
-            <template>
-            ⧉ **ASE**: ☻ skill: **ase-task-preflight**, ▶ ERROR: expected single `[<id>]` argument
-            </template>
-            </elseif>
+        <expand name="task-react-id" arg1="ase-task-preflight"></expand>
 
 2.  **Determine Operation:**
 
     1.  Determine the current task plan content:
 
-        <if condition="
-            <getopt-option-int-reuse-task/> is equal `true`
-            *and* a `ase_task_save(id: '<ase-task-id/>', ...)` tool call
-            exists earlier in the current session
-        ">
-            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>
+        <expand name="task-load-content"></expand>
 
-        -   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/>:
-
-        <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<status/>**
-        </template>
-
-    2.  If the <content/> is still empty, complain and tell the user to
+    2.  If the <task-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. Then
         immediately stop processing this skill.
 
 3.  **Create Implementation Draft:**
 
-    1.  Perform a *preflight* of the *implementation* of <content/> by creating a
+    1.  Perform a *preflight* of the *implementation* of <task-content/> by creating a
         draft for a corresponding, *complete artifact change set*
-        which *would* fully implement the task plan <content/>. Store
+        which *would* fully implement the task plan <task-content/>. Store
         this artifact change set in *unified diff* format in <unified-diff/>.
 
     2.  Append this artifact change set <unified-diff/> to the end
-        of the <content/> with the following <template/>. If a section
+        of the <task-content/> with the following <template/>. If a section
         named `##  IMPLEMENTATION DRAFT` already exists from a
         previous run of this skill, *replace* this entire existing
         section.
@@ -151,20 +82,20 @@ Procedure
 
         </template>
 
-    3.  <if condition="<content/> contains '⚙   Modified:'">
+    3.  <if condition="<task-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
-        the `⚙   Modified: ...` line of <content/> with the new
+        the `⚙   Modified: ...` line of <task-content/> with the new
         `⚙   Modified: <timestamp-modified/>`.
         Do not output anything.
         </if>
 
     4.  Finally, call the `ase_task_save(id: "<ase-task-id/>",
-        text: "<content/>")` tool of the `ase` MCP server to save the updated
+        text: "<task-content/>")` tool of the `ase` MCP server to save the updated
         task plan content. Calculate the number of words <words/> of
-        <content/>. Do not output anything related to this MCP tool call
+        <task-content/>. Do not output anything related to this MCP tool call
         except the following <template/>:
 
         <template>
@@ -175,38 +106,14 @@ Procedure
 
     1.  *Determine next step*:
 
-        -   If <getopt-option-next/> is not equal to `none`:
-            Treat <getopt-option-next/> as a comma-separated chronological
-            list of pre-selected next-step tokens. *Split* it on `,`,
-            take the *first* token as <head/>, and store the remaining
-            tokens (joined back with `,`, or `none` if empty) into
-            <getopt-option-next/> so downstream skills can consume the tail.
-
-            -   If <head/> matches the regex `^(DONE|EDIT|IMPLEMENT)$`:
-                Honor the pre-selected token.
-                Set <result><head/></result>.
-
-            -   else:
-                Only output the following <template/> and then immediately
-                *STOP* processing the entire current skill:
-
-                <template>
-                ⧉ **ASE**: ☻ skill: **ase-task-preflight**, ▶ ERROR: invalid `--next` token: **<head/>**
-                </template>
-
-        -   If <getopt-option-next/> is equal to `none`:
-
-            In the following, you *MUST* *NOT* use your built-in
-            <user-dialog-tool/> tool! Instead, you *MUST* just show a
-            custom dialog according to the expanded `custom-dialog`
-            definition. You *MUST* closely follow this definition:
-
-            <expand name="custom-dialog" arg1="--no-other">
-                Next Step: How would you like to proceed with the plan?
-                DONE: Stop processing.
-                EDIT: Hand processing off to editing.
-                IMPLEMENT: Hand processing off to implementation.
-            </expand>
+        <expand name="task-next-select"
+            arg1="ase-task-preflight"
+            arg2="DONE|EDIT|IMPLEMENT">
+            Next Step: How would you like to proceed with the plan?
+            DONE: Stop processing.
+            EDIT: Hand processing off to editing.
+            IMPLEMENT: Hand processing off to implementation.
+        </expand>
 
     2.  Check the tool <result/> and dispatch accordingly:
 
@@ -244,6 +151,6 @@ Procedure
             the current skill once the `Skill` tool was used.
 
             <template>
-            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implement**
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implementation**
             </template>
 

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

@@ -31,13 +31,15 @@ based on the existing *WHAT* and *WHY*.
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md
 
 Procedure
 ---------
 
 1.  **Determine Task:**
 
-    1.  Set <instruction><getopt-arguments/></instruction> initially.
+    1.  Set <instruction><getopt-arguments/></instruction> initially, with any
+        leading and trailing whitespace stripped.
         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.
@@ -77,12 +79,12 @@ Procedure
         the `text` output field of the `ase_task_load` tool call.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
-            Set <content></content> (set content to empty).
+            Set <task-content></task-content> (set task 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/>.
+            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/>:
 
@@ -90,7 +92,7 @@ Procedure
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan loaded**
         </template>
 
-    2.  <if condition="<content/> is empty">
+    2.  <if condition="<task-content/> is 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. Then immediately stop processing
@@ -101,24 +103,24 @@ Procedure
 
     1.  Start with <instruction></instruction> (set instruction to empty).
 
-    2.  <if condition="<content/> contains neither '-   **WHAT**:' nor '-   **WHY**:'">
-        Set <instruction><content/></instruction> (set instruction to content).
+    2.  <if condition="<task-content/> contains neither '-   **WHAT**:' nor '-   **WHY**:'">
+        Set <instruction><task-content/></instruction> (set instruction to task content).
         </if>
 
-    3.  <if condition="<content/> contains '-   **WHAT**: <text/>'">
+    3.  <if condition="<task-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="<task-content/> contains '-   **WHY**: <text/>' and <instruction/> is empty">
         Set <instruction><text/></instruction> (set instruction to extracted text).
         </if>
 
-    5.  <if condition="<content/> contains '-   **WHY**: <text/>' and <instruction/> is NOT empty">
+    5.  <if condition="<task-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="<task-content/> contains '⎈   Created:  <text/>'">
         Set <timestamp-created><text/></timestamp-created> (set
         timestamp-created to extracted text)
         </if>
@@ -127,8 +129,8 @@ Procedure
         The WHAT/WHY extraction yielded no usable text (e.g. a
         `-   **WHAT**:` line existed but captured empty text, so the
         whole-content fallback above did not fire). Fall back to the
-        full previous plan content: set <instruction><content/></instruction>
-        (set instruction to content).
+        full previous plan content: set <instruction><task-content/></instruction>
+        (set instruction to task content).
         <if condition="<instruction/> is still empty or contains only whitespace">
             There is nothing to reboot from. Only output the following
             <template/> and then immediately *STOP* processing the entire
@@ -141,30 +143,16 @@ Procedure
         </if>
 
     8.  Create a new plan from scratch and store the result as
-        <content/> by closely following the defined plan format
+        <task-content/> by closely following the defined plan format
         <format/> and injecting into it all the information from
         the <instruction/> and all decisions you derived from the
         <instruction/>.
 
-    9.  Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-        `ase` MCP server and use the `text` field of its response for
-        <timestamp-modified/> information. If <timestamp-created/> is
-        still unset (because the previous <content/> had no `Created:`
-        line), set <timestamp-created><timestamp-modified/></timestamp-created>
-        (fall back to the modified timestamp). Then insert the current
-        <ase-task-id/>, previous <timestamp-created/>, and refreshed
-        <timestamp-modified/> information and calculate the number of
-        words <words/> of <content/>.
+    9.  <expand name="task-save-content" arg1="plan rebooted"></expand>
 
-    10. Call the `ase_task_save(id: "<ase-task-id/>",
-        text: "<content/>")` tool of the `ase` MCP server to save the updated
-        task plan content. Do not output anything related to this MCP
-        call.
-
-    11. Only output the following <template/> and continue processing:
+    10. Only output the following <template/> and continue processing:
 
         <template>
-        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan rebooted**
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
         </template>
 
@@ -172,39 +160,15 @@ Procedure
 
     1.  *Determine next step*:
 
-        -   If <getopt-option-next/> is not equal to `none`:
-            Treat <getopt-option-next/> as a comma-separated chronological
-            list of pre-selected next-step tokens. *Split* it on `,`,
-            take the *first* token as <head/>, and store the remaining
-            tokens (joined back with `,`, or `none` if empty) into
-            <getopt-option-next/> so downstream skills can consume the tail.
-
-            -   If <head/> matches the regex `^(DONE|EDIT|IMPLEMENT|PREFLIGHT)$`:
-                Honor the pre-selected token.
-                Set <result><head/></result>.
-
-            -   else:
-                Only output the following <template/> and then immediately
-                *STOP* processing the entire current skill:
-
-                <template>
-                ⧉ **ASE**: ☻ skill: **ase-task-reboot**, ▶ ERROR: invalid `--next` token: **<head/>**
-                </template>
-
-        -   If <getopt-option-next/> is equal to `none`:
-
-            In the following, you *MUST* *NOT* use your built-in
-            <user-dialog-tool/> tool! Instead, you *MUST* just show a
-            custom dialog according to the expanded `custom-dialog`
-            definition. You *MUST* closely follow this definition:
-
-            <expand name="custom-dialog" arg1="--no-other">
-                Next Step: How would you like to proceed with the plan?
-                DONE: Stop processing.
-                EDIT: Hand off plan to editing.
-                IMPLEMENT: Hand off plan to implementation.
-                PREFLIGHT: Hand off plan to pre-flighting.
-            </expand>
+        <expand name="task-next-select"
+            arg1="ase-task-reboot"
+            arg2="DONE|EDIT|IMPLEMENT|PREFLIGHT">
+            Next Step: How would you like to proceed with the plan?
+            DONE: Stop processing.
+            EDIT: Hand off plan to editing.
+            IMPLEMENT: Hand off plan to implementation.
+            PREFLIGHT: Hand off plan to pre-flighting.
+        </expand>
 
     2.  Check the tool <result/> and dispatch accordingly:
 

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

@@ -60,7 +60,7 @@ Procedure
         output anything related to this MCP tool call.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
-            Set <content></content> (set content to empty).
+            Set <task-content></task-content> (set task content to empty).
             Only output the following <template/>:
 
             <template>
@@ -68,18 +68,18 @@ Procedure
             </template>
 
         -   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/>.
+            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**
             </template>
 
-    2.  <if condition="<content/> is not empty">
-        Treat <content/> as *verbatim* Markdown.
+    2.  <if condition="<task-content/> is not empty">
+        Treat <task-content/> as *verbatim* Markdown.
         *Render plan*: Only output the following <template/>. If
-        <getopt-option-full/> is *not* `true`, <content/> is longer than
+        <getopt-option-full/> is *not* `true`, <task-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 `[...]`.
@@ -88,7 +88,7 @@ Procedure
 
         <template>
         <ase-tpl-head title="TASK"/>
-        <content/>
+        <task-content/>
         <ase-tpl-foot title="TASK"/>
         </template>
         </if>