@rse/ase 2.0.6 → 2.0.8

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

@@ -1,6 +1,6 @@
 ---
 name: ase-spec-edit
-argument-hint: "[--help|-h] [--approach|-a] [--grill|-g] [--grill-rounds|-r <n>] [--grill-until|-u MUST|SHOULD|MAY] [--grill-perspective|-p <perspective>] [--grill-ground|-G] [--verify|-v] [--worktree|-w <name>[:<branch>]] [--loop|-l] [<query>]"
+argument-hint: "[--help|-h] [--approach|-a] [--grill|-g] [--grill-rounds|-r <n>] [--grill-until|-u MUST|SHOULD|MAY] [--grill-perspective|-p <perspective>] [--grill-ground|-G] [--verify|-v light|none|full] [--worktree|-w <name>[:<branch>]] [--loop|-l] [<query>]"
 description: >
     Edit Specification: Use when the user wants to "edit" the
     SpecBook-based specification (SPEC) in one shot from a query, with
@@ -22,7 +22,7 @@ Edit Specification
 
 <expand name="getopt"
     arg1="ase-spec-edit"
-    arg2="--approach|-a --grill|-g --grill-rounds|-r=1 --grill-until|-u=(MUST|SHOULD|MAY) --grill-perspective|-p= --grill-ground|-G --verify|-v --worktree|-w= --loop|-l">
+    arg2="--approach|-a --grill|-g --grill-rounds|-r=1 --grill-until|-u=(MUST|SHOULD|MAY) --grill-perspective|-p= --grill-ground|-G --verify|-v=(light|none|full) --worktree|-w= --loop|-l">
     $ARGUMENTS
 </expand>
 
@@ -239,11 +239,18 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
                 arg3="file paths, artifact ids, object kinds, object ids, property keys, references, and literal values"
                 arg4="the specification"
                 arg5="">
-                <if condition="<getopt-option-verify/> is not equal `true`">
+                <if condition="<getopt-option-verify/> is equal `none`">
                 Raise *no* questions at all of focus area `REGRESSION`
-                or `CONFIRMATION`, as without `--verify` no verification
-                takes place which could honor their decisions.
-                </if></expand>
+                or `CONFIRMATION`, as under `--verify none` no
+                verification takes place which could honor their
+                decisions.
+                </if>
+                <elseif condition="<getopt-option-verify/> is equal `light`">
+                Raise *no* questions at all of focus area
+                `CONFIRMATION`, as under `--verify light` no
+                change-specific checks take place which could honor
+                their decisions.
+                </elseif></expand>
 
             If <grill-stop/> is `true`, skip the remaining items of
             this round and all remaining rounds, and continue with
@@ -383,10 +390,11 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
 
 7.  **State: verifying:**
 
-    Enter this state only if <getopt-option-verify/> is equal `true`.
-    Otherwise you *MUST* *strictly skip* the entire state and *any*
-    verification: do *NOT* validate the specification at all and do
-    *NOT* run any build, tests, linter, or type-checker.
+    Enter this state only if <getopt-option-verify/> is equal `light` or
+    `full` (both perform the same validation). Otherwise (`none`) you
+    *MUST* *strictly skip* the entire state and *any* verification: do
+    *NOT* validate the specification at all and do *NOT* run any build,
+    tests, linter, or type-checker.
 
     1.  Validate the specification and capture its <diagnostics/> array
         of `{ file, line, column, severity, message }` objects:
@@ -405,7 +413,7 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
 
     2.  If <diagnostics/> is not empty, fix the reported problems in the
         affected `SPEC` artifacts via the `Edit`/`Write` tools and
-        re-validate as in item 7.1 -- for at most *three* rounds in
+        re-validate as in item 7.1 -- for at most *ten* rounds in
         total.
 
     3.  <if condition="<diagnostics/> is not empty after the last round">
@@ -450,6 +458,6 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
     </ase-tpl-hint>
 
     <ase-tpl-hint level="verbose">
