@rse/ase 0.0.31 → 0.0.33

package/plugin/skills/ase-code-analyze/SKILL.md

@@ -32,6 +32,7 @@ code, for problems in its *logic* and *semantics* and its related
 </objective>
 
 <flow>
+
 1. <step id="STEP 1: Investigate Code Base">
    In this STEP 1, investigate on the code. If the code base is large,
    you *MUST* use the `Agent` tool (not inline work) to create multiple
@@ -104,5 +105,6 @@ code, for problems in its *logic* and *semantics* and its related
    ⧉ **ASE**: ↪ hint: **For deeper analysis, suggestions on solution approaches and then final problem resolution, use `/ase-code-resolve P{n}` in the same or even a different session.**
    </template>
    </step>
+
 </flow>
 

package/plugin/skills/ase-code-craft/SKILL.md

@@ -14,6 +14,7 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 Craft Feature
 =============
@@ -22,13 +23,19 @@ Craft Feature
 Craft Source Code
 </skill>
 
+<expand name="getopt"
+    arg1="ase-code-craft"
+    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    $ARGUMENTS
+</expand>
+
 <role>
 Your role is an experienced, *expert-level software developer*.
 </role>
 
 <objective>
 From scratch *craft* the following feature:
-<feature>$ARGUMENTS</feature>
+<feature><getopt-arguments/></feature>
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
@@ -42,6 +49,10 @@ You *MUST* not skip any numbered item during processing!
 You *MUST* *NOT* output anything in this entire procedure, *except* when
 explicitly requested by this procedure via outputs based on a <template/>!
 
+You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
+filesystem-modifying tool during this entire skill. The *only*
+permitted way to persist artifacts is via `task_save(...)`.
+
 1.  **Reason About Feature**:
 
     1.  <if condition="
@@ -156,19 +167,31 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 4.  **Choose Feature Crafting Approach**:
 
-    1.  Let the *user interactively choose* the preferred feature approach A<n/>
+    1.  If <getopt-option-auto/> is equal `true`:
+        Let the *user interactively choose* the preferred feature approach A<n/>
         with the help of the <user-dialog-tool/> tool. Use *single-selection* only
         and provide small *code change previews*. Mark your recommended
         feature approach with ` ⚝ **RECOMMENDATION** ⚝` here again.
 
-5.  **Write Feature Crafting Plan**:
+    2.  If <getopt-option-auto/> is not equal `true`:
+        Set <n/> to the number of the feature approach A<n/> you recommend.
+        Output a hint with the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **auto-chosen approach A<n/>**
+        </template>
 
-    1.  *Write a feature plan* for the chosen feature A<n/> by
+5.  **Compose Feature Crafting Plan**:
+
+    1.  *Compose a feature plan* for the chosen feature A<n/> by
         closely aligning to the existing architecture and the existing
         code base. Use the <format/> defined for a task plan and inject
         the information from feature A<n/> and all derived realization
         decisions into it. Store the resulting task plan in <content/>.
 
+        You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
+        filesystem-modifying tool during this step.
+
     2.  Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
         `ase` MCP service and use the `text` field of its response for
         <timestamp-created/> and <timestamp-modified/> information. Then
@@ -185,16 +208,22 @@ explicitly requested by this procedure via outputs based on a <template/>!
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    5.  *Ask user*: Let the *user interactively choose*
-        what to do as the next step.
+    5.  *Determine next step*:
+
+        -   If <getopt-option-next/> matches the regex `^(DONE|EDIT|PREFLIGHT|IMPLEMENT)$`:
+            Honor the pre-selection what to do as the next step.
+            Set <result><getopt-option-next/></result>.
+
+        -   If <getopt-option-next/> is equal to `none`:
+            Let the *user interactively choose* what to do as the next step.
 
-        <expand name="user-dialog>
-        Next Step: How would you like to proceed with the plan?
-        DONE: Stop processing.
-        EDIT: Hand processing off to editing.
-        PREFLIGHT: Hand processing off to preflighting.
-        IMPLEMENT: Hand processing off to implementation.
-        </expand>
+            <expand name="user-dialog>
+                Next Step: How would you like to proceed with the plan?
+                DONE: Stop processing.
+                EDIT: Hand processing off to editing.
+                PREFLIGHT: Hand processing off to preflighting.
+                IMPLEMENT: Hand processing off to implementation.
+            </expand>
 
     6.  Check the tool <result/> and dispatch accordingly:
 

package/plugin/skills/ase-code-explain/SKILL.md

