@rse/ase 0.9.53 → 0.9.55

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

@@ -40,6 +40,7 @@ From scratch *craft* the following feature:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-code.md
 
 Procedure
 ---------
@@ -127,11 +128,11 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
 3.  <step id="STEP 3: Internalize Crafting Tenets">
 
-    1.  You *MUST* internalize and strictly honor the **GENERIC TENETS**,
-        and the **CRAFTING TENETS** of the **ASE Tenets** when updating
-        in the following. Do not output anything.
+    1.  <task-kind>CRAFTING</task-kind>
 
-    2.  Do not output anything in this STEP 3.
+    2.  <expand name="code-tenets" arg1="<task-kind/>"></expand>
+
+    3.  Do not output anything in this STEP 3.
 
     </step>
 
@@ -251,9 +252,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  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-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/>.
+        insert the current <ase-task-id/>, <timestamp-created/>,
+        <timestamp-modified/>, and <task-kind/> information and calculate
+        the number of words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
         `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.

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

@@ -64,8 +64,8 @@ A05 COMPLEXITY     A10 SMELLS           A15 PERFORMANCE     A20 DEAD-CODE
 
 `--exclude`|`-e`=*aspect*[`,`...]:
     Remove the given comma-separated list of aspect ids from the checked
-    code quality aspects. Applied *after* `--include`, so `-i A01,A02 -e
-    A02` checks `A01` only.
+    code quality aspects. Applied *after* `--include`, so
+    `-i A01,A02 -e A02` checks `A01` only.
 
 ##  ARGUMENTS
 

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

@@ -40,6 +40,7 @@ to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-code.md
 
 Procedure
 ---------
@@ -127,11 +128,11 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
 3.  <step id="STEP 3: Internalize Refactoring Tenets">
 
-    1.  You *MUST* internalize and strictly honor the **GENERIC TENETS**,
-        and the **REFACTORING TENETS** of the **ASE Tenets** when updating
-        in the following. Do not output anything.
+    1.  <task-kind>REFACTORING</task-kind>
 
-    2.  Do not output anything in this STEP 3.
+    2.  <expand name="code-tenets" arg1="<task-kind/>"></expand>
+
+    3.  Do not output anything in this STEP 3.
 
     </step>
 
@@ -251,9 +252,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  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-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/>.
+        insert the current <ase-task-id/>, <timestamp-created/>,
+        <timestamp-modified/>, and <task-kind/> information and calculate
+        the number of words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
         `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.

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

@@ -40,6 +40,7 @@ to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-code.md
 
 Procedure
 ---------
@@ -181,11 +182,11 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
 3.  <step id="STEP 3: Internalize Problem Resolution Tenets">
 
-    1.  You *MUST* internalize and strictly honor the **GENERIC TENETS**,
-        and the **RESOLVING TENETS** of the **ASE Tenets** when updating
-        in the following. Do not output anything.
+    1.  <task-kind>RESOLVING</task-kind>
 
-    2.  Do not output anything in this STEP 3.
+    2.  <expand name="code-tenets" arg1="<task-kind/>"></expand>
+
+    3.  Do not output anything in this STEP 3.
 
     </step>
 
@@ -305,9 +306,9 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     2.  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-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/>.
+        insert the current <ase-task-id/>, <timestamp-created/>,
+        <timestamp-modified/>, and <task-kind/> information and calculate
+        the number of words <words/> of <task-content/>.
 
     3.  You then *MUST* *save* the resulting plan content with the
         `ase_task_save(id: "<ase-task-id/>", text: "<task-content/>")`.

package/plugin/skills/ase-meta-config/help.md

@@ -67,9 +67,9 @@ The following *operations* exist:
 The `init` and `edit` subcommands of the `ase config` CLI are
 deliberately *not* mirrored: `edit` is bound to the interactive `$EDITOR`
 and therefore has no meaning inside an assistant turn, and `init` is a
-preset-bootstrapping operation that stays a shell concern next to `ase
-setup`. Both remain available as `ase config init` and `ase config edit`
-on the command line.
+preset-bootstrapping operation that stays a shell concern next to
+`ase setup`. Both remain available as `ase config init` and
+`ase config edit` on the command line.
 
 ##  OPTIONS
 

package/plugin/skills/ase-meta-quotes/help.md

@@ -39,9 +39,10 @@ without any quote is rendered as `(none)`.
 
 Every quote is rendered on its own line and carries, where applicable,
 the suffixes `— <author>, <origin>` (in the two `ATTRIBUTED`
-quadrants, omitting whichever part is unknown), `[from proximity:
-<source-topic>]` (when the quote was contributed by a neighborhood topic
-under `--proximity` instead of by *topic-keywords* itself), and
+quadrants, omitting whichever part is unknown),
+`[from proximity: <source-topic>]` (when the quote was contributed by a
+neighborhood topic under `--proximity` instead of by *topic-keywords*
+itself), and
 `(unverified)` (when the exact wording or the attribution could not be
 established with confidence). The `(unverified)` marker is dropped as
 soon as the Internet/Web search under `--ground` confirms the wording and

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

@@ -98,7 +98,7 @@ Set <args></args> (set args to empty).
         Set <words-before><words/></words-before> (remember the loaded
         word count for the strictly-smaller check in step 3).
 
-        <if condition="<task-content/> contains '⎈   Created:  <text/>'">
+        <if condition="the frontmatter of <task-content/> carries a `Created: <text/>` key">
         Set <timestamp-created><text/></timestamp-created> (extract the
         original creation timestamp so it can be re-inserted unchanged
         into the condensed <task-content/> in step 3).
@@ -125,10 +125,11 @@ Set <args></args> (set args to empty).
         and unchanged*. Honor the following ruleset *strictly*:
 
         1.  *Preserve-exactly (never alter)*: the plan <format/>
-            structure (the headings `#`/`##`, all three `##  CONTEXT`,
-            `##  CHANGES`, and `##  VERIFICATION` sections, the
-            `Created:`/`Modified:` lines, and
-            the `- **<aspect/>**:` bullet labels), all *code spans* and
+            structure (the frontmatter block with its `Id:`, `Created:`,
+            `Modified:`, `Status:`, `Properties:`, and `Kind:` keys,
+            the headings `#`/`##`, all
+            three `##  CONTEXT`, `##  CHANGES`, and `##  VERIFICATION`
+            sections, and the `- **<aspect/>**:` bullet labels), all *code spans* and
             code blocks, technical terms, file paths, identifiers,
             numbers, severities (`LOW`/`MEDIUM`/`HIGH`/`ACCEPTED`), and
             the `*<aspect/>*` emphasis highlighting convention.

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

@@ -30,7 +30,7 @@ telegrapher-like even under the `writer` persona.
 
 The plan is saved *only* when condensing actually makes it smaller; if no
 further reduction is possible, the plan is left untouched (including its
-`⚙   Modified:` timestamp) and reported as *already condensed*.
+`Modified:` frontmatter timestamp) and reported as *already condensed*.
 
 After condensing, the user is asked whether to stop or hand off to
 `ase-task-edit`, `ase-task-implement`, or `ase-task-preflight`, unless

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

@@ -322,13 +322,13 @@ Set <args></args> (set args to empty).
     `PREFLIGHT`, or declines/cancels in the dialog of step 3.4:
 
     1.  *Update timestamp*:
-        <if condition="<task-content/> contains '⚙   Modified:' AND <task-content-dirty/> is 'true'">
+        <if condition="the frontmatter of <task-content/> carries a `Modified:` key AND <task-content-dirty/> is 'true'">
         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 <task-content/> with the new
-        `⚙   Modified: <timestamp-modified/>`.
+        the `Modified: ...` frontmatter key of <task-content/> with the
+        new <timestamp-modified/> value.
         Do not output anything.
         </if>
 
@@ -346,6 +346,27 @@ Set <args></args> (set args to empty).
         </if>
 
     3.  *Render plan*: Treat <task-content/> as *verbatim* Markdown.
+
+        For the *rendering only*, drop the leading *frontmatter* block --
+        both `---` delimiters and all of their keys -- and instead place
+        the following column-aligned glyph lines *before* the
+        `#   TASK: <title/>` heading, separated from it by an empty line,
+        omitting the line of every key absent from the frontmatter. The
+        glyph lines *MUST* stay *above* the heading, exactly where the
+        frontmatter block sits in the plan file, and *MUST NOT* be moved
+        below it. This keeps the `---` delimiters from rendering as a
+        horizontal rule plus a *setext heading*. This rewrite is
+        *display-only* and *MUST NOT* change <task-content/> itself:
+
+        <format>
+        ◉   **Id:**         <task-id/>
+        ⎈   **Created:**    <timestamp-created/>
+        ⚙   **Modified:**   <timestamp-modified/>
+        ◐   **Status:**     <task-status/>
+        ⚑   **Properties:** <task-properties/>
+        ☯   **Kind:**       <task-kind/>
+        </format>
+
         Only output the following <template/>, so the user
         can read the plan and react to it. If <task-content/> is longer
         than 90 lines and a `##  IMPLEMENTATION DRAFT` section (from the
@@ -355,9 +376,9 @@ Set <args></args> (set args to empty).
         Use the following <template/>:
 
         <template>
-        <ase-tpl-head title="TASK"/>
+        <ase-tpl-head title="TASK" subtitle="<task-id/>"/>
         <task-content/>
-        <ase-tpl-foot title="TASK"/>
+        <ase-tpl-foot title="TASK" subtitle="<task-id/>"/>
         </template>
 
     4.  *Determine next step*:

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

@@ -216,7 +216,7 @@ Set <args>--int-reuse-task</args>.
 
     2.  Finally, update the plan in <plan/> based on all answers <answer-N/>.
 
-    3.  <if condition="<plan/> contains '⎈   Created:  <text/>'">
+    3.  <if condition="the frontmatter of <plan/> carries a `Created: <text/>` key">
         Set <timestamp-created><text/></timestamp-created> (set
         timestamp-created to extracted text)
         </if>
@@ -225,11 +225,15 @@ Set <args>--int-reuse-task</args>.
         `ase` MCP server and use the `text` field of its response for
         <timestamp-modified/> information. If <timestamp-created/> is
         still unset (because the previous <plan/> had no `Created:`
-        line), set <timestamp-created><timestamp-modified/></timestamp-created>
+        frontmatter key), 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 <plan/>.
+        <timestamp-modified/> information into the frontmatter keys `Id:`,
+        `Created:`, and `Modified:` and calculate the number of
+        words <words/> of <plan/>. Additionally *add* the value `grilled`
+        to the `Properties:` frontmatter key if it is still absent,
+        keeping all already present values and *creating* the whole key
+        (with the single value `grilled`) if the plan carries none.
 
     5.  Call the `ase_task_save(id: "<ase-task-id/>",
         text: "<plan/>")` tool of the `ase` MCP server to save the updated

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

@@ -24,7 +24,8 @@ the code base and world knowledge), marks the current-plan choice, and
 lets the user pick via an interactive dialog. It honors checks for
 *fuzzy language*, *conflicting terminology*, *conflicting code*, and
 *non-concrete scenarios*. Once all aspects are resolved, the plan is
-updated and persisted, and the user is offered a hand-off to editing,
+updated and persisted, its `Properties:` frontmatter key gains the value
+`grilled`, and the user is offered a hand-off to editing,
 implementation, or preflight.
 
 ##  OPTIONS

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-implement
-argument-hint: "[--help|-h] [--next|-n <option>[,...]] [<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>[,...]] [--worktree|-w] [<id>]"
 description: >
     Implement current or given task plan.
     Use when the user calls to "implement", "realize" or "apply" the
@@ -21,7 +21,7 @@ Implement a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-implement"
-    arg2="--next|-n=(none|DONE|DELETE)... --int-reuse-task">
+    arg2="--next|-n=(none|DONE|DELETE)... --worktree|-w --int-reuse-task">
     $ARGUMENTS
 </expand>
 
@@ -32,6 +32,8 @@ with a corresponding, complete *change set*.
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-code.md
 
 Procedure
 ---------
@@ -59,7 +61,98 @@ Procedure
         or `ase-task-edit` skills first to create a task plan. Then
         immediately stop processing this skill.
 
-3.  **Create Implementation:**
+    3.  Internalize the tenets stated by the plan:
+
+        <expand name="code-tenets-from-plan"></expand>
+
+3.  **Prepare WorkTree:**
+
+    <if condition="<getopt-option-worktree/> is not equal `true`">
+    No worktree was requested, so the implementation is applied directly
+    to the *current* working copy. Set <worktree-dir></worktree-dir>
+    (empty) and *skip* all remaining sub-steps of this step. Do not
+    output anything.
+    </if>
+
+    1.  Set <worktree-name><ase-task-id/></worktree-name>. The worktree
+        is *never* named by an own option value: it always carries the
+        unique *task id*, so the worktree directory and its branch stay
+        unambiguously tied to the very task plan implemented in them.
+        The task id is a plain identifier by construction, hence it is
+        directly usable as both a directory and a branch name. Do not
+        output anything.
+
+    2.  Determine the *repository root* by running the corresponding
+        command (taken exactly as given) and capturing its output into
+        <repo-root/>:
+
+        `git rev-parse --show-toplevel`
+
+        <if condition="this command fails">
+        The current directory is no Git repository, so no worktree can be
+        created. Only output the following <template/> and then
+        immediately *STOP* processing the entire current skill, leaving
+        the working copy *untouched*:
+
+        <template>
+        ⧉ **ASE**: ☻ skill: **ase-task-implement**, ▶ ERROR: no Git repository -- cannot create worktree
+        </template>
+        </if>
+
+        Then set <worktree-dir><repo-root/>/.ase/worktree/<worktree-name/></worktree-dir>.
+
+    3.  Determine the *existing worktrees* and *existing branches* by
+        running the corresponding commands (taken exactly as given) and
+        capturing their outputs:
+
+        `git worktree list --porcelain`
+
+        `git branch --list`
+
+        <if condition="the worktree directory <worktree-dir/> or the branch <worktree-name/> already exists">
+        Only output the following <template/> and then immediately *STOP*
+        processing the entire current skill, leaving the existing
+        worktree, its branch, and the working copy *untouched*:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ ERROR: worktree or branch **<worktree-name/>** already exists
+        </template>
+
+        Directly *after* this error <template/>, and *before* stopping,
+        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">
+        Remove the existing worktree via `git worktree remove` and `git branch -d`, or rename the task via `/ase-task-rename` to implement it under a still unused worktree name.
+        </ase-tpl-hint>
+        </if>
+
+    4.  Create the worktree by running the corresponding command (taken
+        exactly as given), which creates the directory *and* -- named
+        after its last path component -- the branch <worktree-name/> from
+        `HEAD`. The `.ase` directory is usually git-ignored, so the
+        worktree itself never shows up as a change:
+
+        `git worktree add "<worktree-dir/>"`
+
+        <if condition="this command fails">
+        Only output the following <template/> and then immediately *STOP*
+        processing the entire current skill, leaving the working copy
+        *untouched*:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ ERROR: worktree **<worktree-name/>** failed to create
+        </template>
+        </if>
+
+    5.  Only output the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ◉ worktree: **.ase/worktree/<worktree-name/>**, ▶ status: **worktree created**
+        </template>
+
+4.  **Create Implementation:**
 
     1.  Perform a *final implementation* of the task plan
         by modifying the *artifacts* with a corresponding, complete
@@ -73,6 +166,19 @@ Procedure
         overrules the implementation draft in the `IMPLEMENTATION DRAFT`
         section of <task-content/>.
 
+        <if condition="<worktree-dir/> is not empty">
+        The change set *MUST* land *exclusively inside* the worktree
+        <worktree-dir/>: resolve *every* file path of the task plan
+        relative to <worktree-dir/> instead of the original working copy,
+        and run *every* verification command (build, tests, linter,
+        type-checker, program execution) with <worktree-dir/> as its
+        working directory. You *MUST* *NEVER* modify, stage, stash,
+        revert, or commit anything *outside* of this worktree. Leave the
+        worktree *uncommitted*: do *not* run `git add` and do *not* run
+        `git commit`, so the user keeps full control over the final
+        commit.
+        </if>
+
         <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
@@ -83,13 +189,52 @@ Procedure
         way.
         </if>
 
-    2.  Only output the following <template/>:
+    2.  Update the frontmatter of <task-content/> as follows, *creating*
+        each of the `Properties:`, `Status:`, and `Modified:` keys the
+        plan does not carry yet at its position in the key order of the
+        plan <format/>:
+
+        -   *Add* the value `implemented` to the `Properties:` key if it
+            is still absent, keeping all already present values.
+
+        -   *Add* the value `verified` to the `Properties:` key as well,
+            but *only* if the verification phase was actually performed
+            and succeeded -- hence *never* for a plan whose
+            `##  VERIFICATION` section is deliberately omitted.
+
+        -   Set the `Status:` key to `COMPLETED`, but *only* if the
+            change set was applied *completely* and *successfully* --
+            this traverses the `start` and `complete` transitions of the
+            state machine of the plan <format/> in one go. Otherwise
+            leave the `Status:` key *untouched*, as an incomplete run
+            transitioned nowhere.
+
+        -   Refresh the `Modified:` key with the current time in
+            ISO-style format, determined by calling the
+            `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
+            MCP server.
+
+        Then 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.
+
+    3.  Only output the following <template/>:
 
         <template>
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented**
         </template>
 
-4.  **Decide Next Step:**
+    4.  <if condition="<worktree-dir/> is not empty">
+        Give the closing 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 change set is uncommitted in `.ase/worktree/<worktree-name/>` on branch `<worktree-name/>` -- review and commit it there, then remove the worktree via `git worktree remove`.
+        </ase-tpl-hint>
+        </if>
+
+5.  **Decide Next Step:**
 
     1.  *Determine next step*:
 

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

@@ -8,6 +8,7 @@
 `ase-task-implement`
     [`--help`|`-h`]
     [`--next`|`-n` *option*[,...]]
+    [`--worktree`|`-w`]
     [*id*]
 
 ##  DESCRIPTION
@@ -16,7 +17,18 @@ 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.
+plan content always overrules the draft. 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
+completely and successfully.
+
+The *kind of change* stated by the plan's `Kind:` frontmatter key
+(`CRAFTING`, `REFACTORING`, or `RESOLVING`) selects which
+*operation-specific tenet set* of the **ASE Tenets** is internalized
+before any artifact is touched, in addition to the always applying
+**GENERIC TENETS**. If a plan carries no such key, the kind is
+*inferred* from the plan content, defaulting to `CRAFTING`.
 
 If the task plan deliberately *omits* the `##  VERIFICATION` section
 (as produced by `ase-code-craft`, `ase-code-refactor`,
@@ -25,6 +37,17 @@ the entire verification phase is strictly skipped: no build, tests,
 linter, type-checker, or program execution is performed once the
 source files have been modified.
 
+With `--worktree`|`-w`, the change set is *not* applied to the current
+working copy: a *fresh Git WorkTree* `.ase/worktree/<id>` and its
+equally named branch are created from `HEAD` *before* any artifact is
+touched, and the entire implementation -- including all verification
+runs -- then happens *inside* that worktree, which is left
+*uncommitted*. The worktree is *not* named by an option value: it
+always carries the unique *task id*, so worktree and branch stay tied
+to the very task plan implemented in them. As the worktree branches off
+`HEAD`, *uncommitted* changes of the current working copy are *not*
+carried over into it.
+
 After implementation, the user is asked whether to preserve or
 delete the task plan, unless `--next` pre-selects this choice.
 
@@ -40,6 +63,14 @@ delete the task plan, unless `--next` pre-selects this choice.
     answer required), `DONE` (preserve task plan and stop), or
     `DELETE` (hand off to `ase-task-delete`).
 
+`--worktree`|`-w`:
+    Apply the change set inside a dedicated *Git WorkTree* instead of
+    the current working copy. The worktree directory `.ase/worktree/<id>`
+    and its equally named branch are derived from the *task id* and
+    created from `HEAD`. If either the directory or the branch already
+    exists, the skill stops and touches nothing. By default, the change
+    set is applied to the current working copy.
+
 ##  ARGUMENTS
 
 *id*:
@@ -60,7 +91,15 @@ Implement a specific task and delete the plan when done:
 ❯ /ase-task-implement --next DELETE hello
 ```
 
+Implement the task `hello` inside the isolated Git WorkTree
+`.ase/worktree/hello`:
+
+```text
+❯ /ase-task-implement --worktree hello
+```
+
 ##  SEE ALSO
 
 [`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md),
 [`ase-task-view`](../ase-task-view/help.md), [`ase-task-delete`](../ase-task-delete/help.md).
+