Ase Task Edit

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

$ARGUMENTS

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

Procedure

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.

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.

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 :

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

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

      4. Only output the following :

      5. Only output the following :

2. Determine Plan:

   1. Determine any existing plan content:

      Set to the text argument of the most recent ase_task_save(id: '<ase-task-id/>', ...) tool call, without calling ase_task_load again. Set plan reused. Do not output anything.

      Set false.

      • If starts with ERROR:: Silently ignore the MCP error. Set to empty. Set to "0". Do not output anything.

      • If starts NOT with ERROR:: Set (set content to text). Calculate the number of words of . Only output the following :

   2. **No plan content yet. What is the task you want to plan?**

      Then set to the response of the user and only output the following :

   3. Determine previous-plan handling:

      • If matches the regex ^(OVERWRITE|REFINE|PRESERVE)$: Honor the pre-selection what to do with the previous plan. Set .

      • If is equal to none:

        In the following, you MUST NOT use your built-in tool! Instead, you MUST just show a custom dialog according to the expanded custom-dialog definition. You MUST closely follow this definition:

      Check the tool and dispatch accordingly:

      • If is CANCEL or PRESERVE:

        Only output the following and then immediately STOP processing this skill:

      • If is OVERWRITE:

        Only output the following and continue processing:

      • If is REFINE:

        Only output the following and continue processing:

      • If matches OTHER: <text/>:

        Set (append the user's free-text hint to the existing instruction).

        Only output the following and continue processing:

   5. Only output the following and continue processing:

3. Iterative Plan Refinement Loop:

   REPEAT the following steps from 3.1 up to and including 3.4 in a LOOP until the user selects DONE, GRILL, IMPLEMENT, or PREFLIGHT, or declines/cancels in the dialog of step 3.4:

   1. Update timestamp:

   2. Persist plan:

   3. Render plan: Treat as verbatim Markdown. Only output the following , so the user can read the plan and react to it. If is longer than 90 lines and a ## IMPLEMENTATION DRAFT section (from the companion skill ase-task-preflight) exists, replace the entire content of the ## IMPLEMENTATION DRAFT section with [...]. Else, do not truncate, summarize, or partially show the plan. Use the following :

   4. Determine next step:

      • If is not equal to none: Treat as a comma-separated chronological list of pre-selected next-step tokens. Split it on ,, take the first token as , and store the remaining tokens (joined back with ,, or none if empty) into so subsequent loop iterations or downstream skills can consume the tail.

        • If matches the regex ^(DONE|GRILL|IMPLEMENT|PREFLIGHT)$: Honor the pre-selected token. Set .

          Set (clear the instruction, as any instruction carried in via the arguments was already applied to the plan in step 2 before this loop), so that a later OTHER: <text/> refinement correctly starts from a fresh refinement instruction below.

        • else: Only output the following and then immediately STOP processing the entire current skill:

      • If is equal to none:

        In the following, you MUST NOT use your built-in tool! Instead, you MUST just show a custom dialog according to the expanded custom-dialog definition. You MUST closely follow this definition:

      Check the tool and dispatch accordingly:

      • If is DONE:

        Break out of the loop, only output the following and then STOP. Do not implement the plan.

      • If is GRILL:

        Break out of the loop. Set (set args to empty).

      • If is PREFLIGHT:

        Break out of the loop. Set (set args to empty).

      • If is IMPLEMENT:

        Break out of the loop. Set (set args to empty).

      • If matches OTHER: <text/>:

        Set (replace existing instruction).

        Finally, only output the following and then continue the loop at step 3.1!

      • If is CANCEL:

        Break out of the loop, only output the following and then STOP. Do not implement the plan.