@@ -27,6 +27,7 @@ code and *explain* it in *brief*, *standardized*, and *concise* way.
 </objective>
 
 <flow>
+
 1.  <step id="STEP 1: Investigate Code Base">
     Investigate on the code. If the code base is large, you *MUST* use
     the `Agent` tool (not inline work) to create multiple sub-agents to
@@ -111,5 +112,6 @@ code and *explain* it in *brief*, *standardized*, and *concise* way.
     - [...]
     </template>
     </step>
+
 </flow>
 

package/plugin/skills/ase-code-refactor/SKILL.md

@@ -14,6 +14,7 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 Refactor Artifacts
 ==================
@@ -22,13 +23,19 @@ Refactor Artifacts
 Refactor Artifacts
 </skill>
 
+<expand name="getopt"
+    arg1="ase-code-refactor"
+    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    $ARGUMENTS
+</expand>
+
 <role>
 Your role is an experienced, *expert-level software developer*.
 </role>
 
 <objective>
 *Refactor* existing artifacts the following way:
-<request>$ARGUMENTS</request>
+<request><getopt-arguments/></request>
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
@@ -42,6 +49,10 @@ You *MUST* not skip any numbered item during processing!
 You *MUST* *NOT* output anything in this entire procedure, *except* when
 explicitly requested by this procedure via outputs based on a <template/>!
 
+You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
+filesystem-modifying tool during this entire skill. The *only*
+permitted way to persist artifacts is via `task_save(...)`.
+
 1.  **Reason About Refactoring**:
 
     1.  <if condition="
@@ -160,20 +171,32 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 4.  **Choose Refactoring Approach**:
 
-    1.  Let the *user interactively choose* the preferred refactoring approach A<n/>
+    1.  If <getopt-option-auto/> is equal `true`:
+        Let the *user interactively choose* the preferred refactoring approach A<n/>
         with the help of the <user-dialog-tool/> tool. Use *single-selection* only
         and provide small *code change previews*. Mark your recommended
         refactoring approach with ` ⚝ **RECOMMENDATION** ⚝` here again.
         Except for the interactive selection, do not output anything in this step.
 
-5.  **Write Refactoring Plan**:
+    2.  If <getopt-option-auto/> is not equal `true`:
+        Set <n/> to the number of the refactoring approach A<n/> you recommend.
+        Output a hint with the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **auto-chosen approach A<n/>**
+        </template>
 
-    1.  *Write a refactoring plan* for the chosen refactoring A<n/> by
+5.  **Compose Refactoring Plan**:
+
+    1.  *Compose a refactoring plan* for the chosen refactoring A<n/> by
         closely aligning to the existing architecture and the existing
         code base. Use the <format/> defined for a task plan and inject
         the information from refactoring A<n/> and all derived realization
         decisions into it. Store the resulting task plan in <content/>.
 
+        You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
+        filesystem-modifying tool during this step.
+
     2.  Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
         `ase` MCP service and use the `text` field of its response for
         <timestamp-created/> and <timestamp-modified/> information. Then
@@ -190,16 +213,22 @@ explicitly requested by this procedure via outputs based on a <template/>!
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    5.  *Ask user*: Let the *user interactively choose*
-        what to do as the next step.
+    5.  *Determine next step*:
+
+        -   If <getopt-option-next/> matches the regex `^(DONE|EDIT|PREFLIGHT|IMPLEMENT)$`:
+            Honor the pre-selection what to do as the next step.
+            Set <result><getopt-option-next/></result>.
+
+        -   If <getopt-option-next/> is equal to `none`:
+            Let the *user interactively choose* what to do as the next step.
 
-        <expand name="user-dialog>
-        Next Step: How would you like to proceed with the plan?
-        DONE: Stop processing.
-        EDIT: Hand processing off to editing.
-        PREFLIGHT: Hand processing off to preflighting.
-        IMPLEMENT: Hand processing off to implementation.
-        </expand>
+            <expand name="user-dialog>
+                Next Step: How would you like to proceed with the plan?
+                DONE: Stop processing.
+                EDIT: Hand processing off to editing.
+                PREFLIGHT: Hand processing off to preflighting.
+                IMPLEMENT: Hand processing off to implementation.
+            </expand>
 
     6.  Check the tool <result/> and dispatch accordingly:
 

package/plugin/skills/ase-code-resolve/SKILL.md

@@ -14,6 +14,7 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 Resolve Problem
 ===============
@@ -22,13 +23,19 @@ Resolve Problem
 Resolve Problem
 </skill>
 
