@rse/ase 0.9.8 → 0.9.10

package/dst/ase-statusline.js

@@ -245,12 +245,14 @@ export default class StatuslineCommand {
                 out += ansi;
                 col += raw.length;
             };
-            /*  active <color> span state: when non-null, renderer/literal output is buffered
-                instead of appended directly, and flushed via c[color](buf) on </color>  */
+            /*  active <color> span state: when non-null, each emitted chunk is colored
+                individually and passed straight through appendOutput, so column
+                accounting and line-wrapping continue to work per-chunk inside the span
+                instead of treating the whole colored run as one atomic chunk  */
             let span = null;
             const emit = (chunk) => {
-                if (span !== null)
-                    span.buf += chunk;
+                if (span !== null && span.color !== "default")
+                    appendOutput((c[span.color])(chunk));
                 else
                     appendOutput(chunk);
             };
@@ -446,13 +448,7 @@ export default class StatuslineCommand {
             };
             /*  walk each template line and render  */
             const closeSpan = () => {
-                if (span !== null) {
-                    const wrapped = span.color === "default" ?
-                        span.buf :
-                        (c[span.color])(span.buf);
-                    span = null;
-                    appendOutput(wrapped);
-                }
+                span = null;
             };
             for (const line of tmpl) {
                 let i = 0;
@@ -465,7 +461,7 @@ export default class StatuslineCommand {
                             if (m[1] === "/")
                                 closeSpan();
                             else if (span === null)
-                                span = { color: m[2], buf: "" };
+                                span = { color: m[2] };
                             i += m[0].length;
                             continue;
                         }

package/dst/ase-task.js

@@ -59,12 +59,22 @@ export class Task {
     static baseDir(log) {
         return path.join(Task.projectRoot(), Task.spec(log).basedir);
     }
+    /*  ensure a task id's "TASK-<id>.md" filename satisfies
+        the configured "files" miniglob  */
+    static enforceFiles(log, id) {
+        const { files } = Task.spec(log);
+        const filename = `TASK-${id}.md`;
+        if (!picomatch(files, { dot: true })(filename))
+            throw new Error(`task: id "${id}" yields filename "${filename}" ` +
+                `which does not match the configured "files" glob "${files}"`);
+    }
     /*  resolve the on-disk path for a given task id; as a side effect,
         eagerly migrate any legacy <basedir>/<id>/plan.md files to the
         current <basedir>/TASK-<id>.md layout on first access (guarded by
         a cheap check, so it is a no-op once the store is migrated)  */
     static path(log, id) {
         Task.validateId(id);
+        Task.enforceFiles(log, id);
         if (Task.needsMigration(log))
             Task.migrateAll(log);
         return path.join(Task.baseDir(log), `TASK-${id}.md`);
@@ -93,7 +103,7 @@ export class Task {
             return [];
         const migrated = [];
         for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
-            if (!entry.isDirectory() || !/^[A-Za-z0-9-]+$/.test(entry.name))
+            if (!entry.isDirectory() || !/^[A-Za-z0-9_-]+$/.test(entry.name))
                 continue;
             const id = entry.name;
             const oldFile = path.join(dir, id, "plan.md");
@@ -138,7 +148,7 @@ export class Task {
     }
     /*  rename a task by moving its <project>/<basedir>/TASK-<oldId>.md file
         to <project>/<basedir>/TASK-<newId>.md; the embedded
-        "# ✪ TASK <id>:" heading inside the plan content is rewritten to
+        "#   TASK <id>:" heading inside the plan content is rewritten to
         the new id; returns true on success, false if the source task does
         not exist; throws if the target id already exists  */
     static rename(log, oldId, newId) {

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.9.8",
+    "version":                              "0.9.10",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",
@@ -42,7 +42,7 @@
     },
     "dependencies": {
         "commander":                        "15.0.0",
-        "@dotenvx/dotenvx":                 "1.71.2",
+        "@dotenvx/dotenvx":                 "1.71.3",
         "yaml":                             "2.9.0",
         "valibot":                          "1.4.1",
         "execa":                            "9.6.1",

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

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

package/plugin/meta/ase-dialog.md

@@ -1,5 +1,4 @@
 
-
 User Dialog
 ===========
 
@@ -12,16 +11,20 @@ User Dialog
 </if>
 
 <define name="user-dialog">
+
 Let the *user interactively choose* an answer.
 
 1.  Take the following question specification:
+
     <spec>
         <content/>
     </spec>
 
-    Each line of <spec/> (separated by newlines) is of the format:
+    The first line of <spec/> (separated by newlines) is of the format:
+    `<question-label/>: <question-description/>`
 
-    `<label/>: <description/>`.
+    The second and following lines of <spec/> (separated by newlines) are of the format:
+    `<label/>: <description/>`
 
     The first line provides the question label and the question
     description. The second and following lines each provide an
@@ -49,8 +52,8 @@ Let the *user interactively choose* an answer.
 
             If <n/> is less than 2:
             Set <result>ERROR: user-dialog requires 2-4 answer lines, got <n/></result>
-            and *SKIP* the following step 2 (do not call `AskUserQuestion`)
-            and continue with step 3 dispatch.
+            and *SKIP* the following step 2.2 (do not call `AskUserQuestion`)
+            and continue with step 2.3 dispatch.
 
         2.  Call the `AskUserQuestion` tool of the agent harness with:
 
@@ -103,8 +106,8 @@ Let the *user interactively choose* an answer.
 
             If <n/> is less than 2:
             Set <result>ERROR: user-dialog requires 2-4 answer lines, got <n/></result>
-            and *SKIP* the following step 2 (do not call `ask_user`)
-            and continue with step 3 dispatch.
+            and *SKIP* the following step 2.2 (do not call `ask_user`)
+            and continue with step 2.3 dispatch.
 
         2.  Call the `ask_user` tool of the agent harness with:
 
@@ -137,3 +140,126 @@ Let the *user interactively choose* an answer.
 
 </define>
 
+<define name="custom-dialog">
+
+In the following, you *MUST* *NOT* use the <user-dialog-tool/> tool!
+Instead, you *MUST* just show a custom output, let the user enter input,
+and then you set the result accordingly. For this, closely follow the
+following procedure:
+
+1.  Take the following question specification:
+    <spec><content/></spec>
+
+    Take the following options:
+    <opts><arg1/></opts>
+
+    The first line of <spec/> (separated by newlines) is of the format:
+    `<question-label/>: <question-description/>`
+
+    The second and following lines of <spec/> (separated by newlines) are of the format:
+    `<label/>: <description/>`
+
+    The first line provides the question label and the question
+    description. The second and following lines each provide an
+    answer label and an answer description.
+
+    Do not output anything in this step!
+
+2.  Dispatch according to the agent tool:
+
+    1.  You *MUST* not output anything in this step.
+
+        Set <text></text> (set to empty).
+        Set <keys></keys> (set to empty).
+        Set <n>0</n> (set entry count to zero).
+        Set <width/> to the maximum length plus 3 of the <label/> strings in the
+        contiguous answer lines of <spec/> starting at line 2 (the answer labels only,
+        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">
+            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/>`.
+            Set <n/> to <n/> + 1 (increment entry count).
+            Set <label-key/> to <ase-tpl-key digit="<n/>"/>.
+            Set <label-text/> to `<ase-tpl-pad width="<width/>" text="<label/>:"/>`.
+            Append an entry to <text/>:
+
+            <text>
+            <text/>
+            <ase-tpl-boxline><label-key/>  ▶  **<label-text/>** <description/></ase-tpl-boxline>
+            </text>
+
+            <if condition="<keys/> is empty">
+                Set <keys><label-key/></keys>
+            </if>
+            <else>
+                Set <keys><keys/>/<label-key/></keys>
+            </else>
+        </for>
+
+        <if condition="<opts/> contains `--other`">
+            Set <hint>Please choose *one* option by typing <keys/>/**CANCEL**, or other free-text instruction.</hint>.
+        </if>
+        <else>
+            Set <hint>Please choose *one* option by typing <keys/>/**CANCEL**.</hint>.
+        </else>
+
+        Set:
+
+        <text>
+        <ase-tpl-boxed title="DIALOG" subtitle="<question-label/>">
+
+        <ase-tpl-boxline>**<question-description/>**</ase-tpl-boxline>
+
+        <text/>
+
+        <hint/>
+
+        </ase-tpl-boxed>
+        </text>
+
+        If <n/> is less than 2:
+        Set <result>ERROR: custom-dialog requires 2-8 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
+        user input, store the user input in <result/> and then continue with
+        step 2.3 below:
+
+        <template>
+        <text/>
+        </template>
+
+    3.  Do not output anything in this step!
+        Check the <result/> and dispatch accordingly:
+
+        1.  If <result/> is `cancel`, `CANCEL`, `reject`, `REJECT`, or
+            otherwise indicates that the user doesn't want to proceed,
+            or the user declined to answer the question, or that
+            the dialog was cancelled, rejected or skipped, set
+            <result>CANCEL</result>.
+
+        2.  Otherwise, determine the selected <label/>
+            by mapping the <result/> (usually containing one of the
+            "key" or "label" strings) to one of the answer labels in
+            <spec/>. Set <result><label/></result>.
+
+        3.  If <result/> is then *NEITHER* one of the "key"
+            *NOR* "label" values from <spec/>:
+            <if condition="<opts/> contains `--other`">
+                Set <result>OTHER: <result/></result>
+                (prefix result with "OTHER").
+            </if>
+            <else>
+                Output the following <template/> and then *START OVER*
+                by *GOING* to step 2.2 above.
+
+                <template>
+                ⧉ **ASE**: ERROR: **Invalid option selected!**
+                </template>
+            </else>
+
+</define>
+

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

@@ -77,14 +77,14 @@ distinct **Artifact**s (listed under their <artifact-name/> and their
 The **Artifact**s have the following cross-references:
 
 ```text
-ARCH-02-FV Functionality View   ──(depends on)─► ARCH-02-FV Functionality View
-ARCH-03-IV Information View     ──(entity)─►     SPEC-05-DM Data Model
+ARCH-02-FV Functionality View   ──(depends on)─► ARCH-01-CV Context View
+ARCH-03-IV Information View     ──(entity)─►     SPEC-07-DM Data Model
 ARCH-03-IV Information View     ──(owner)─►      ARCH-02-FV Functionality View
 ARCH-04-CO Concurrency View     ──(hosts)─►      ARCH-02-FV Functionality View
 ARCH-06-DP Deployment View      ──(hosts)─►      ARCH-02-FV Functionality View
 ARCH-07-OV Operations View      ──(element)─►    ARCH-02-FV Functionality View
 ARCH-07-OV Operations View      ──(element)─►    ARCH-06-DP Deployment View
-ARCH-08-QP Quality Perspectives ──(addresses)─►  SPEC-04-NR Non-Functional Requirements
+ARCH-08-QP Quality Perspectives ──(addresses)─►  SPEC-05-NR Non-Functional Requirements
 ARCH-08-QP Quality Perspectives ──(affects)─►    ARCH-02-FV Functionality View
 ARCH-08-QP Quality Perspectives ──(affects)─►    ARCH-06-DP Deployment View
 ARCH-09-DR Decision Record      ──(affects)─►    ARCH-02-FV Functionality View

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

@@ -563,7 +563,7 @@ manages, defining how information is organized and connected.
 
     ### RELATIONS
 
-    -   `<spec-dm-relation-id/>`: [`<spec-dm-relation-target/>`](#<spec-dm-relation-id/>)(`<spec-dm-relation-cardinality/>`):<br/>
+    -   `<spec-dm-relation-id/>`: [`<spec-dm-relation-target/>`](#<spec-dm-relation-target-id/>)(`<spec-dm-relation-cardinality/>`):<br/>
         <spec-dm-relation-description/>,
         **BECAUSE** <spec-dm-relation-rationale/>.
 
@@ -615,7 +615,7 @@ manages, defining how information is organized and connected.
     -   <spec-dm-relation-target/>: the <spec-dm-entity-name/> of the
         entity the directed relation targets.
 
-    -   <spec-dm-relation-id/>: the <spec-dm-entity-id/> of the
+    -   <spec-dm-relation-target-id/>: the <spec-dm-entity-id/> of the
         entity the directed relation targets.
 
     -   <spec-dm-relation-cardinality/>: the cardinality of the entity
@@ -724,8 +724,17 @@ making the forbidden moves as explicit as the allowed ones.
         is implicitly forbidden.
 
     -   Every <spec-sm-state-name/> used in a transition *MUST* be
-        declared in the `### STATES` block, and every non-final state
-        *MUST* have at least one outgoing transition.
+        declared in the `### STATES` block, and every state with no
+        outgoing transition *MUST* be listed in <spec-sm-lifecycle-final/>
+        (a state with no outgoing transition that is not final would be a
+        stuck dead-end). The converse does *not* hold: a
+        <spec-sm-lifecycle-final/> state *MAY* still have outgoing
+        transitions, modeling a resting state that can later be left again
+        (e.g. a `Closed` state with a `reopen` transition back to
+        `Active`). Thus <spec-sm-lifecycle-final/> designates the states in
+        which the entity may legally come to rest, which is a superset of,
+        but not necessarily equal to, the set of declared states that have
+        no outgoing transition.
 
     -   In case a transition has no side effect, the
         entire `<spec-sm-transition-effect/>,` clause is omitted.

package/plugin/meta/ase-getopt.md

@@ -8,31 +8,41 @@ 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>--help|-h <arg2/></getopt-spec>.
-    Set <getopt-args><content/></getopt-args>.
+    Set <getopt-skill><arg1/></getopt-skill>
+    Set <getopt-spec>--help|-h <arg2/></getopt-spec>
+    Set <getopt-args><content/></getopt-args>
 
 2.  **Short-Circuit Processing**:
-    If <getopt-args/> does *NOT* match the regexp `(^|\s)-` (i.e.
-    contains no options at all):
-
-    For each option token in <getopt-spec/> of the form
-    `--<long/>[|-<short/>][=<default/>|=(<c1/>|<c2/>|...)[...]]`, set
-    <getopt-option-<long/>/> to <default/> (for `=<default/>`
-    form), or to <c1/> (the first choice, for `=(<c1/>|<c2>/|...)`
-    form, or for the list form `=(<c1/>|<c2>/|...)...`),
-    or to `false` (for value-less options). Then set
-    <getopt-arguments><getopt-args/></getopt-arguments>.
-
-    Additionally, simulate <getopt-info/> as a comma-separated
-    markdown rendering of the parsed options in the form `<longN/>:
-    **<valueN/>**, [...]` (joined with `, `, with each value
-    shell-quoted if value contains spaces or special characters, and
-    excluding the `help` option and any *internal* option whose long
-    name starts with `int-`).
-
-    Then silently *SKIP* only the following steps 3-6
-    and proceed directly to step 7 to display the results.
+    You *MUST* decide here, via the following *mandatory* <if/> control
+    construct, whether the options are parsed *locally* (no MCP call) or
+    *remotely* (via the MCP call in steps 3-6). This is a *hard branch*,
+    not an optional optimization: when the <if/> branch is taken, steps
+    3-6 are *structurally unreachable* and you *MUST NOT* call the
+    `ase_getopt` MCP tool under any circumstances.
+
+    <if condition="<getopt-args/> does *NOT* match the regexp `(^|\s)-` (i.e. it does not start with an option)">
+        Parse the options *locally*, without any MCP call:
+
+        For each option token in <getopt-spec/> of the form
+        `--<long/>[|-<short/>][=<default/>|=(<c1/>|<c2/>|...)[...]]`, set
+        <getopt-option-<long/>/> to <default/> (for `=<default/>`
+        form), or to the *single token* <c1/> (the first choice, both
+        for the choice form `=(<c1/>|<c2>/|...)` and for the list form
+        `=(<c1/>|<c2>/|...)...` -- an *unsupplied* list-option always
+        defaults to the single token <c1/>, *not* to a whole list),
+        or to `false` (for value-less options). Then set
+        <getopt-arguments><getopt-args/></getopt-arguments>.
+
+        Additionally, simulate <getopt-info/> as a comma-separated
+        markdown rendering of the parsed options in the form `<longN/>:
+        **<valueN/>**, [...]` (joined with `, `, with each value
+        shell-quoted if value contains spaces or special characters, and
+        excluding the `help` option and any *internal* option whose long
+        name starts with `int-`).
+
+        You then *MUST* silently *SKIP* the steps 3-6 below
+        and proceed directly to step 7 to display the results.
+    </if>
 
 3.  **MCP Call**:
     Call the `ase_getopt(name: "<getopt-skill/>", spec:
@@ -44,11 +54,13 @@ set placeholders into the context as a side-effect.
     `=(<c1>|<c2>|...)` declares a value-taking option restricted to the
     listed fixed choices (the first choice acts as the default), and the
     trailing `...` (as in `=(<c1>|<c2>|...)...`) declares a value-taking
-    option whose value is a *comma-separated list* of choice tokens
-    (the first choice still acts as the default; only the *first*
-    token of the list is validated by the parser against the choice
-    set -- subsequent tokens are *not* validated, and skills validate
-    each remaining token themselves as they consume it).
+    option whose *supplied* value is a *comma-separated list* of choice
+    tokens (when *unsupplied*, the option defaults to the *single
+    token* `<c1>`, identical to the non-list choice form -- the list
+    semantics apply only to an explicitly supplied value; only the
+    *first* token of a supplied list is validated by the parser against
+    the choice set -- subsequent tokens are *not* validated, and skills
+    validate each remaining token themselves as they consume it).
 
 4.  **Short-Circuit for Error**:
     If <text/> starts with `ERROR:`:

package/plugin/meta/ase-skill.md

@@ -215,6 +215,11 @@ Skill Identification
     @${CLAUDE_SKILL_DIR}/help.md
     </template>
 
+-   *IMPORTANT*:
+    You *MUST* *NOT* output any summaries, explanations, or next
+    steps at the end of a skill beside the explicit outputs via any
+    <template/>.
+
 Template Patterns
 -----------------
 
@@ -227,12 +232,13 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-head title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 16 - length("<title/>")), i.e., <bar/> is
-    the "─" character repeated (70 - 16 - length("<title/>")) times):
+    (where <title-len/> is the number of characters in the string
+    `⧉ ASE: <title/>`, and <bar/> is the `─` character repeated exactly
+    (67 - <title-len/>) times):
 
     <template>
 
-    ╭────━━━━**(** `<title/>` **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    ╭────━━━━**(** ⧉ ASE: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
 
     </template>
 
@@ -245,15 +251,66 @@ Template Patterns
     </template>
 
 -   When `<ase-tpl-foot title="<title/>"/>` should be expanded, use
-    (where <bar/> = "─" x (70 - 16 - length("<title/>")), i.e., <bar/> is
-    the "─" character repeated (71 - 16 - length("<title/>")) times):
+    (where <title-len/> is the number of characters in the string
+    `⧉ ASE: <title/>`, and <bar/> is the `─` character repeated exactly
+    (67 - <title-len/>) times):
 
     <template>
 
-    ╰────━━━━**(** `<title/>` **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    ╰────━━━━**(** ⧉ ASE: **`<title/>`** **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
 
     </template>
 
+-   When `<ase-tpl-boxline><line/></ase-tpl-boxline>` should be expanded, use:
+
+    <if condition="<line/> is not empty">
+        <template>
+        │ <line/>
+        </template>
+    </if>
+    <else>
+        <template>
+        │
+        </template>
+    </else>
+
+-   When `<ase-tpl-boxed title="<title/>"[ subtitle="<subtitle/>"]><content/></ase-tpl-boxed>`
+    should be expanded use the following helper placeholder and then the <template/>:
+
+    -   <if condition="<subtitle/> is not empty">
+            Set <raw-title>⧉ ASE: <title/>: <subtitle/><raw-title>.
+            Set <render-title>⧉ ASE: **`<title/>`**: `<subtitle/>`</render-title>.
+        </if>
+        <else>
+            Set <raw-title>⧉ ASE: <title/><raw-title>.
+            Set <render-title>⧉ ASE: **`<title/>`**</render-title>.
+        </else>
+    -   Set <raw-title-len/> to the number of characters in <raw-title/>.
+    -   Set <bar/> to the `─` character repeated exactly (67 - <raw-title-len/>) times.
+    -   Set <body> to <content/> with all line-starts prefixed with `│ `.
+
+    <template>
+
+    ╭────━━━━**(** <render-title/> **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+    │
+    <body/>
+    │
+    ╰────━━━━**(** <render-title/> **)**━━━━────<bar/>┈┈┈┈┈┈┈┈┈┈
+
+    </template>
+
+-   When `<ase-tpl-key digit="<digit/>"/>` should be expanded, use:
+
+    <if condition="<digit/> is '1'"><template>➊</template></if>
+    <if condition="<digit/> is '2'"><template>➋</template></if>
+    <if condition="<digit/> is '3'"><template>➌</template></if>
+    <if condition="<digit/> is '4'"><template>➍</template></if>
+    <if condition="<digit/> is '5'"><template>➎</template></if>
+    <if condition="<digit/> is '6'"><template>➏</template></if>
+    <if condition="<digit/> is '7'"><template>➐</template></if>
+    <if condition="<digit/> is '8'"><template>➑</template></if>
+    <if condition="<digit/> is '9'"><template>➒</template></if>
+
 -   When `<ase-tpl-bullet-secondary/>` should be expanded, use:
 
     <template>⚪</template>
@@ -265,3 +322,9 @@ Template Patterns
 -   When `<ase-tpl-bullet-signal/>` should be expanded, use:
 
     <template>🟠</template>
+
+-   When `<ase-tpl-pad width="<width/>" text="<text/>"/>` should be expanded, use
+    (where <ws/> = ` ` x (<width/> - length("<text/>")), i.e., <ws/> is
+    the ` ` character repeated (<width/> - length("<text/>")) times):
+
+    <template><text/><ws/></template>

package/plugin/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.9.8",
+    "version":                              "0.9.10",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/skills/ase-arch-analyze/help.md

@@ -46,5 +46,5 @@ Analyze a specific module:
 
 ##  SEE ALSO
 
-`ase-arch-discover`, `ase-code-analyze`, `ase-code-resolve`,
-`ase-code-refactor`, `ase-code-insight`.
+[`ase-arch-discover`](../ase-arch-discover/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md), [`ase-code-resolve`](../ase-code-resolve/help.md),
+[`ase-code-refactor`](../ase-code-refactor/help.md), [`ase-code-insight`](../ase-code-insight/help.md).