@rse/ase 0.9.44 → 0.9.46

package/dst/ase-setup.js

@@ -453,6 +453,29 @@ export default class SetupCommand {
                 await this.mcpRemove(tool, spec.server, scope);
         };
     }
+    /*  build a chat-model MCP handler which bridges to a locally
+        installed AI agent harness CLI via the mcp-to-harness stdio
+        scaffold; the API key environment variable carries no key at all,
+        but instead the harness model identifier, with the special value
+        "default" selecting the default model of the harness  */
+    harnessMcpHandler(harness) {
+        return async (spec, tool, scope, action, _envKey, envVal) => {
+            if (action === "activate")
+                await this.mcpAdd(tool, spec.server, {}, {
+                    type: "stdio", command: [
+                        "npx", "-y", "mcp-to-harness",
+                        "--service", spec.name,
+                        "--mcp-tool", "query",
+                        "--harness", harness,
+                        ...(envVal !== "default" ? [
+                            "--harness-model", envVal
+                        ] : [])
+                    ]
+                }, scope);
+            else
+                await this.mcpRemove(tool, spec.server, scope);
+        };
+    }
     /*  registry of pre-defined MCP servers: maps each server id onto its
         dedicated handler which performs the activate/deactivate operation  */
     mcpServers = [
@@ -510,6 +533,33 @@ export default class SetupCommand {
             skills: ["ase-meta-chat", "ase-meta-quorum"],
             handler: this.chatMcpHandler({ url: "https://api.z.ai/api/paas/v4/", api: "completion", model: "glm-5.1" }, { model: "z-ai/glm-5.1" })
         },
+        {
+            id: "anthropic-claude",
+            name: "Anthropic Claude",
+            version: "latest",
+            env: ["ANTHROPIC_CLAUDE"],
+            server: "chat-anthropic-claude",
+            skills: ["ase-meta-chat", "ase-meta-quorum"],
+            handler: this.harnessMcpHandler("claude")
+        },
+        {
+            id: "openai-codex",
+            name: "OpenAI Codex",
+            version: "latest",
+            env: ["OPENAI_CODEX"],
+            server: "chat-openai-codex",
+            skills: ["ase-meta-chat", "ase-meta-quorum"],
+            handler: this.harnessMcpHandler("codex")
+        },
+        {
+            id: "github-copilot",
+            name: "GitHub Copilot",
+            version: "latest",
+            env: ["GITHUB_COPILOT"],
+            server: "chat-github-copilot",
+            skills: ["ase-meta-chat", "ase-meta-quorum"],
+            handler: this.harnessMcpHandler("copilot")
+        },
         {
             id: "brave",
             name: "Brave",

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "https://ase.tools",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "https://github.com/rse/ase/issues" },
-    "version":                              "0.9.44",
+    "version":                              "0.9.46",
     "license":                              "Apache-2.0",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -42,12 +42,12 @@
     },
     "dependencies": {
         "commander":                        "15.0.0",
-        "@dotenvx/dotenvx":                 "2.15.1",
+        "@dotenvx/dotenvx":                 "2.17.2",
         "yaml":                             "2.9.0",
         "valibot":                          "1.4.2",
         "execa":                            "10.0.0",
         "mkdirp":                           "3.0.1",
-        "@hapi/hapi":                       "21.4.9",
+        "@hapi/hapi":                       "21.4.10",
         "beautiful-mermaid":                "1.1.3",
         "cli-table3":                       "0.6.5",
         "chalk":                            "5.6.2",

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

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

package/plugin/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.9.44",
+    "version":     "0.9.46",
     "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.9.44",
+    "version":     "0.9.46",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/agents/ase-code-lint.md

@@ -303,6 +303,17 @@ Workflow
                 which should be changed. Set <new-text/> to the lines of the
                 new code in <file/> which will replace it.
 
+                Keep the hunk *minimal*: <old-text/> and <new-text/>
+                *MUST* *NOT* share any common leading or trailing
+                lines - *strip* such lines, as they are *unchanged*
+                context and not part of the change. When two changed
+                regions are separated by unchanged lines, emit *two
+                separate* change hunks instead of one large hunk which
+                re-states the unchanged lines. Render a *moved* block
+                as one pure-deletion hunk at its old location plus one
+                pure-insertion hunk at its new location - *never* by
+                deleting and re-adding the unchanged lines in between.
+
             3.  Set <context-before/> to exactly *up to two* lines of
                 *unchanged* code context which occurs in <file/>
                 directly *before* <old-text/>, i.e., the lines (<line/>

package/plugin/agents/ase-docs-proofread.md

@@ -42,6 +42,14 @@ Workflow
         should be changed. Set <new-text/> to the lines of the
         new text which will replace it.
 
+        Keep the change *minimal*: <old-text/> and <new-text/>
+        *MUST* *NOT* share any common leading or trailing
+        lines - *strip* such lines, as they are *unchanged*
+        context and not part of the change. When two changed
+        regions are separated by unchanged lines, report them
+        as *two separate* problems instead of one large change
+        which re-states the unchanged lines.
+
     4.  Set <description/> to an ultra-brief and concise
         Markdown-formatted description of the problem with
         a hint of what is wrong and why it is wrong. In

package/plugin/agents/ase-meta-chat.md

@@ -9,6 +9,9 @@ tools:
     - "mcp__chat-xai-grok__query"
     - "mcp__chat-zai-glm__query"
     - "mcp__chat-alibaba-qwen__query"
+    - "mcp__chat-anthropic-claude__query"
+    - "mcp__chat-openai-codex__query"
+    - "mcp__chat-github-copilot__query"
 ---
 
 @../meta/ase-control.md
@@ -20,19 +23,22 @@ tools:
 
 2.  Set <server></server> (set to empty).
 
-    <if condition="<llm/> is equal 'chatgpt'"> <server>chat-openai-chatgpt</server></if>
-    <if condition="<llm/> is equal 'gemini'">  <server>chat-google-gemini</server> </if>
-    <if condition="<llm/> is equal 'deepseek'"><server>chat-deepseek</server>      </if>
-    <if condition="<llm/> is equal 'grok'">    <server>chat-xai-grok</server>      </if>
-    <if condition="<llm/> is equal 'glm'">     <server>chat-zai-glm</server>       </if>
-    <if condition="<llm/> is equal 'qwen'">    <server>chat-alibaba-qwen</server>  </if>
+    <if condition="<llm/> is equal 'chatgpt'"> <server>chat-openai-chatgpt</server>  </if>
+    <if condition="<llm/> is equal 'gemini'">  <server>chat-google-gemini</server>   </if>
+    <if condition="<llm/> is equal 'deepseek'"><server>chat-deepseek</server>        </if>
+    <if condition="<llm/> is equal 'grok'">    <server>chat-xai-grok</server>        </if>
+    <if condition="<llm/> is equal 'glm'">     <server>chat-zai-glm</server>         </if>
+    <if condition="<llm/> is equal 'qwen'">    <server>chat-alibaba-qwen</server>    </if>
+    <if condition="<llm/> is equal 'claude'">  <server>chat-anthropic-claude</server></if>
+    <if condition="<llm/> is equal 'codex'">   <server>chat-openai-codex</server>    </if>
+    <if condition="<llm/> is equal 'copilot'"> <server>chat-github-copilot</server>  </if>
 
     <if condition="<server/> is empty">
         You *MUST* output the following <template/> and immediately *STOP* processing
         (do *NOT* continue with any further step and do *NOT* call any MCP tool):
 
         <template>
-        ERROR: unknown LLM `<llm/>` (has to be one of: chatgpt, gemini, deepseek, grok, glm, qwen)
+        ERROR: unknown LLM `<llm/>` (has to be one of: chatgpt, gemini, deepseek, grok, glm, qwen, claude, codex, copilot)
         </template>
     </if>
 

package/plugin/agents/ase-meta-search.md

@@ -1,7 +1,6 @@
 ---
 name: ase-meta-search
 description: "Query the Web"
-model: sonnet
 effort: low
 tools:
     - "mcp__search-perplexity__perplexity_search"

package/plugin/etc/stx.conf

@@ -11,7 +11,12 @@ lint
 
 #   [plugin] build project
 build : lint
-    true
+    (   for name in $(cd skills; ls -1 | grep -v ase-meta-intent | sort); do
+            echo "<skill name=\"$name\">"
+            cat skills/$name/help.md | sed -e '/^##  SEE ALSO/,$d'
+            echo "</skill>"
+        done
+    ) >skills/ase-meta-intent/data.md
 
 #   [plugin] remove all generated files
 clean

package/plugin/meta/ase-common-task.md

@@ -0,0 +1,145 @@
+
+Task Skill Common Steps
+=======================
+
+<define name="task-react-id">
+
+1.  <if condition="
+        <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+    ">
+    Set <ase-task-id><instruction/></ase-task-id> (set task
+    id to instruction) and <instruction></instruction> (set
+    instruction empty), call the `ase_task_id(id: "<ase-task-id/>",
+    session: "<ase-session-id/>")` tool from the `ase` MCP
+    server to switch the task, and then only output the
+    following <template/>:
+
+    <template>
+    ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
+    </template>
+    </if>
+
+2.  <elseif condition="
+        <instruction/> has the format `<id/>: <text/>` where
+        <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$` and
+        <text/> is *empty*
+    ">
+    Set <instruction></instruction> (set instruction to empty)
+    and <ase-task-id><id/></ase-task-id> (set task id to
+    id) and call the `ase_task_id(id: "<ase-task-id/>", session:
+    "<ase-session-id/>")` tool from the `ase` MCP server to
+    switch the task, and then only output the following
+    <template/>:
+
+    <template>
+    ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
+    </template>
+    </elseif>
+
+3.  <elseif condition="<instruction/> is NOT empty">
+    The argument is neither empty nor a valid task id. As this
+    skill only accepts an optional `[<id>]` argument and *never*
+    a free-text instruction, only output the following <template/>
+    and then immediately *STOP* processing the entire current skill:
+
+    <template>
+    ⧉ **ASE**: ☻ skill: **<arg1/>**, ▶ ERROR: expected single `[<id>]` argument
+    </template>
+    </elseif>
+
+</define>
+
+<define name="task-load-content">
+
+<if condition="
+    <getopt-option-int-reuse-task/> is equal `true`
+    *and* a `ase_task_save(id: '<ase-task-id/>', ...)` tool call
+    exists earlier in the current session
+">
+    Set <text/> to the `text` argument of the most recent
+    `ase_task_save(id: '<ase-task-id/>', ...)` tool call,
+    *without* calling `ase_task_load` again. Set <status>plan
+    reused</status>. Do not output anything.
+</if>
+<else>
+    Call the `ase_task_load(id: "<ase-task-id/>")` tool of the
+    `ase` MCP server to load the current task plan content and
+    set <text/> to the `text` output field of this `ase_task_load`
+    tool call. Do not output anything related to this MCP tool
+    call. Set <status>plan loaded</status>.
+</else>
+
+-   If <text/> starts with `ERROR:` or `WARNING:`:
+    Set <task-content></task-content> (set task content to empty).
+    Set <words/> to "0".
+
+-   If <text/> starts NOT with `ERROR:` and NOT with `WARNING:`:
+    Set <task-content><text/></task-content> (set task content to text).
+    Calculate the number of words <words/> of <task-content/>.
+
+Only output the following <template/>:
+
+<template>
+⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<status/>**
+</template>
+
+</define>
+
+<define name="task-save-content">
+
+Update <timestamp-modified/> with the current time in ISO-style
+format, which has to be determined by calling the
+`ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
+MCP server and use the `text` field of its response. If
+<timestamp-created/> is still unset (because the plan content
+had no `Created:` line), set
+<timestamp-created><timestamp-modified/></timestamp-created>
+(fall back to the modified timestamp). Re-insert the current
+<ase-task-id/>, the original <timestamp-created/>, and the
+refreshed <timestamp-modified/> into <task-content/> and calculate
+the number of words <words/> of <task-content/>.
+
+Call the `ase_task_save(id: "<ase-task-id/>", text:
+"<task-content/>")` tool of the `ase` MCP server to save the task
+plan content. Do not output anything related to this MCP call
+except the following <template/>:
+
+<template>
+⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **<arg1/>**
+</template>
+
+</define>
+
+<define name="task-next-select">
+
+-   If <getopt-option-next/> is not equal to `none`:
+    Treat <getopt-option-next/> as a comma-separated chronological
+    list of pre-selected next-step tokens. *Split* it on `,`,
+    take the *first* token as <head/>, and store the remaining
+    tokens (joined back with `,`, or `none` if empty) into
+    <getopt-option-next/> so downstream skills can consume the tail.
+
+    -   If <head/> matches the regex `^(<arg2/>)$`:
+        Honor the pre-selected token.
+        Set <result><head/></result>.
+
+    -   else:
+        Only output the following <template/> and then immediately
+        *STOP* processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ☻ skill: **<arg1/>**, ▶ ERROR: invalid `--next` token: **<head/>**
+        </template>
+
+-   If <getopt-option-next/> is equal to `none`:
+
+    In the following, you *MUST* *NOT* use your built-in
+    <user-dialog-tool/> tool! Instead, you *MUST* just show a
+    custom dialog according to the expanded `custom-dialog`
+    definition. You *MUST* closely follow this definition:
+
+    <expand name="custom-dialog" arg1="--no-other">
+        <content/>
+    </expand>
+
+</define>

package/plugin/meta/ase-constitution.md

@@ -34,6 +34,8 @@ Commandments
 ------------
 
 - Be *honest* and *transparent* in all your responses.
+- *Ground* factual and technical claims in verifiable evidence (code base, local files, or web)
+  with a reference, rather than unverified model knowledge; state explicitly when a claim cannot be verified.
 - Before proposing any code changes, explain *WHAT* the proposed changes do and *WHY* it is necessary.
 - Use *concise* and *type-safe code* only.
 - Use *precise* and *surgical code changes* only.
@@ -45,7 +47,8 @@ Commandments
 - Always use *parentheses around arrow function parameters*, even for a single parameter.
 - Make a line break before the keywords "else", "catch", and "finally".
 - Try to *vertically align similar operators* on consecutive, similar lines.
-- Place spaces after opening and before closing angle brackets and braces.
+- Place spaces after opening and before closing angle brackets
+  (except for array access and array types) and braces (except for regular expression ranges).
 - Use *double-quotes* (`"[...]"`) instead of single-quotes (`'[...]'`) for all strings.
 - Use K&R coding style with *opening braces* at the end of lines and *closing braces* at the beginning of lines.
 - When a language has a *more strongly-typed variant*, prefer that variant.

package/plugin/meta/ase-dialog.md

@@ -3,13 +3,13 @@ User Dialog
 ===========
 
 <user-dialog-tool>unknown</user-dialog-tool>
-<if condition="<ase-agent-tool/> is 'claude'">
+<if condition="<ase-agent-tool/> is `claude`">
     <user-dialog-tool>AskUserQuestion</user-dialog-tool>
 </if>
-<if condition="<ase-agent-tool/> is 'copilot'">
+<if condition="<ase-agent-tool/> is `copilot`">
     <user-dialog-tool>ask_user</user-dialog-tool>
 </if>
-<if condition="<ase-agent-tool/> is 'codex'">
+<if condition="<ase-agent-tool/> is `codex`">
     <user-dialog-tool>none</user-dialog-tool>
 </if>
 
@@ -50,7 +50,7 @@ following procedure:
         excluding the question label on line 1, and stopping at the first missing line --
         the same lines the entry loop below renders).
 
-        <for items="2 3 4 5 6 7 8 9">
+        <for items="2 3 4 5 6 7 8 9 10">
             Take from <spec/> the line number <item/>.
             If this line does not exist, <break/>.
             If this line exists, parse it according to the format `<label/>: <description/>`.
@@ -81,7 +81,7 @@ following procedure:
             Set <keys><keys/>/**CANCEL**</keys>.
         </else>
 
-        <if condition="<opts/> contains `--other`">
+        <if condition="<opts/> contains `--other` and does *not* contain `--no-other`">
             Set <hint>Please choose *one* option by typing <keys/>, or other free-text instruction.</hint>.
         </if>
         <else>
@@ -103,7 +103,7 @@ following procedure:
         </text>
 
         If <n/> is less than 2:
-        Set <result>ERROR: custom-dialog requires 2-8 answer lines, got <n/></result>
+        Set <result>ERROR: custom-dialog requires 2-9 answer lines, got <n/></result>
         and *SKIP* the following step 2.2 and continue with step 2.3 dispatch.
 
     2.  Output the following <template/>, end the current turn, wait for the
@@ -134,7 +134,7 @@ following procedure:
 
         4.  If <result/> is then *NEITHER* one of the "key"
             *NOR* "label" values from <spec/>:
-            <if condition="<opts/> contains `--other`">
+            <if condition="<opts/> contains `--other` and does *not* contain `--no-other`">
                 Set <result>OTHER: <result/></result>
                 (prefix result with `OTHER: `).
             </if>

package/plugin/meta/ase-format-arch.md

@@ -411,7 +411,7 @@ communicate.
         the chosen concurrency structure.
 
     -   In case the unit hosts no functional components, the
-        entire `- Hosts:` bullet point is omitted.
+        entire `-   Hosts:` bullet point is omitted.
 
     -   In case the rationale is not present, the
         entire `, **BECAUSE** [...]` clause is omitted.
@@ -551,7 +551,7 @@ elements to the runtime platform, hardware, and network topology.
         the node's placement and platform choice.
 
     -   In case the node hosts no functional components, the
-        entire `- Hosts:` bullet point is omitted.
+        entire `-   Hosts:` bullet point is omitted.
 
     -   In case the rationale is not present, the
         entire `, **BECAUSE** [...]` clause is omitted.
@@ -619,7 +619,7 @@ production, defining installation, monitoring, and management concerns.
         for the operational approach.
 
     -   In case the element reference is not present, the
-        entire `- Element:` bullet point is omitted.
+        entire `-   Element:` bullet point is omitted.
 
     -   In case the rationale is not present, the
         entire `, **BECAUSE** [...]` clause is omitted.
@@ -707,7 +707,7 @@ How the Non-Functional Requirements (NR) are addressed.
         ("why") for the chosen tactic over alternatives.
 
     -   In case the element reference is not present, the
-        entire `- Affects:` bullet point is omitted.
+        entire `-   Affects:` bullet point is omitted.
 
     -   In case the rationale is not present, the
         entire `, **BECAUSE** [...]` clause is omitted.

package/plugin/meta/ase-format-spec.md

@@ -285,9 +285,6 @@ over time.
     -   <spec-cj-step-name/> is a summary (5-10 words) of the *step* at its
         <spec-cj-step-touchpoint/>.
 
-    -   <spec-cj-step-actor/> is a `SPEC-PE-<spec-pe-persona-id/>` reference to the
-        corresponding **Aspect** of the Personas **Artifact**.
-
     -   <spec-cj-step-stage/> is one of:
 
         -   `Awareness`:     Customer is not aware of solution, but has a need.
@@ -297,6 +294,9 @@ over time.
         -   `Retention`:     Customer in the long-term stays a customer.
         -   `Advocacy`:      Customer is a fan of solution and tells the tribe.
 
+    -   <spec-cj-step-actor/> is a `SPEC-PE-<spec-pe-persona-id/>` reference to the
+        corresponding **Aspect** of the Personas **Artifact**.
+
     -   <spec-cj-step-goal/> is what the actor wants to achieve at this step.
 
     -   <spec-cj-step-touchpoint/> is where or how the interaction happens
@@ -311,7 +311,7 @@ over time.
         actor encounters at this step (optional).
 
     -   In case a <spec-cj-step/> has no pain point at all, the
-        entire `- Pain Point:` bullet point is omitted.
+        entire `-   Pain Point:` bullet point is omitted.
 
 Functional Requirements (FR)
 ----------------------------
@@ -518,7 +518,7 @@ constraining the Functional and Non-Functional Requirements.
         business rule.
 
     -   In case the rule constrains no specific requirement, the
-        entire `- Constrains:` bullet point is omitted.
+        entire `-   Constrains:` bullet point is omitted.
 
     -   In case the rationale is not present, the
         entire `, **BECAUSE** [...]` clause is omitted.
@@ -656,24 +656,24 @@ manages, defining how information is organized and connected.
 
     With:
 
-    -    <export-table-1/> is a Markdown table for the attributes with one
-         row per <spec-dm-attribute-id/>, sorted by <spec-dm-attribute-id/>
-         -- with the columns:
+    -   <export-table-1/> is a Markdown table for the attributes with one
+        row per <spec-dm-attribute-id/>, sorted by <spec-dm-attribute-id/>
+        -- with the columns:
 
-         -   `Attribute`     (`**<spec-dm-attribute-id/>**`)
-         -   `Type`          (`<spec-dm-attribute-qualifier/><spec-dm-attribute-type/>`)
-         -   `Description`   (`<spec-dm-attribute-description/>, **BECAUSE** <spec-dm-attribute-rationale/>.`)
+        -   `Attribute`     (`**<spec-dm-attribute-id/>**`)
+        -   `Type`          (`<spec-dm-attribute-qualifier/><spec-dm-attribute-type/>`)
+        -   `Description`   (`<spec-dm-attribute-description/>, **BECAUSE** <spec-dm-attribute-rationale/>.`)
 
-    -    <export-table-2/> is a Markdown table for the relation with one
-         row per <spec-dm-relation-id/>, sorted by <spec-dm-relation-id/> --
-         with the columns:
+    -   <export-table-2/> is a Markdown table for the relation with one
+        row per <spec-dm-relation-id/>, sorted by <spec-dm-relation-id/> --
+        with the columns:
 
-         -   `Relation`      (`**<spec-dm-relation-id/>**`)
-         -   `Target`        (`[<spec-dm-relation-target/>](#<spec-dm-relation-target-id/>) (<spec-dm-relation-cardinality/>)`)
-         -   `Description`   (`<spec-dm-relation-description/>, **BECAUSE** <spec-dm-relation-rationale/>.`)
+        -   `Relation`      (`**<spec-dm-relation-id/>**`)
+        -   `Target`        (`[<spec-dm-relation-target/>](#<spec-dm-relation-target-id/>) (<spec-dm-relation-cardinality/>)`)
+        -   `Description`   (`<spec-dm-relation-description/>, **BECAUSE** <spec-dm-relation-rationale/>.`)
 
-    -    In case a <spec-dm-entity/> has no relations at all, the
-         entire `### RELATIONS` block (including <export-table-2/>) is omitted.
+    -   In case a <spec-dm-entity/> has no relations at all, the
+        entire `### RELATIONS` block (including <export-table-2/>) is omitted.
 
 -   Export: `export.svg`
 
@@ -853,7 +853,7 @@ ambiguities to avoid, shared consistently across all Artifacts.
         <spec-gl-term-name/> where helpful.
 
     -   In case a term has no synonyms, the
-        entire `- Synonyms:` bullet point is omitted.
+        entire `-   Synonyms:` bullet point is omitted.
 
 Use Cases (UC)
 --------------
@@ -932,7 +932,7 @@ for main, alternative, and exceptional paths.
         **SCENARIO** blocks of this use case).
 
     -   In case the use case realizes no specific functional requirement,
-        the entire `- Requirements:` bullet point is omitted.
+        the entire `-   Requirements:` bullet point is omitted.
 
     -   In case a precondition or postcondition is not present, the
         respective bullet point is omitted.
@@ -1271,13 +1271,13 @@ turn.
 
     -   <spec-ds-storyboard-usecase/> is a
         `SPEC-UC-<spec-uc-usecase-id/>` reference to the corresponding
-        **Aspect** of the Use Case **Artifact** the storyboard
+        **Aspect** of the Use Cases **Artifact** the storyboard
         visualizes (optional).
 
     -   <spec-ds-storyboard-scenario/> is a
         `SPEC-UC-<spec-uc-usecase-id/>-<spec-uc-usecase-scenario-id/>`
         reference to the corresponding scenario **Aspect** of the Use
-        Case **Artifact** the storyboard visualizes (optional).
+        Cases **Artifact** the storyboard visualizes (optional).
 
     -   <spec-ds-frame-name/>: a short (2-5 word) label for the screen,
         turn, or state depicted by the storyboard frame. Frames are

package/plugin/meta/ase-format-task.md

@@ -59,7 +59,7 @@ You *MUST* honor the following hints on this *task* format:
 -   The <title/> is a short summary of the <summary-what/>, no longer than
     50 characters.
 
--   The sections `##  CHANGES` and `##  VERIFICATION` all are just a short
+-   The sections `##  CHANGES` and `##  VERIFICATION` are each just a short
     list of 1-5 bullet points. Each bullet point is formatted as
     `- **<aspect/>**: <specification/>` where <aspect/> indicates
     the aspect of the section and <specification/> is 1-3 sentences

package/plugin/meta/ase-persona.md

@@ -18,7 +18,7 @@ requested communication style at any time during a session.
 -   If <ase-persona-style/> is `caveman`:
     You *MUST* use the terse, rough, and stuttering communication style of a *caveman*.
 
--   If <ase-persona-style/> is `writer`, `engineer`, `journalist`, `telegrapher` or `caveman`:
+-   If <ase-persona-style/> is `writer`, `engineer`, `journalist`, `telegrapher`, or `caveman`:
     -   You *MUST* *always keep* technical terms exactly, independent of other persona rules below.
     -   You *MUST* *always keep* errors quoted exactly, independent of other persona rules below.
     -   You *MUST* *always keep* code blocks unchanged, independent of other persona rules below.
@@ -28,7 +28,7 @@ requested communication style at any time during a session.
     -   You *MUST* bundle related aspects into paragraphs.
     -   You *MUST* output blank lines between paragraphs.
 
--   If <ase-persona-style/> is `engineer`, `journalist`, `telegrapher` or `caveman`:
+-   If <ase-persona-style/> is `engineer`, `journalist`, `telegrapher`, or `caveman`:
     -   You *MUST* use `○` as the bullet point marker symbol in bullet point lists.
     -   You *MUST* *drop* filler words
         ("just", "really", "basically", "actually", "simply", etc).
@@ -62,7 +62,7 @@ requested communication style at any time during a session.
         -   <keywords/> is only one to four keywords summarizing the <details/>
         -   <details/> is one to four prose sentences explaining the aspect
 
--   If <ase-persona-style/> is `telegrapher` or `caveman`:
+-   If <ase-persona-style/> is `telegrapher`, or `caveman`:
     -   You *MUST* *use only* bullet point lists without blank lines between bullet points.
     -   You *MUST* *use only* one bullet point per explanation aspect.
     -   You *MUST* *use* shorter synonyms

package/plugin/meta/ase-skill.md

@@ -299,7 +299,7 @@ Template Patterns
 
     <template>
 
-    ╭────────────────────────────────────────────────────────────────────┈┈┈┈┈┈┈┈┈
+    ╭───────────────────────────────────────────────────────────────────┈┈┈┈┈┈┈┈┈┈
 
     </template>
 
@@ -330,7 +330,7 @@ Template Patterns
     <raw-title-len/> is the number of characters in <raw-title/>,
     and <bar/> is the `─` character repeated exactly max(0, 67 -
     <raw-title-len/>) times -- clamped to zero so an over-long title
-    never yields a negative count.
+    never yields a negative count):
 
     <template>