+<expand name="getopt"
+    arg1="ase-code-resolve"
+    arg2="--auto|-a --next|-n=(none|DONE|EDIT|PREFLIGHT|IMPLEMENT)">
+    $ARGUMENTS
+</expand>
+
 <role>
 Your role is an experienced, *expert-level software developer*.
 </role>
 
 <objective>
 *Resolve* the following problem:
-<problem>$ARGUMENTS</problem>
+<problem><getopt-arguments/></problem>
 </objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
@@ -42,6 +49,10 @@ You *MUST* not skip any numbered item during processing!
 You *MUST* *NOT* output anything in this entire procedure, *except* when
 explicitly requested by this procedure via outputs based on a <template/>!
 
+You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
+filesystem-modifying tool during this entire skill. The *only*
+permitted way to persist artifacts is via `task_save(...)`.
+
 1.  **Reason About Problem**:
 
     1.  If <problem/> matches the regexp `^[PT]\d+$` (i.e. a bare issue
@@ -212,19 +223,31 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 4.  **Choose Problem Resolution Approach**:
 
-    1.  Let the *user interactively choose* the preferred resolution approach A<n/>
+    1.  If <getopt-option-auto/> is equal `true`:
+        Let the *user interactively choose* the preferred resolution approach A<n/>
         with the help of the <user-dialog-tool/> tool. Use *single-selection* only
         and provide small *code change previews*. Mark your recommended
         resolution approach with ` ⚝ **RECOMMENDATION** ⚝` here again.
 
-5.  **Write Problem Resolution Plan**:
+    2.  If <getopt-option-auto/> is not equal `true`:
+        Set <n/> to the number of the resolution approach A<n/> you recommend.
+        Output a hint with the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **auto-chosen approach A<n/>**
+        </template>
 
-    1.  *Write a plan* with code references, a precise description of the
+5.  **Compose Problem Resolution Plan**:
+
+    1.  *Compose a plan* with code references, a precise description of the
         problem, the chosen resolution approach, a preview of the *unified
         diff* of the necessary code changes, and a possible way to verify
         the success of the resolution, by using the <format/> defined for a
         task plan. Store the resulting task plan in <content/>.
 
+        You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any
+        filesystem-modifying tool during this step.
+
     2.  Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
         `ase` MCP service and use the `text` field of its response for
         <timestamp-created/> and <timestamp-modified/> information. Then
@@ -248,16 +271,22 @@ explicitly requested by this procedure via outputs based on a <template/>!
         ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan created**
         </template>
 
-    6.  *Ask user*: Let the *user interactively choose*
-        what to do as the next step.
+    6.  *Determine next step*:
+
+        -   If <getopt-option-next/> matches the regex `^(DONE|EDIT|PREFLIGHT|IMPLEMENT)$`:
+            Honor the pre-selection what to do as the next step.
+            Set <result><getopt-option-next/></result>.
+
+        -   If <getopt-option-next/> is equal to `none`:
+            Let the *user interactively choose* what to do as the next step.
 
-        <expand name="user-dialog>
-        Next Step: How would you like to proceed with the plan?
-        DONE: Stop processing.
-        EDIT: Hand processing off to editing.
-        PREFLIGHT: Hand processing off to preflighting.
-        IMPLEMENT: Hand processing off to implementation.
-        </expand>
+            <expand name="user-dialog>
+                Next Step: How would you like to proceed with the plan?
+                DONE: Stop processing.
+                EDIT: Hand processing off to editing.
+                PREFLIGHT: Hand processing off to preflighting.
+                IMPLEMENT: Hand processing off to implementation.
+            </expand>
 
     7.  Check the tool <result/> and dispatch accordingly:
 

package/plugin/skills/ase-meta-changes/SKILL.md

@@ -45,6 +45,7 @@ The ChangeLog entries for a single product release version
 are also grouped and sorted according to the above <prefix/>es.
 
 <flow>
+
 1. <step id="STEP 1: Locate and read existing ChangeLog entries">
    The *ChangeLog* file `CHANGELOG.md` contains sections
    with headers in the style `N.M.K (YYYY-MM-DD)`.
@@ -91,5 +92,6 @@ are also grouped and sorted according to the above <prefix/>es.
    Also, update the date `YYYY-MM-DD` in the `N.M.K (YYYY-MM-DD)`
    headline of the *first* (most recent) section.
    </step>
+
 </flow>
 

package/plugin/skills/ase-meta-chat/SKILL.md

@@ -31,6 +31,7 @@ Query foreign LLM for: <query>$ARGUMENTS</query>
 </objective>
 
 <flow>
+
 1.  <step id="STEP 1: Select LLMs">
     Use the *first word* of the following <query/> for selecting the
     foreign LLMs to query, and their corresponding MCP servers, from the
@@ -54,5 +55,6 @@ Query foreign LLM for: <query>$ARGUMENTS</query>
     text from the agent response on your own and do not interpret the
     result in any way.
     </step>
+
 </flow>
 

package/plugin/skills/ase-task-edit/SKILL.md

@@ -15,6 +15,7 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-persona.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
 ============================
@@ -23,6 +24,12 @@ Iteratively Edit a Task Plan
 Iteratively Edit a Task Plan
 </skill>
 
+<expand name="getopt"
+    arg1="ase-task-edit"
+    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --next|-n=(none|DONE|IMPLEMENT|PREFLIGHT|REFINE)">
+    $ARGUMENTS
+</expand>
+
 Your role is an experienced, *expert-level assistant*,
 specialized in the *planning* of changes
 through *iterative conversational refinement*.
@@ -45,7 +52,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 1.  **Determine Task and Instruction:**
 
-    1.  Set <instruction>$ARGUMENTS</instruction> initially.
+    1.  Set <instruction><getopt-arguments/></instruction> initially.
         Inherit the always existing <ase-task-id/> from the current context.
         Do not output anything.
 
@@ -162,14 +169,21 @@ explicitly requested by this procedure via outputs based on a <template/>!
     3.  <if condition="<content/> is not empty AND
             <instruction/> is not empty AND
             <instruction/> is not equal <content/>">
-        Let the *user interactively choose* what to do as the next step.
+        *Determine previous-plan handling*:
+
+        -   If <getopt-option-plan/> matches the regex `^(OVERWRITE|REFINE|PRESERVE)$`:
+            Honor the pre-selection what to do with the previous plan.
+            Set <result><getopt-option-plan/></result>.
+
+        -   If <getopt-option-plan/> is equal to `none`:
+            Let the *user interactively choose* what to do as the next step.
 
-        <expand name="user-dialog>
-        Previous Plan: Should the previous plan content be overwritten, refined, or preserved?
-        OVERWRITE: Continue operation, overwrite previous plan.
-        REFINE: Continue operation, refine previous plan.
-        PRESERVE: Cancel operation, preserve previous plan.
-        </expand>
+            <expand name="user-dialog>
+                Previous Plan: Should the previous plan content be overwritten, refined, or preserved?
+                OVERWRITE: Continue operation, overwrite previous plan.
+                REFINE: Continue operation, refine previous plan.
+                PRESERVE: Cancel operation, preserve previous plan.
+            </expand>
 
         Check the tool <result/> and dispatch accordingly:
 
@@ -285,9 +299,11 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </if>
 
     3.  *Render plan*: Only output the following <template/>, so the user
-        can read the plan and react to it. Do *not* truncate, summarize,
-        or partially show the plan -- always show the complete plan
-        <content/> here:.
+        can read the plan and react to it. If <content/> is longer than
+        90 lines and a `※ IMPLEMENTATION DRAFT` section exists, replace
+        the entire content of the `※ IMPLEMENTATION DRAFT` section with
+        `[...]`. Else, do *not* truncate, summarize, or partially show
+        the plan. Use the following <template/>:
 
         <template>
         ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(** `TASK-PLAN-BEGIN` **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
@@ -295,16 +311,24 @@ explicitly requested by this procedure via outputs based on a <template/>!
         ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(**  `TASK-PLAN-END`  **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
         </template>
 
-    4.  *Ask user*: Let the *user interactively choose* what to do as the
-        next step.
+    4.  *Determine next step*:
+
+        -   If <getopt-option-next/> matches the regex `^(DONE|IMPLEMENT|PREFLIGHT|REFINE)$`:
+            Honor the pre-selection what to do as the next step.
+            Set <result><getopt-option-next/></result>.
+            Then *clear* <getopt-option-next/> by setting <getopt-option-next>none</getopt-option-next>
+            so that subsequent loop iterations fall back to the interactive dialog.
+
+        -   If <getopt-option-next/> is equal to `none`:
+            Let the *user interactively choose* what to do as the next step.
 
-        <expand name="user-dialog>
-        Next Step: How would you like to proceed with the plan?
-        DONE: Mark plan finalized, exit planning loop.
-        IMPLEMENT: Hand off plan to implementation.
-        PREFLIGHT: Hand off plan to pre-flighting.
-        REFINE: Further refine plan with instructions.
-        </expand>
+            <expand name="user-dialog>
+                Next Step: How would you like to proceed with the plan?
+                DONE: Mark plan finalized, exit planning loop.
+                IMPLEMENT: Hand off plan to implementation.
+                PREFLIGHT: Hand off plan to pre-flighting.
+                REFINE: Further refine plan with instructions.
+            </expand>
 
         Check the tool <result/> and dispatch accordingly:
 

package/plugin/skills/ase-task-implement/SKILL.md

@@ -13,6 +13,7 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 Implement a Task Plan
 =====================
@@ -21,6 +22,12 @@ Implement a Task Plan
 Implement a Task Plan
 </skill>
 
+<expand name="getopt"
+    arg1="ase-task-implement"
+    arg2="--next|-n=(none|DONE|DELETE)">
+    $ARGUMENTS
+</expand>
+
 Your role is an experienced, *expert-level assistant*,
 specialized in the *implementation* of changes.
 
@@ -38,7 +45,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 1.  **Determine Task:**
 
-    1.  Set <instruction>$ARGUMENTS</instruction> initially.
+    1.  Set <instruction><getopt-arguments/></instruction> initially.
         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.
@@ -117,14 +124,20 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 4.  **Decide Next Step:**
 
-    1.  *Ask user*: Let the *user interactively choose*
-        what to do as the next step.
+    1.  *Determine next step*:
+
+        -   If <getopt-option-next/> matches the regex `^(DONE|DELETE)$`:
+            Honor the pre-selection what to do as the next step.
+            Set <result><getopt-option-next/></result>.
+
+        -   If <getopt-option-next/> is equal to `none`:
+            Let the *user interactively choose* what to do as the next step.
 
-        <expand name="user-dialog>
-        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>
+            <expand name="user-dialog>
+                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:
 

package/plugin/skills/ase-task-list/SKILL.md

@@ -40,5 +40,6 @@ List Task Plans
     |-----------|--------------------|
     | **<id/>** | `<mtime/>`         |
     | [...]     | [...]              |
+
     </template>
 

package/plugin/skills/ase-task-preflight/SKILL.md

@@ -13,6 +13,7 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 Preflight a Task Plan
 =====================
@@ -21,6 +22,12 @@ Preflight a Task Plan
 Preflight a Task Plan
 </skill>
 
+<expand name="getopt"
+    arg1="ase-task-preflight"
+    arg2="--next|-n=(none|DONE|EDIT|IMPLEMENT)">
+    $ARGUMENTS
+</expand>
+
 Your role is an experienced, *expert-level assistant*,
 specialized in the *implementation* of changes.
 
@@ -38,7 +45,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 1.  **Determine Task:**
 
-    1.  Set <instruction>$ARGUMENTS</instruction> initially.
+    1.  Set <instruction><getopt-arguments/></instruction> initially.
         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.
@@ -104,15 +111,15 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     2.  Append this artifact change set <unified-diff/> to the end
         of the <content/> with the following <template/>. If a section
-        named `## ※ IMPLEMENTATION DRAFT:` already exists from a
+        named `## ※ IMPLEMENTATION DRAFT` already exists from a
         previous run of this skill, *replace* this entire existing
         section.
 
         <template>
 
-        ## ※ IMPLEMENTATION DRAFT:
+        ## ※ IMPLEMENTATION DRAFT
 
-        ```
+        ```text
         <unified-diff/>
         ```
 
@@ -139,15 +146,21 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 4.  **Decide Next Step:**
 
-    1.  *Ask user*: Let the *user interactively choose*
-        what to do as the next step.
+    1.  *Determine next step*:
+
+        -   If <getopt-option-next/> matches the regex `^(DONE|EDIT|IMPLEMENT)$`:
+            Honor the pre-selection what to do as the next step.
+            Set <result><getopt-option-next/></result>.
 
-        <expand name="user-dialog>
-        Next Step: How would you like to proceed with the plan?
-        DONE: Stop processing.
-        EDIT: Hand processing off to editing.
-        IMPLEMENT: Hand processing off to implementation.
-        </expand>
+        -   If <getopt-option-next/> is equal to `none`:
+            Let the *user interactively choose* what to do as the next step.
+
+            <expand name="user-dialog>
+                Next Step: How would you like to proceed with the plan?
+                DONE: Stop processing.
+                EDIT: Hand processing off to editing.
+                IMPLEMENT: Hand processing off to implementation.
+            </expand>
 
     2.  Check the tool <result/> and dispatch accordingly:
 
@@ -178,4 +191,3 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implement**
             </template>
 
-