/ase-task-implement

name: ase-task-implement
argument-hint: "[--help|-h] [--next|-n <option>[,...]] [--worktree|-w <name>] [--source|-s <source>] [--changeset|-c <changeset>] [--draft|-d] [--no-cleanup|-K] [--stateless|-S] [<id>]"
description: >
    Implement current or given task plan, optionally as an implementation
    draft attachment only. Use when the user calls to "implement", "realize",
    "draft", "dry-run", or "test-drive" 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|EDIT|INTEGRATE|DELETE)... --worktree|-w= --source|-s= --changeset|-c= --draft|-d --no-cleanup|-K --stateless|-S --int-reuse-task"> $ARGUMENTS </expand>

<objective> *Implement* the task plan by creating a corresponding, complete *change set* from its *source* into its *changeset* location. </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 @${CLAUDE_SKILL_DIR}/../../meta/ase-common-changeset.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>

3. Resolve the draft shorthand: if <getopt-option-draft/> is `true` and <getopt-option-changeset/> is not empty, only output the following <template/> and then immediately *STOP* processing the entire current skill:

<template> ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ ERROR: options `--draft` and `--changeset` are mutually exclusive </template>

Otherwise, if <getopt-option-draft/> is `true`, set <getopt-option-changeset>attachment:draft</getopt-option-changeset>, so the change set lands as the *implementation draft* in the attachment `draft` of the plan only. Do not output anything.

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-task-edit` skill 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 Source and Changeset:**

The *source* (code basis) and the *changeset* (location of the change set) are controlled by the `Source:` and `Changeset:` frontmatter keys of the plan, which the `--source` and `--changeset` options override *ad-hoc* without changing the plan. The `worktree` value of the source refers to the *origin working copy* the skill was started in, the `worktree` value of the changeset to the *context worktree*, selected by the `--worktree` option (both are the same without `--worktree`). A context worktree created by `--worktree` carries its *own* branch, which starts at the source, so the source branch itself is never checked out there and stays available as the integration target.

1. Set <task-source/> to <getopt-option-source/> if it is not empty, otherwise to the value of the `Source:` frontmatter key of <task-content/>, or to the configured default <ase-project-task-default-source/> if the key is absent, and parse it:

<expand name="changeset-value" arg1="Source" arg2="<task-source/>" arg3="`worktree`, `branch`" arg4="◉ task: **<ase-task-id/>**"></expand>

Set <source-type><value-type/></source-type> and <source-name><value-name/></source-name>.

2. Set <task-changeset/> to <getopt-option-changeset/> if it is not empty, otherwise to the value of the `Changeset:` frontmatter key of <task-content/>, or to the configured default <ase-project-task-default-changeset/> if the key is absent, and parse it:

<expand name="changeset-value" arg1="Changeset" arg2="<task-changeset/>" arg3="`worktree`, `branch`, `attachment`" arg4="◉ task: **<ase-task-id/>**"></expand>

Set <changeset-type><value-type/></changeset-type> and <changeset-name><value-name/></changeset-name>.

<if condition="<task-changeset/> is not `attachment:draft` and the backmatter of <task-content/> contains an attachment block with the `Type` key value `text/x-diff; charset=utf-8; kind="draft"`, whose `Desc` key carries no `merged <commit/>` value"> The plan carries an undelivered *implementation draft*, which only an `attachment:draft` changeset builds upon, so this run *ignores* it and implements the plan from scratch into <task-changeset/>. Only output the following <template/>, directly followed by the hint, and then *continue* processing:

<template> ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ WARNING: implementation draft attachment is **ignored** for changeset **<task-changeset/>** </template>

<ase-tpl-hint level="minimal"> Use `/ase-task-implement --draft` to build upon the draft, or `/ase-task-integrate --draft` to deliver it. </ase-tpl-hint> </if>

3. D