@rse/ase 0.0.32 → 0.0.33

package/.claude-plugin/marketplace.json

@@ -0,0 +1,17 @@
+{
+    "name":                "ase",
+    "owner": {
+        "name":            "Dr. Ralf S. Engelschall",
+        "email":           "rse@engelschall.com"
+    },
+    "metadata": {
+        "description":     "Agentic Software Engineering (ASE)"
+    },
+    "plugins": [
+        {
+            "name":        "ase",
+            "source":      "./plugin/",
+            "description": "Agentic Software Engineering (ASE)"
+        }
+    ]
+}

package/dst/ase-getopt.js

@@ -0,0 +1,145 @@
+/*
+**  Agentic Software Engineering (ASE)
+**  Copyright (c) 2025-2026 Dr. Ralf S. Engelschall <rse@engelschall.com>
+**  Licensed under GPL 3.0 <https://spdx.org/licenses/GPL-3.0-only>
+*/
+import { z } from "zod";
+import { Command, Option } from "commander";
+import { parse as shParse, quote as shQuote } from "shell-quote";
+/*  MCP registration entry point for the option-parser tool  */
+export class GetoptMCP {
+    register(mcp) {
+        mcp.registerTool("getopt", {
+            title: "ASE option parser",
+            description: "Parse `args` against the options specification in " +
+                "`spec` of the form `--<long>[|-<short>][=<default>] ...` " +
+                "and return `{ opts, argv, args, info }` as JSON `text`, where " +
+                "`argv` is the array of remaining tokens after option parsing, " +
+                "`args` is the verbatim substring of the original input " +
+                "containing those remaining tokens (quotes preserved), and " +
+                "`info` is a markdown rendering of the parsed options in the " +
+                "form `key: **value**, key: **value**, ...` for printing at " +
+                "the top of a skill.",
+            inputSchema: {
+                name: z.string()
+                    .describe("Name of the caller (e.g. skill name), used in error messages"),
+                spec: z.string()
+                    .describe("Whitespace-separated option spec, e.g. `--foo/-f --bar --baz/-b=BAZ`"),
+                args: z.union([z.string(), z.array(z.string())])
+                    .describe("Arguments to parse (string is split on whitespace)")
+            }
+        }, async (args) => {
+            let helpText = "";
+            try {
+                /*  normalize args  */
+                const argsRaw = typeof args.args === "string" ? args.args : null;
+                const argsVec = typeof args.args === "string" ?
+                    shParse(args.args).filter((e) => typeof e === "string") :
+                    args.args;
+                /*  build a fresh commander program  */
+                const cmd = new Command(args.name)
+                    .exitOverride()
+                    .allowExcessArguments(true)
+                    .allowUnknownOption(false)
+                    .passThroughOptions(true)
+                    .configureOutput({
+                    writeOut: (str) => { helpText += str; },
+                    writeErr: () => { }
+                });
+                /*  tokenize spec and add one option per token  */
+                const tokens = args.spec.split(/\s+/).filter((e) => e.length > 0);
+                const re = /^--([A-Za-z][A-Za-z0-9-]*)(?:\|-([A-Za-z]))?(?:=(\((.*)\)|.*))?$/;
+                for (const tok of tokens) {
+                    const m = re.exec(tok);
+                    if (m === null)
+                        throw new Error(`invalid spec token "${tok}"`);
+                    const long = m[1];
+                    const short = m[2] ?? null;
+                    const valuePart = m[3] ?? null;
+                    const choicePart = m[4] ?? null;
+                    const takesValue = valuePart !== null;
+                    const choices = choicePart !== null ? choicePart.split("|") : null;
+                    const dflt = choices !== null ? choices[0] : valuePart;
+                    const head = short !== null ? `-${short}, --${long}` : `--${long}`;
+                    const flags = takesValue ? `${head} <value>` : head;
+                    const opt = new Option(flags);
+                    if (takesValue) {
+                        if (choices !== null)
+                            opt.choices(choices);
+                        opt.default(dflt);
+                    }
+                    else
+                        opt.default(false);
+                    cmd.addOption(opt);
+                }
+                /*  parse args  */
+                cmd.parse(argsVec, { from: "user" });
+                /*  compute verbatim trailing argument string  */
+                let argsVerbatim = "";
+                if (argsRaw !== null) {
+                    /*  tokenize raw input into [start,end) ranges, preserving quotes  */
+                    const ranges = [];
+                    let i = 0;
+                    while (i < argsRaw.length) {
+                        while (i < argsRaw.length && /\s/.test(argsRaw[i]))
+                            i++;
+                        if (i >= argsRaw.length)
+                            break;
+                        const start = i;
+                        while (i < argsRaw.length && !/\s/.test(argsRaw[i])) {
+                            const ch = argsRaw[i];
+                            if (ch === "\"" || ch === "'") {
+                                const quote = ch;
+                                i++;
+                                while (i < argsRaw.length && argsRaw[i] !== quote) {
+                                    if (argsRaw[i] === "\\" && i + 1 < argsRaw.length)
+                                        i++;
+                                    i++;
+                                }
+                                if (i < argsRaw.length)
+                                    i++;
+                            }
+                            else
+                                i++;
+                        }
+                        ranges.push({ start, end: i });
+                    }
+                    const tail = cmd.args.length;
+                    if (tail > 0 && ranges.length >= tail) {
+                        const first = ranges[ranges.length - tail].start;
+                        argsVerbatim = argsRaw.slice(first);
+                    }
+                }
+                else
+                    argsVerbatim = cmd.args.join(" ");
+                /*  build markdown info rendering of parsed options  */
+                const opts = cmd.opts();
+                const info = Object.entries(opts)
+                    .map(([k, v]) => `${k}: **${shQuote([String(v)])}**`)
+                    .join(", ");
+                /*  build result  */
+                const result = { opts, argv: cmd.args, args: argsVerbatim, info };
+                return {
+                    content: [{ type: "text", text: JSON.stringify(result) }]
+                };
+            }
+            catch (err) {
+                /*  intercept commander help/version output  */
+                const code = err?.code ?? "";
+                if (code === "commander.helpDisplayed"
+                    || code === "commander.help"
+                    || code === "commander.version") {
+                    return {
+                        isError: true,
+                        content: [{ type: "text", text: `ERROR: usage information requested\n\n${helpText.trimEnd()}` }]
+                    };
+                }
+                const message = err instanceof Error ? err.message : String(err);
+                return {
+                    isError: true,
+                    content: [{ type: "text", text: `ERROR: ${message}` }]
+                };
+            }
+        });
+    }
+}