-    Use `/ase-spec-edit --grill` to stress-test the query first, `--verify` to validate the specification afterwards, and `--loop` to chain several edits.
+    Use `/ase-spec-edit --grill` to stress-test the query first, `--verify none` to skip the validation of the specification afterwards, and `--loop` to chain several edits.
     </ase-tpl-hint>
     </else>

package/plugin/skills/ase-spec-edit/help.md

@@ -13,7 +13,7 @@
     [`--grill-until`|`-u` `MUST`|`SHOULD`|`MAY`]
     [`--grill-perspective`|`-p` *perspective*]
     [`--grill-ground`|`-G`]
-    [`--verify`|`-v`]
+    [`--verify`|`-v` `light`|`none`|`full`]
     [`--worktree`|`-w` *name*[`:`*branch*]]
     [`--loop`|`-l`]
     [*query*]
@@ -37,8 +37,8 @@ project, and read the specification artifacts related to the query),
 *grilling* (optionally stress-test the query with rounds of questions),
 *implementing* (optionally select an approach, then apply the change set
 in place, honoring the GENERIC and SPECIFYING tenets and the `SPEC`
-format contract), and *verifying* (optionally validate the specification
-until it passes). The *querying* state, every *grilling* round, and the
+format contract), and *verifying* (validate the specification until it
+passes, unless disabled via `--verify none`). The *querying* state, every *grilling* round, and the
 approach selection close with an `EDIT TODO` box showing the established
 `WHAT` and `HOW` information.
 
@@ -74,8 +74,9 @@ timestamp refreshed.
     of a round are sorted by descending focus area importance
     (`DOMAIN`, `INTERFACE`, `ARCHITECTURE`, `IMPLEMENTATION`,
     `REGRESSION`, `CONFIRMATION`). Questions of focus area
-    `REGRESSION` and `CONFIRMATION` are raised only together with
-    `--verify`, as only then a verification honors their decisions.
+    `REGRESSION` are raised only under `--verify light` or `full`, and
+    those of focus area `CONFIRMATION` only under `--verify full`, as
+    only then a verification honors their decisions.
     All questions of a round are announced together below a `GRILLING ROUND K/L` line (the round numbering is
     omitted when only a single round is performed) as a
     `QUESTION`/`ANSWERS` table with one row per question, each row
@@ -134,12 +135,13 @@ timestamp refreshed.
     no usable facts are found, a warning is shown and the grilling falls
     back to model knowledge. Only effective together with `--grill`.
 
--   `--verify`|`-v`:
+-   `--verify`|`-v` `light`|`none`|`full`:
     Verify the edited specification by validating it via *SpecBook*
     linting and fixing the reported diagnostics in the affected `SPEC`
-    artifacts, for at most three rounds. Any diagnostics remaining after
-    the last round are listed as `REMAINING DIAGNOSTICS`. Without
-    `--verify`, strictly no validation is performed at all.
+    artifacts, for at most ten rounds. Any diagnostics remaining after
+    the last round are listed as `REMAINING DIAGNOSTICS`. The default
+    `light` and the level `full` perform the same validation. The level
+    `none` strictly performs no validation at all.
 
 -   `--worktree`|`-w` *name*[`:`*branch*]:
     Apply the change sets inside the dedicated Git worktree
@@ -151,8 +153,8 @@ timestamp refreshed.
     single worktree serves the whole skill run: it is prepared before
     the first discovery, so discovering, grilling, and implementing all
     operate on it, all `--loop` iterations land in it, and it is left
-    uncommitted for review. Under
-    `--verify`, the validation then runs as the `ase spec lint` command
+    uncommitted for review. Unless
+    `--verify none` is given, the validation then runs as the `ase spec lint` command
     inside the worktree. If *name* is a bare lower-case word naming no
     existing worktree and a *query* follows (like `-w fix the crash`, a
     former boolean `-w` usage), the skill asks whether *name* is the
@@ -181,16 +183,22 @@ timestamp refreshed.
 
 ##  EXAMPLES
 
-Edit in one shot, without any questions or validation:
+Edit in one shot, without any questions, but with validation:
 
 ```text
 ❯ /ase-spec-edit add a Reviewer persona to the persona model
 ```
 
