/ase-task-implement

name: ase-task-implement
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
    "task", "plan", "spec", or "specification".
user-invocable: true
disable-model-invocation: false
effort: xhigh

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

<purpose name="ase-task-implement"> Implement a Task Plan </purpose>

<expand name="getopt" arg1="ase-task-implement" arg2="--next|-n=(none|DONE|DELETE)... --worktree|-w --int-reuse-task"> $ARGUMENTS </expand>

<objective> *Implement* the task plan by modifying the *artifacts* with a corresponding, complete *change set*. </objective>

@${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 ---------

1. **Determine Task:**

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:

<expand name="task-react-id" arg1="ase-task-implement"></expand>

2. **Determine Operation:**

1. Determine the current task plan content:

<expand name="task-load-content"></expand>

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. 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 *change set*.

For this, prim