package/dst/ase-service.js

@@ -21,6 +21,7 @@ import { TaskMCP } from "./ase-task.js";
 import { KVMCP } from "./ase-kv.js";
 import PersonaMCP from "./ase-persona.js";
 import { TimestampMCP } from "./ase-timestamp.js";
+import { GetoptMCP } from "./ase-getopt.js";
 import pkg from "../package.json" with { type: "json" };
 /*  shared service host  */
 export const SERVICE_HOST = "127.0.0.1";
@@ -236,6 +237,7 @@ export default class ServiceCommand {
             new KVMCP().register(mcp);
             new PersonaMCP(this.log).register(mcp);
             new TimestampMCP().register(mcp);
+            new GetoptMCP().register(mcp);
             return mcp;
         };
         /*  listen to HTTP/REST endpoints  */

package/dst/ase-setup.js

@@ -126,6 +126,28 @@ export default class SetupCommand {
         }
         return 0;
     }
+    /*  handler for "ase setup enable" (both tools)  */
+    async doEnable(tool) {
+        const spec = toolSpecs[tool];
+        await this.ensureTool(spec.cli);
+        this.log.write("info", `setup: enable: enabling ASE ${spec.label} plugin`);
+        const args = tool === "claude" ?
+            ["plugin", "enable", "ase@ase"] :
+            ["plugin", "install", "ase@ase"];
+        await this.run(spec.cli, args, { retries: tool === "claude" ? 1 : 3 });
+        return 0;
+    }
+    /*  handler for "ase setup disable" (both tools)  */
+    async doDisable(tool) {
+        const spec = toolSpecs[tool];
+        await this.ensureTool(spec.cli);
+        this.log.write("info", `setup: disable: disabling ASE ${spec.label} plugin`);
+        const args = tool === "claude" ?
+            ["plugin", "disable", "ase@ase"] :
+            ["plugin", "uninstall", "ase@ase"];
+        await this.run(spec.cli, args, { retries: tool === "claude" ? 1 : 3 });
+        return 0;
+    }
     /*  handler for "ase setup uninstall" (both tools)  */
     async doUninstall(tool, dev) {
         const spec = toolSpecs[tool];
@@ -197,5 +219,21 @@ export default class SetupCommand {
             .action(async (opts) => {
             process.exit(await this.doUninstall(this.parseTool(opts.tool), opts.dev));
         });
+        /*  register CLI sub-command "ase setup enable"  */
+        setupCmd
+            .command("enable")
+            .description("enable the ASE plugin for a tool")
+            .option("-t, --tool <tool>", "target tool (\"claude\" or \"copilot\")", toolDflt)
+            .action(async (opts) => {
+            process.exit(await this.doEnable(this.parseTool(opts.tool)));
+        });
+        /*  register CLI sub-command "ase setup disable"  */
+        setupCmd
+            .command("disable")
+            .description("disable the ASE plugin for a tool")
+            .option("-t, --tool <tool>", "target tool (\"claude\" or \"copilot\")", toolDflt)
+            .action(async (opts) => {
+            process.exit(await this.doDisable(this.parseTool(opts.tool)));
+        });
     }
 }

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.0.32",
+    "version":                              "0.0.33",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -68,6 +68,7 @@
         "dst/**/*",
         "bin/**/*",
         "plugin/**/*",