-Grill the query with two rounds first, then edit and validate:
+Edit in one shot, without any questions or validation:
+
+```text
+❯ /ase-spec-edit -v none add a Reviewer persona to the persona model
+```
+
+Grill the query with two rounds first, then edit and fully validate:
 
 ```text
-❯ /ase-spec-edit -g -r 2 -v split the Event entity into Event and EventSeries
+❯ /ase-spec-edit -g -r 2 -v full split the Event entity into Event and EventSeries
 ```
 
 Let the user pick one of several specification approaches first, then

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-edit
-argument-hint: "[--help|-h] [--plan|-p <option>] [--mode|-m auto|craft|refactor|resolve|specify] [--approach|-a] [--unverified|-u] [--next|-n <option>[,...]] [<id> | <id>: <instruction> | <instruction> | <issue-id>]"
+argument-hint: "[--help|-h] [--plan|-p <option>] [--mode|-m auto|craft|refactor|resolve|specify] [--approach|-a] [--unverified|-u] [--focus|-f <section>[,...]] [--quiet|-q] [--interactive|-i] [--next|-n <option>[,...]] [<id> | <id>: <instruction> | <instruction> | <issue-id>]"
 description: >
     Iteratively edit and refine a named plan for a task through a
     conversational loop. A new plan is optionally composed along the
@@ -27,7 +27,7 @@ Iteratively Edit a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-edit"
-    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --mode|-m=(auto|craft|refactor|resolve|specify) --approach|-a --unverified|-u --next|-n=(none|DONE|GRILL|DRAFT|IMPLEMENT)... --int-reuse-task --int-source-dir=">
+    arg2="--plan|-p=(none|OVERWRITE|REFINE|PRESERVE) --mode|-m=(auto|craft|refactor|resolve|specify) --approach|-a --unverified|-u --focus|-f=(all|SPECIFICATION|SPEC|WHAT|DESIGN|DES|HOW|VERIFICATION|VERIFY|VER|WHEN)... --quiet|-q --interactive|-i --next|-n=(none|DONE|GRILL|DRAFT|IMPLEMENT)... --int-reuse-task --int-source-dir=">
     $ARGUMENTS
 </expand>
 
@@ -81,6 +81,19 @@ 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.
 
+<if condition="<getopt-option-focus/> is not equal `all`">
+Restrict the refinement to the sections in <sections/>: all other
+sections and the "backmatter" stay *unchanged* and serve as read-only
+context. Only if the <instruction/> inevitably requires a *foreign
+change* outside of these sections, apply it nevertheless, set <foreign/>
+to the comma-separated names of the changed sections (resp.
+`backmatter`), and only output the following <template/>:
+
+<template>
+⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ WARNING: changed sections outside of focus: **<foreign/>**
+</template>
+</if>
+
 <if condition="<getopt-option-int-source-dir/> is not empty">
 The *code basis* of the task is the separate working copy
 <getopt-option-int-source-dir/> (e.g. a checkout of the branch of its
@@ -212,6 +225,17 @@ then immediately *STOP* processing the entire current skill:
 Set <chosen-approach></chosen-approach> (empty). Do not output anything.
 </else>
 
+<if condition="<getopt-option-focus/> is not equal `all` and <task-content/> is not empty">
+This is the `OVERWRITE` of an existing plan under a focus, so re-generate
+*only* the sections in <sections/> of <task-content/> in-place, by
+closely following the defined plan format <format/> and injecting into
+them all the information from the <instruction/>, the <chosen-approach/>
+(if not empty), all decisions you derived from the <instruction/> and the
+<chosen-approach/>, and the grounding in the project. All other sections,
+the "backmatter", and all other frontmatter keys stay *unchanged*. Set the
+`Kind:` frontmatter key to <task-kind/>.
+</if>
+<else>
 Create a new plan from scratch and store the result as
 <task-content/> by closely following the defined plan format
 <format/> and injecting into it all the information from
@@ -220,6 +244,14 @@ decisions you derived from the <instruction/> and the <chosen-approach/>, and
 the grounding in the project. Set the `Kind:` frontmatter key to
 <task-kind/>.
 
+<if condition="<getopt-option-focus/> is not equal `all`">
+Populate *only* the sections in <sections/> and keep all other sections
+*empty*, i.e., as bare `##` headings without any bullet-points, until a
+later round focuses them. Hence, the `CHANGELOG.md` bullet-point of the
+grounding above is due only if `DESIGN` is in <sections/>.
+</if>
+</else>
+
 <if condition="<task-kind/> is equal `RESOLVING`">
 The plan *MUST* carry code references, a precise description of the
 problem, the resolution approach, a preview of the *unified
@@ -238,7 +270,8 @@ 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 <timestamp-created/> and <timestamp-modified/>
 information. Then insert the current <ase-task-id/>,
-<timestamp-created/>, and <timestamp-modified/> information.
+<timestamp-created/>, and <timestamp-modified/> information -- except
+for the `OVERWRITE` under a focus above, which keeps the `Created:` key.
 Set <task-content-dirty>true</task-content-dirty>.
 </define>
 
@@ -262,6 +295,23 @@ Set <args></args> (set args to empty).
         Inherit the always existing <ase-session-id/> from the current context.
         Do not output anything.
 
+        <expand name="task-focus" arg1="ase-task-edit"></expand>
+
+        Set <band-open>false</band-open>.
+        <if condition="<getopt-option-interactive/> is `true`">
+        The band of `--interactive` is drawn by the function hooks module
+        of the plugin, which provides the `mcp__ase__ase_task_band` tool
+        in an interactive terminal only. Load the schema of this tool (if
+        deferred, via `ToolSearch` with the query
+        `select:mcp__ase__ase_task_band`). If this tool does not exist,
+        only output the following <template/> and then immediately *STOP*
+        processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ☻ skill: **ase-task-edit**, ▶ ERROR: `--interactive` requires the active ASE function hooks in an interactive terminal
+        </template>
+        </if>
+
     2.  Resolve a potential analyzer issue:
 
         <if condition="
@@ -647,6 +697,7 @@ Set <args></args> (set args to empty).
         silently *skip* this entire step 3.3 (no MCP tool call and no
         output at all) and continue with step 3.4.
 
+        <if condition="<getopt-option-quiet/> is not equal `true` and <getopt-option-interactive/> is not equal `true`">
         <if condition="<task-render/> is empty">
         Call the `ase_markdown_prepare(text: "<task-content/>")` tool of
         the `ase` MCP server and set <task-render/> to the `text` output
@@ -684,22 +735,34 @@ Set <args></args> (set args to empty).
         ⇥   **Target:**    <task-target/>
         </format>
 
+        Set <focus-label></focus-label> (empty).
+        <if condition="<getopt-option-focus/> is not equal `all`">
+        For the *rendering only*, overriding the above, additionally drop
+        the glyph lines, the `#   TASK: <title/>` heading, every `##`
+        section whose name is *not* in <sections/>, and the entire
+        "backmatter", keeping the remaining sections, including their
+        `##` headings, in their plan order, and set <focus-label/> to
+        ` (<names/>)`, with <names/> being the comma-separated names of
+        these remaining sections.
+        </if>
+
         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. Use the
-        following <template/>:
+        summarize, or partially show the plan, beyond the focus
+        above. Use the following <template/>:
 
         <template>
-        <ase-tpl-head title="TASK" subtitle="<task-id/>"/>
+        <ase-tpl-head title="TASK" subtitle="<task-id/><focus-label/>"/>
         <task-render/>
-        <ase-tpl-foot title="TASK" subtitle="<task-id/>"/>
+        <ase-tpl-foot title="TASK" subtitle="<task-id/><focus-label/>"/>
         </template>
+        </if>
 
         <if condition="the backmatter of <task-content/> contains an attachment
             block with the `Type` key value `text/x-diff; charset=utf-8; kind="draft"`
             which is *stale* according to the plan <format/> (its `Modified` key
             is absent or older than the `Modified` key of the frontmatter)">
-        Directly *after* this <template/>, only output the following
+        Directly *after* any rendering, only output the following
         <template/> and then give the corrective hint by expanding the
         subsequent construct (which, depending on the configured
         <ase-guidance-level/>, may expand into nothing and hence emit
@@ -742,7 +805,40 @@ Set <args></args> (set args to empty).
                 ⧉ **ASE**: ☻ skill: **ase-task-edit**, ▶ ERROR: invalid `--next` token: **<head/>**
                 </template>
 
-        -   If <getopt-option-next/> is equal to `none`:
+        -   If <getopt-option-next/> is equal to `none` and <getopt-option-interactive/> is `true`:
+
+            <if condition="<band-open/> is `false`">
+            Call the `mcp__ase__ase_task_band(id: "<ase-task-id/>")` tool --
+            if <getopt-option-focus/> is not equal `all`, additionally with
+            the argument `sections: "<sections/>"` -- to show the plan in the
+            band above the prompt, which from now on follows every change of
+            the plan on its own, and set <band-open>true</band-open>. If its
+            `text` output field starts with `ERROR: <info/>`, only output the
+            following <template/> and then immediately *STOP* processing the
+            entire current skill:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ ERROR: **<info/>**
+            </template>
+            </if>
+
+            Do *not* show any dialog. Only output the following <template/>,
+            end the current turn, wait for the user input, and store the
+            user input in <result/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **awaiting instruction**
+            </template>
+
+            If <result/>, with any leading and trailing whitespace stripped,
+            case-insensitively equals `DONE`, `GRILL`, `DRAFT`, `IMPLEMENT`,
+            or `CANCEL` -- exactly the inputs on which the band closes on its
+            own -- set <result/> to this upper-case token. Otherwise, set
+            <result>OTHER: <result/></result>, also for an input which merely
+            indicates that the user does not want to proceed, as the band
+            stays open on it.
+
+        -   If <getopt-option-next/> is equal to `none` and <getopt-option-interactive/> is not `true`:
 
             In the following, you *MUST* *NOT* use your built-in
             <user-dialog-tool/> tool! Instead, you *MUST* just show a
@@ -772,6 +868,15 @@ Set <args></args> (set args to empty).
 
             *Break* out of the *loop*.
             <expand name="handoff-args"/>
+            <if condition="<getopt-option-quiet/> is `true`">
+                Set <args><args/> --quiet</args>.
+            </if>
+            <if condition="<getopt-option-interactive/> is `true`">
+                Set <args><args/> --int-interactive</args>.
+            </if>
+            <if condition="<getopt-option-focus/> is not equal `all`">
+                Set <args><args/> --focus <getopt-option-focus/></args>.
+            </if>
             Only output the following <template/> and then call the
             `Skill(skill: "ase:ase-task-grill", args: "<args/>")` tool
             to *grill* the finalized plan.

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

@@ -11,6 +11,9 @@
     [`--mode`|`-m` `auto`|`craft`|`refactor`|`resolve`|`specify`]
     [`--approach`|`-a`]
     [`--unverified`|`-u`]
+    [`--focus`|`-f` *section*[,...]]
+    [`--quiet`|`-q`]
+    [`--interactive`|`-i`]
     [`--next`|`-n` *option*[,...]]
     [*id* | *id*: *instruction* | *instruction* | *issue-id*]
 
@@ -95,6 +98,51 @@ stale draft.
     build, tests, linter, type-checker, or program execution) once
     the source files have been modified.
 
+-   `--focus`|`-f` *section*[,...]:
+    Edit and show only the given plan *section*(s). Each *section* is
+    one of `SPECIFICATION` (also `SPEC` or `WHAT`), `DESIGN` (also `DES`
+    or `HOW`), or `VERIFICATION` (also `VERIFY`, `VER`, or `WHEN`),
+    matched case-sensitively, or the sentinel `all` (default). The shown
+    plan consists only of these sections, including their headings, but
+    without the frontmatter and the title.
+
+    The rest of the plan stays the context, and an *instruction* requiring a
+    change outside of the focus is applied nevertheless and reported by
+    a warning. A new plan gets all section headings, but only the focused
+    sections are populated, and `OVERWRITE` re-generates only them. An
+    unknown, empty, or duplicate *section* token aborts the skill. It is
+    forwarded on a hand-off to `ase-task-grill`, but not on a hand-off
+    to another skill.
+
+-   `--quiet`|`-q`:
+    Do not print the resulting plan at the end of a planning round. The
+    status lines, the dialogs, and the warning on a stale implementation
+    draft stay. It is forwarded on a hand-off to `ase-task-grill`, but
+    not on a hand-off to another skill.
+
+-   `--interactive`|`-i`:
+    Show the plan in a band above the prompt (*Anthropic Claude Code CLI* with
+    active ASE function hooks in an interactive terminal only, else the skill
+    aborts), instead of printing it, and ask for the next step without any
+    dialog. The band takes 75% of the terminal height, in the fullscreen mode
+    all the rows the terminal UI leaves it. Under `--focus`, it shows only the
+    focused sections.
+
+    The band follows every change of the plan, also by others, and keeps its
+    scroll position. Its line numbers are those of the plan text in `ase task
+    edit`. It shows the last change as a unified diff with colored backgrounds and
+    line numbers, red for removed and blue for added lines. In the fullscreen
+    mode, scroll it with the mouse wheel, or with *CTRL+x* *TAB* and then
+    *PageUp*/*PageDown*.
+
+    At the prompt, type either a refinement instruction, or one of `DONE`,
+    `GRILL`, `DRAFT`, `IMPLEMENT`, or `CANCEL` (in any case), which closes the
+    band. After a hand-off to `ase-task-grill`, a hand-off back reopens it.
+
+    Type `##` at the end of the prompt (which removes it again) to remove the
+    unified diff and show just the latest state of the plan, until its next
+    change. The band stays open and the input does not reach the agent.
+
 -   `--next`|`-n` *option*[,...]:
     Automatically answer the user dialog for the next step (at the end
     of this skill). *option* is a single token or a *comma-separated
@@ -166,6 +214,18 @@ Plan a refactoring under the id `cleanup`:
 ❯ /ase-task-edit -m refactor cleanup: extract HTTP client into its own class
 ```
 
+Refine and show only the `DESIGN` section of the task under id `hello`:
+
+```text
+❯ /ase-task-edit --focus HOW hello: print the text via a dedicated logger.
+```
+
+Refine the task under id `hello` with its plan shown in a band above the prompt:
+
+```text
+❯ /ase-task-edit --interactive hello
+```
+
 ##  SEE ALSO
 
 [`ase-code-edit`](../ase-code-edit/help.md), [`ase-spec-edit`](../ase-spec-edit/help.md), [`ase-task-grill`](../ase-task-grill/help.md),

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-grill
-argument-hint: "[--help|-h] [--rounds|-r <n>] [--until|-u MUST|SHOULD|MAY] [--perspective|-p <perspective>] [--ground|-G] [--focus|-f <section>[,...]] [--force|-F] [--next|-n <option>[,...]] [<id>]"
+argument-hint: "[--help|-h] [--rounds|-r <n>] [--until|-u MUST|SHOULD|MAY] [--perspective|-p <perspective>] [--ground|-G] [--focus|-f <section>[,...]] [--force|-F] [--quiet|-q] [--next|-n <option>[,...]] [<id>]"
 description: >
     Interview the user relentlessly about the task plan until reaching a
     shared understanding, resolving each branch of the question decision
@@ -22,7 +22,7 @@ Iteratively Grill a Task Plan
 
 <expand name="getopt"
     arg1="ase-task-grill"
-    arg2="--rounds|-r=1 --until|-u=(MUST|SHOULD|MAY) --perspective|-p= --ground|-G --focus|-f=(all|SPECIFICATION|SPEC|DESIGN|DES|VERIFICATION|VER)... --force|-F --next|-n=(none|DONE|GRILL|EDIT|IMPLEMENT|DRAFT)... --int-reuse-task">
+    arg2="--rounds|-r=1 --until|-u=(MUST|SHOULD|MAY) --perspective|-p= --ground|-G --focus|-f=(all|SPECIFICATION|SPEC|WHAT|DESIGN|DES|HOW|VERIFICATION|VERIFY|VER|WHEN)... --force|-F --quiet|-q --next|-n=(none|DONE|GRILL|EDIT|IMPLEMENT|DRAFT)... --int-reuse-task --int-interactive">
     $ARGUMENTS
 </expand>
 
@@ -61,23 +61,9 @@ Set <args>--int-reuse-task</args>.
         ⧉ **ASE**: ☻ skill: **ase-task-grill**, ▶ ERROR: invalid `--rounds` value: **<getopt-option-rounds/>**
         </template>
 
-    3.  Treat <getopt-option-focus/> as a comma-separated list of
-        *section tokens*. Trim and upper-case every token, then expand
-        the abbreviations `SPEC`, `DES`, and `VER` to `SPECIFICATION`,
-        `DESIGN`, and `VERIFICATION`, and expand the sentinel `ALL`
-        (the default) to `SPECIFICATION,DESIGN,VERIFICATION`. Set
-        <sections/> to the resulting list, *keeping the given order*.
-        The getopt parser validates only the *first* token, so you
-        *MUST* validate each token yourself: if any token is *empty*,
-        *not* one of the recognized sections or abbreviations, or
-        results in a section already present in <sections/>, bind
-        <token/> to that offending token, then only output the
-        following <template/> and immediately *STOP* processing the
-        entire current skill:
+    3.  Resolve the plan sections under focus:
 
-        <template>
-        ⧉ **ASE**: ☻ skill: **ase-task-grill**, ▶ ERROR: invalid `--focus` token: **<token/>**
-        </template>
+        <expand name="task-focus" arg1="ase-task-grill"></expand>
 
         Each section in <sections/> selects its *focus areas* of the
         grilling: `SPECIFICATION` selects `DOMAIN` and `INTERFACE`,
@@ -277,7 +263,19 @@ Set <args>--int-reuse-task</args>.
                 can re-ask it.
 
             Set <changes/> to all bullet-points of <task-content/> which
-            were changed or added in this round. Do not output anything.
+            were changed or added in this round. Do not output anything,
+            except for the following warning:
+
+            <if condition="<getopt-option-focus/> is not equal `all` and <changes/> contains a bullet-point of a section *not* in <sections/>">
+            An answer required a *foreign change* outside of the focus,
+            which is applied nevertheless. Set <foreign/> to the
+            comma-separated names of these sections and only output the
+            following <template/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ WARNING: changed sections outside of focus: **<foreign/>**
+            </template>
+            </if>
 
         5.  SAVE PLAN:
 
@@ -298,6 +296,7 @@ Set <args>--int-reuse-task</args>.
 
         6.  SHOW PLAN CHANGES:
 
+            <if condition="<getopt-option-quiet/> is not equal `true`">
             Set <round-suffix/> to
             ` round <m/>/<getopt-option-rounds/>` if
             <getopt-option-rounds/> is greater than 1, or to empty
@@ -316,6 +315,7 @@ Set <args>--int-reuse-task</args>.
 
             <ase-tpl-foot title="PLAN CHANGES" subtitle="after grilling<round-suffix/>"/>
             </template>
+            </if>
 
 4.  **Decide Next Step:**
 
@@ -326,7 +326,7 @@ Set <args>--int-reuse-task</args>.
             arg2="DONE|GRILL|EDIT|IMPLEMENT|DRAFT">
             Next Step: How would you like to proceed with the plan?
             DONE: Stop processing.
-            GRILL: Re-grill the entire plan again.
+            GRILL: Re-grill the plan again.
             EDIT: Hand off plan to editing.
             DRAFT: Hand off plan to implementation drafting.
             IMPLEMENT: Hand off plan to implementation.
@@ -352,6 +352,12 @@ Set <args>--int-reuse-task</args>.
             <if condition="<getopt-option-ground/> is `true`">
                 Set <args><args/> --ground</args>.
             </if>
+            <if condition="<getopt-option-quiet/> is `true`">
+                Set <args><args/> --quiet</args>.
+            </if>
+            <if condition="<getopt-option-int-interactive/> is `true`">
+                Set <args><args/> --int-interactive</args>.
+            </if>
             Only output the following <template/> and then call the
             tool `Skill(skill: "ase:ase-task-grill", args: "<args/>")`
             to invoke the `ase:ase-task-grill` skill again in order to
@@ -365,6 +371,15 @@ Set <args>--int-reuse-task</args>.
 
         -   If <result/> is `EDIT`:
             <expand name="handoff-args"/>
+            <if condition="<getopt-option-quiet/> is `true`">
+                Set <args><args/> --quiet</args>.
+            </if>
+            <if condition="<getopt-option-int-interactive/> is `true`">
+                Set <args><args/> --interactive</args>.
+            </if>
+            <if condition="<getopt-option-focus/> is not equal `all`">
+                Set <args><args/> --focus <getopt-option-focus/></args>.
+            </if>
             Only output the following <template/> and then call the
             tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`
             to invoke the `ase:ase-task-edit` skill in order to *edit*

package/plugin/skills/ase-task-grill/help.md

@@ -13,6 +13,7 @@
     [`--ground`|`-G`]
     [`--focus`|`-f` *section*[,...]]
     [`--force`|`-F`]
+    [`--quiet`|`-q`]
     [`--next`|`-n` *option*[,...]]
     [*id*]
 
@@ -61,7 +62,7 @@ persisted, its `Tags:` frontmatter key records each grilled section as
 its own tag `grilled:`*section* (lower-case, kept alongside the tags of
 previously grilled sections, e.g. `grilled:specification,
 grilled:design`), and a `PLAN CHANGES` box shows the bullet-points
-changed by the round. Finally, the user is offered a complete
+changed by the round (unless `--quiet` is given). Finally, the user is offered a complete
 re-grilling (with the same grilling options), or a hand-off to editing,
 implementation, or draft.
 
@@ -123,19 +124,28 @@ in state `[-]` (cancelled) or `[>]` (deferred) are never questioned.
 
 -   `--focus`|`-f` *section*[,...]:
     Grill only the given plan *section*(s), in the given order. Each
-    *section* is one of `SPECIFICATION` (abbreviated `SPEC`), `DESIGN`
-    (abbreviated `DES`), or `VERIFICATION` (abbreviated `VER`), matched
-    case-insensitively, or the sentinel `all` (default), which expands
-    to `SPECIFICATION,DESIGN,VERIFICATION`. The questions are derived
-    from the themes of the focused sections only, while the entire plan
-    stays the context, and the answers may still update any section.
-    An unknown, empty, or duplicate *section* token aborts the skill.
+    *section* is one of `SPECIFICATION` (also `SPEC` or `WHAT`), `DESIGN`
+    (also `DES` or `HOW`), or `VERIFICATION` (also `VERIFY`, `VER`, or
+    `WHEN`), matched case-sensitively, or the sentinel `all` (default),
+    which expands to `SPECIFICATION,DESIGN,VERIFICATION`. The questions
+    are derived from the themes of the focused sections only, while the
+    entire plan stays the context, and an answer requiring a change
+    outside of the focus is applied nevertheless and reported by a
+    warning. An unknown, empty, or duplicate *section* token aborts the
+    skill. It is forwarded on a re-grilling and on a hand-off to
+    `ase-task-edit`, but not on a hand-off to another skill.
 
 -   `--force`|`-F`:
     Re-grill already grilled sections completely, i.e., ignore their
     `grilled:`*section* tags instead of skipping them resp. re-asking
     only their `[?]` bullet-points.
 
+-   `--quiet`|`-q`:
+    Do not print the `PLAN CHANGES` box of the bullet-points changed by
+    a round. The status lines and the dialogs stay. It is forwarded on a
+    re-grilling and on a hand-off to `ase-task-edit`, but not on a
+    hand-off to another skill.
+
 -   `--next`|`-n` *option*[,...]:
     Automatically answer the user dialog for the next step (at the end
     of this skill). *option* is a single token or a *comma-separated