Ase task implement

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

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

<expand name="getopt" arg1="ase-task-implement" arg2="--next|-n=(none|DONE|DELETE)... --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

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. Create Implementation:

   1. Perform a final implementation of the task plan by modifying the artifacts with a corresponding, complete change set.

      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 <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/> 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, do *NOT* run any type-checker, do *NOT* execute the modified program, and do *NOT* otherwise verify the change set in any way. </if>

   2. Only output the following <template/>:

      <template> ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented** </template>

4. Decide Next Step:

   1. Determine next step:

      <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:

      • If <result/> is DONE or CANCEL: Only output the following <template/> and then STOP.

        <template> ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan implemented -- done** </template>

      • If <result/> is DELETE: Set <args></args> (empty). Do not forward any remaining --next list tokens, because the ase:ase-task-delete skill accepts only an optional [<id>] argument and no --next option; remaining tokens are intentionally discarded. Only output the following <template/> and then call the tool Skill(skill: "ase:ase-task-delete", args: "<args/>") to invoke the ase:ase-task-delete skill in order to delete the updated plan. Immediately stop processing the 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** </template>