+        ".claude-plugin/**/*",
         "README.md"
     ],
     "scripts": {

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.31",
+    "version":     "0.0.33",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.github/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.31",
+    "version":     "0.0.33",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/meta/ase-getopt.md

@@ -0,0 +1,68 @@
+
+<define name="getopt">
+
+For parsing the command/skill options, perform the following seven steps
+and then continue processing the remaining skill.
+
+Do not output anything in the following steps. The entire purpose is to
+set placeholders into the context as a side-effect.
+
+1.  **Determine Parameters**:
+    Set <getopt-skill><arg1/></getopt-skill>.
+    Set <getopt-spec/><arg2/></getopt-spec>.
+    Set <getopt-opts/><arg3/>/getopt-opts>.
+    Set <getopt-args/><content/></getopt-args>.
+
+2.  **Short-Circuit for Quick Processing**:
+    If <getopt-opts/> contains `quick` *AND*
+    <getopt-args/> does *NOT* match the regexp `^\s*-':
+    Set <getopt-arguments><getopt-args/></getopt-arguments> and
+    then just silently *SKIP* the following steps 3-7!
+
+3.  **MCP Call**:
+    Call the `getopt(name: <getopt-skill/>, spec: <getopt-spec/>, args:
+    <getopt-args/>)` tool of the `ase` MCP service and set <text/> to the
+    `text` output field of this tool call. The `spec` syntax for each
+    option token is `--<long>[|-<short>][=<default>|=(<c1>|<c2>|...)]`,
+    where `=<default>` declares a value-taking option with a default,
+    and `=(<c1>|<c2>|...)` declares a value-taking option restricted to
+    the listed fixed choices (the first choice acts as the default).
+
+4.  **Short-Circuit for Error**:
+    If <text/> starts with `ERROR:`:
+    Remove all `ERROR:` or `error:` prefixes from <text/>.
+    Then only output the following <template/> and
+    then immediately *STOP* processing the entire current skill:
+
+    <template>
+    ⧉ **ASE**: ☻ skill: **<getopt-skill/>**, ▶ ERROR: option parsing failed: **<text/>**
+    </template>
+
+5.  **Parsing JSON Result**:
+    The tool returned a single `text` content payload containing JSON.
+    Parse this JSON in <text/> now into <getopt-result/> by recognizing
+    the following shape:
+
+    ```json
+    {
+        "opts": { "<long1/>": <value1/>, "<long2/>": <value2/>, ... },
+        "argv": [ "<arg1/>", "<arg2/>", ... ]
+        "args": "..."
+    }
+    ```
+
+6.  **Materializing into Context**:
+    For each *key* `<long/>` in <getopt-result/>`.opts`:
+    Set <getopt-option-<long/>/> to the corresponding value from
+    `<getopt-result/>.opts[<long/>]`.
+    Set <getopt-arguments/> to the value of `<getopt-result/>.args`.
+    Set <getopt-info/> to `<getopt-result/>`.info`.
+
+7.  **Display Results**:
+    Just output the following <template/>:
+
+    <template>
+    ⧉ **ASE**: ☻ skill: **<getopt-skill/>**, ▶ options: <getopt-info/>
+    </template>
+</define>
+

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-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-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-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.
@@ -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>.
+
+        -   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>
+            <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:
 

package/plugin/skills/ase-task-reboot/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
 
 Reboot a Task Plan
 ==================
@@ -21,6 +22,12 @@ Reboot a Task Plan
 Reboot a Task Plan
 </skill>
 
+<expand name="getopt"
+    arg1="ase-task-reboot"
+    arg2="--next|-n=(none|DONE|EDIT)">
+    $ARGUMENTS
+</expand>
+
 Your role is an experienced, *expert-level assistant*,
 specialized in the *planning* of changes.
 
@@ -40,7 +47,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.
@@ -132,14 +139,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|EDIT)$`:
+            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.
-        </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.
+            </expand>
 
     2.  Check the tool <result/> and dispatch accordingly: