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 <purpose name="ase-task-edit"> Iteratively Edit a Task Plan </purpose> <expand name="getopt" arg1="ase-task-edit" arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --dry|-d --next|-n=(none|DONE|GRILL|PREFLIGHT|IMPLEMENT)... --int-reuse-task"> $ARGUMENTS </expand> <objective> 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. </objective> @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md Procedure --------- <define name="apply-refinement"> Treat the <instruction/> as a *refinement instruction* for the plan, and update <task-content/> in-place by *applying* the requested <instruction/> 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. Attachment blocks of the "backmatter" are *never* dropped by a refinement. Instead, *remember* every attachment block whose content the applied <instruction/> changed as *touched*, so its `Modified` key is refreshed together with the frontmatter in step 3.1. An attachment the <instruction/> did not change stays *verbatim* -- an implementation dr...