ase-task-edit

name	ase-task-edit
argument-hint	[--help|-h] [--plan|-p <option>] [--dry|-d] [--next|-n <option>[,...]] [<id> | <id>: <instruction> | <instruction>]
description	Iteratively edit and refine a named plan for a task through a conversational loop. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or preflight. Use when the user wants to plan a task purely through chat-driven refinement.
user-invocable	true
disable-model-invocation	false
effort	high

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

Iteratively Edit a Task Plan

$ARGUMENTS

Establish and refine the *task plan* purely through a *chat-driven loop*. The user steers each round via an interactive dialog that offers continued refinement, finalization, or hand-off to implementation or preflight.

@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md

Procedure

Treat the as a *refinement instruction* for the plan, and update in-place by *applying* the requested to the *plan*.

When refining the plan this way, preserve the overall structure of the plan and only modify what the user actually requested. Do not rewrite unrelated sections of the plan.

Calculate the number of words of . Set true.

Create a new plan from scratch and store the result as by closely following the defined plan format and injecting into it all the information from the and all decisions you derived from the .

If a CHANGELOG.md file exists in the project (or in any affected sub-package), the plan MUST include, as part of its ## CHANGES section, an explicit bullet point describing the addition of a corresponding new entry to that CHANGELOG.md file, aligned with its existing style and conventions.

You *MUST* completely omit the `## VERIFICATION` section (including its heading and all of its bullet points) from .

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 fresh and information. Then insert the current , , and information and calculate the number of words of . Set true.

1. Determine Task and Instruction:

   1. Set initially. Inherit the always existing from the current context. Inherit the always existing from the current context. Do not output anything.

   2. React on task and/or instruction:

      1. Set (set task id to instruction) and (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