@rse/ase 1.0.4 → 1.0.6

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

@@ -4,25 +4,30 @@
 SpecBook Project Instantiation
 ==============================
 
--   The **SpecBook SCHEMA Model** of this project depends on
-    the value of the <ase-spec-schema/> placeholder (holding the
-    `project.artifact.spec.schema` configuration value):
+-   The **SpecBook SCHEMA Model** of this project depends on the value
+    of the <ase-spec-schema/> placeholder (holding the
+    `project.artifact.spec.schema` configuration value), which is a
+    *whitespace-separated list* of schema entries, merged in the given
+    order into *one* **SpecBook SCHEMA Model**:
 
     -   If <ase-spec-schema/> is *empty*:
 
-        Then the **SpecBook SCHEMA Model** is the standard YAML
-        schema configuration bundled with **ASE** in the file
-        `meta/ase-format-specbook.yaml` (relative to the plugin root),
-        which you *MUST* read via the `Read` tool before working on the
-        specification of the **SpecBook SPEC Model**.
+        Then the list is treated as the single entry `std`.
 
-    -   If <ase-spec-schema/> is *not empty*:
+    -   For each entry `std` in the list:
 
-        Then the **SpecBook SCHEMA Model** is the custom YAML schema
-        configuration of the project in the file <ase-spec-schema/>
-        (relative to the project root), which you *MUST* read via
-        the `Read` tool before working on the specification of the
-        **SpecBook SPEC Model**.
+        The entry names the standard YAML schema configuration bundled
+        with **ASE** in the file `meta/ase-format-specbook.yaml`
+        (relative to the plugin root).
+
+    -   For each *other* entry in the list:
+
+        The entry names a custom YAML schema configuration file of the
+        project (relative to the project root).
+
+    You *MUST* read all resulting schema configuration files via the
+    `Read` tool before working on the specification of the **SpecBook
+    SPEC Model**.
 
 -   The **SpecBook SPEC Model** of this project is the set of specification
     Markdown files in the directory <ase-spec-basedir/> (relative

package/plugin/meta/ase-format-specbook.yaml

@@ -45,7 +45,7 @@
       optional: true
     - name: THEME-STYLE
       desc: The theme style.
-      value: enum(dark,light)
+      value: enum(Dark,Light)
       optional: true
     - name: THEME-TONE
       desc: The theme color tone.
@@ -190,7 +190,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[TERM:*]], [[PREMISE:*]], [[RULE:*]], [[DM.ENTITY:*]], [[ROLE:*]], [[PERSONA:*]]"
+        nodes: "[[TERM:*]], [[PREMISE:*]], [[RULE:*]], [[DM.ENTITY:*]], [[ROLE:*]], [[PERSONA:*]], [[WORKFLOW:*]], [[CONVENTION:*]], [[CV.ENTITY:*]]"
         labeled: true
         qualified: true
         config:
@@ -257,7 +257,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[ROLE:*]], [[TERM:*]], [[PERSONA:*]], [[ACTIVITY:*]], [[USE-CASE:*]], [[CV.ENTITY:*]]"
+        nodes: "[[ROLE:*]], [[TERM:*]], [[PERSONA:*]], [[WORKFLOW:*]], [[ACTIVITY:*]], [[USE-CASE:*]], [[TRANSITION:*]], [[CV.ENTITY:*]]"
         labeled: true
         qualified: true
         config:
@@ -292,8 +292,8 @@
           optional: true
         - name: GENDER
           desc: >
-            The gender of the persona: `male`, `female`, or `diverse`.
-          value: enum(male,female,diverse)
+            The gender of the persona: `Male`, `Female`, or `Diverse`.
+          value: enum(Male,Female,Diverse)
           optional: true
         - name: AGE
           desc: >
@@ -312,8 +312,8 @@
           optional: true
         - name: PROFICIENCY
           desc: >
-            The technical and domain skill level of the persona: `novice`, `intermediate`, or `expert`.
-          value: enum(novice,intermediate,expert)
+            The technical and domain skill level of the persona: `Novice`, `Intermediate`, or `Expert`.
+          value: enum(Novice,Intermediate,Expert)
           optional: true
         - name: GOAL
           desc: >
@@ -714,7 +714,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[USE-CASE:*]], [[ROLE:*]], [[PERSONA:*]], [[STEP:*]], [[ACTIVITY:*]], [[FR.REQUIREMENT:*]], [[RULE:*]], [[TRANSITION:*]], [[PERMISSION:*]], [[PRINCIPLE:*]], [[CV.ENTITY:*]]"
+        nodes: "[[USE-CASE:*]], [[ROLE:*]], [[PERSONA:*]], [[STEP:*]], [[ACTIVITY:*]], [[FR.REQUIREMENT:*]], [[RULE:*]], [[DM.ENTITY:*]], [[TRANSITION:*]], [[PERMISSION:*]], [[PRINCIPLE:*]], [[STORYBOARD:*]], [[CV.ENTITY:*]], [[TEST-CASE:*]]"
         labeled: true
         qualified: true
         config:
@@ -830,7 +830,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[DM.ENTITY:*]], [[FR.REQUIREMENT:*]], [[USE-CASE:*]]"
+        nodes: "[[DM.ENTITY:*]], [[FR.REQUIREMENT:*]], [[USE-CASE:*]], [[LIFECYCLE:*]], [[FV.COMPONENT:*]], [[CONCERN:*]], [[TACTIC:*]], [[DECISION:*]], [[TEST-CASE:*]]"
         edges: "[[RELATION:*]]"
         labeled: true
         qualified: true
@@ -894,14 +894,16 @@
           desc: >
             A named directed relation of the entity, carrying a camel-cased, 1-3 word long, per-entity unique identifier and targeting another entity, and described by a 1-sentence description ("what") plus a 1-sentence rationale ("why"). A relation carries no attributes of its own: a relation needing attributes (an "association class") is reified as an entity of its own, related from both sides.
           optional: true
+          format:
+            maxTableColumns: 5
           props:
             - name: TARGET
               desc: Reference to the DATA-MODEL entity the directed relation targets.
               value: "[[DM.ENTITY:*]]"
             - name: KIND
               desc: >
-                The kind of the directed relation: `association` for a plain reference to an independent target entity, `aggregation` for a shared part-of relation whose target outlives the entity, or `composition` for an exclusive part-of relation whose target is owned by and deleted with the entity; defaults to `association`.
-              value: enum(association,aggregation,composition)
+                The kind of the directed relation: `Association` for a plain reference to an independent target entity, `Aggregation` for a (optionally even shared) part-of relation whose target outlives the entity, or `Composition` for an exclusive part-of relation whose target is owned by and deleted with the entity; defaults to `Association`.
+              value: enum(Association,Aggregation,Composition)
               optional: true
             - name: ARITY
               desc: >
@@ -1109,7 +1111,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[INTERFACE:*]], [[TYPE:*]], [[ENDPOINT:*]]"
+        nodes: "[[INTERFACE:*]], [[TYPE:*]], [[ENDPOINT:*]], [[FV.COMPONENT:*]]"
         labeled: true
         qualified: true
         config:
@@ -1175,7 +1177,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[TYPE:*]], [[INTERFACE:*]]"
+        nodes: "[[TYPE:*]], [[INTERFACE:*]], [[ENDPOINT:*]]"
         deep: true
         labeled: true
         qualified: true
@@ -1442,7 +1444,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[PRINCIPLE:*]], [[PERSONA:*]], [[STEP:*]], [[USE-CASE:*]], [[PATTERN:*]]"
+        nodes: "[[PRINCIPLE:*]], [[PERSONA:*]], [[STEP:*]], [[USE-CASE:*]], [[CONVENTION:*]], [[PATTERN:*]], [[ELEMENT:*]], [[DECISION:*]]"
         labeled: true
         qualified: true
         config:
@@ -1554,7 +1556,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[PATTERN:*]], [[PRINCIPLE:*]], [[STORYBOARD:*]]"
+        nodes: "[[PATTERN:*]], [[PRINCIPLE:*]], [[STORYBOARD:*]], [[DECISION:*]]"
         deep: true
         labeled: true
         qualified: true
@@ -1620,7 +1622,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[STORYBOARD:*]], [[PERSONA:*]], [[SCENARIO:*]], [[PATTERN:*]]"
+        nodes: "[[STORYBOARD:*]], [[PERSONA:*]], [[SCENARIO:*]], [[PATTERN:*]], [[MOCKUP:*]]"
         deep: true
         labeled: true
         qualified: true
@@ -1867,7 +1869,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[FV.COMPONENT:*]], [[FR.REQUIREMENT:*]], [[INTERFACE:*]], [[DM.ENTITY:*]], [[TACTIC:*]], [[DECISION:*]]"
+        nodes: "[[FV.COMPONENT:*]], [[FR.REQUIREMENT:*]], [[INTERFACE:*]], [[DM.ENTITY:*]], [[UNIT:*]], [[NODE:*]], [[CONCERN:*]], [[TACTIC:*]], [[DECISION:*]]"
         labeled: true
         qualified: true
         properties:
@@ -1960,6 +1962,7 @@
       diagram:
         type: hub
         center: self
+        nodes: "[[TS.TIER:*]], [[TS.TIER:*.COMPONENT:*]], [[DV.TIER:*]]"
         hierarchy: true
         properties:
           - PRODUCT
@@ -1975,7 +1978,7 @@
           diagram:
             type: hub
             center: self
-            nodes: "[[TS.TIER:*.COMPONENT:*]], [[FV.COMPONENT:*]], [[TACTIC:*]], [[DECISION:*]]"
+            nodes: "[[TS.TIER:*.COMPONENT:*]], [[FV.COMPONENT:*]], [[CONCERN:*]], [[TACTIC:*]], [[DECISION:*]]"
             labeled: true
             qualified: true
             properties:
@@ -2434,7 +2437,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[DV.TIER:*]], [[AREA:*]], [[NODE:*]], [[NETWORK:*]], [[FV.COMPONENT:*]], [[UNIT:*]], [[TACTIC:*]], [[DECISION:*]]"
+        nodes: "[[DV.TIER:*]], [[AREA:*]], [[NODE:*]], [[NETWORK:*]], [[FV.COMPONENT:*]], [[UNIT:*]], [[CONCERN:*]], [[TACTIC:*]], [[DECISION:*]]"
         labeled: true
         qualified: true
         properties:
@@ -2642,7 +2645,7 @@
       diagram:
         type: hub
         center: self
-        nodes: "[[TACTIC:*]], [[NR.REQUIREMENT:*]], [[FV.COMPONENT:*]], [[UNIT:*]], [[ASPECT:*]], [[NODE:*]], [[DM.ENTITY:*]], [[CONCERN:*]], [[DECISION:*]], [[TS.TIER:*.COMPONENT:*]]"
+        nodes: "[[TACTIC:*]], [[NR.REQUIREMENT:*]], [[FV.COMPONENT:*]], [[UNIT:*]], [[ASPECT:*]], [[NODE:*]], [[DM.ENTITY:*]], [[CONCERN:*]], [[DECISION:*]], [[TS.TIER:*.COMPONENT:*]], [[TEST-CASE:*]]"
         labeled: true
         qualified: true
         properties:

package/plugin/meta/ase-skill.md

@@ -476,6 +476,13 @@ Template Patterns
         un-styled text <raw-title/>.
     -   Set <bar/> to the `─` character repeated exactly max(0, 67 - <raw-title-len/>)
         times -- clamped to zero so an over-long title never yields a negative count.
+    -   Pre-wrap every line of <content/> at *96 visible columns* (the box
+        width minus the `│ ` prefix, Markdown markup not counted), breaking
+        only at word boundaries and never inside an identifier, path, URL,
+        or quoted code: the agent tool wraps longer lines *without* the `│ `
+        prefix and visibly breaks the box. Indent each continuation line to
+        the text column of its first line (e.g. behind a key glyph, bullet,
+        or padded label), so gutters stay aligned.
     -   Set <body/> to <content/> with all non-empty lines prefixed with
         `│ ` and all empty lines prefixed with just `│` (so no trailing
         whitespace is produced). Do *not* prefix any line twice -- the

package/plugin/output-styles/ase-terse.md

@@ -0,0 +1,58 @@
+---
+name: "ase-terse"
+description: Respond tersely, leading with results and skipping preamble and narration.
+keep-coding-instructions: true
+force-for-plugin: false
+---
+
+##  ASE Output Style
+
+In your communication to the user you should:
+
+-   **Assume no shared context**:
+    The user has not read anything you read: no files, no tool output, no
+    search results. Only your messages. Assume the user has no prior context on
+    internal files or draft iterations.
+
+-   **Respond tersely**:
+    The user chose brevity over narration, so keep your responses short and
+    direct while doing the work just as thoroughly.
+
+-   **Lead with the result**:
+    Your **FIRST** sentence **MUST** state the direct answer, verdict, or status
+    immediately and with zero preamble (like "Let me...", "Now I'll...", etc.).
+
+-   **Cut narration, keep substance**:
+    Don't restate the request, the plan, or each step you took. Report outcomes,
+    decisions, and anything the user must act on.
+
+-   **Select formatting per output block**:
+    Map decisions/tradeoffs to a *table*, temporal steps to a *numbered
+    list*, concepts to *bulleted list* anchors, caveats/warnings/notices to a
+    *callout/quote* (`> **Notice:**`), previews of code edits to a *unified
+    diff*, and execution syntax to a *code block*.
+
+-   **Execute tools silently**:
+    Perform intermediate tool operations silently without narrating your intent
+    or planned tool calls in your messages.
+
+-   **State things plainly**:
+    Skip hedging boilerplate. Mention a caveat only when it changes what the
+    user should do next.
+
+-   **Give full detail on request**:
+    When the user asks for an explanation or detail, answer completely.
+    Conciseness never means withholding requested information.
+
+-   **Never trade correctness for brevity**:
+    Error reports, failing test output, security warnings, and confirmations for
+    destructive actions keep their full content.
+
+-   **End without closing recap**:
+    Avoid telling the user what you already said in the same turn.
+
+Where these rules conflict with the default communication and formatting
+guidance of the agent harness, these rules here win. But these rules never
+override the ASE persona communication style, which stays in effect at all
+times.
+

package/plugin/skills/ase-help-intent/data.md

@@ -3172,12 +3172,13 @@ Generate a user-wide skill and overwrite a previous generation:
 The `ase-spec-activate` skill activates the know-how about the
 *SpecBook*-based specification (`SPEC`) of the project in the current
 session: it loads the *SpecBook* format contract, reads the *SpecBook*
-schema configuration of the project (the standard schema bundled with
-*ASE*, or the custom schema configured via `project.artifact.spec.schema`),
-and resolves the list of `SPEC` artifacts in the configured specification
-base directory. The activation is reported in a `SPEC ACTIVATED` box,
-listing the schema file (marked `standard` or `custom`) and the base
-directory with the number of resolved artifacts.
+schema configuration of the project (the schema files configured via
+`project.artifact.spec.schema`, where the entry `std` -- also the default
+-- names the standard schema bundled with *ASE*), and resolves the list
+of `SPEC` artifacts in the configured specification base directory. The
+activation is reported in a `SPEC ACTIVATED` box, listing the schema
+files (each marked `standard` or `custom`) and the base directory with
+the number of resolved artifacts.
 
 Once activated, the specification can be worked with *ad-hoc* in plain
 conversation for the remainder of the session: reading, querying, and

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

@@ -67,19 +67,21 @@ an ad-hoc change, and it *never* touches the artifact kinds `CODE`,
 
 3.  **Activate Schema:**
 
-    1.  Set <schema-file/> to the path of the **SpecBook SCHEMA Model**
-        of the project (resolved as described in `ase-format-spec.md`)
-        and <schema-kind/> to `standard` for the bundled schema or
-        `custom` for a project-specific one. Do not output anything.
-
-    2.  <if condition="the content of <schema-file/> was *not* already read into the current context -- neither by an earlier run of this skill nor by a dedicated specification skill">
-        Read the **SpecBook SCHEMA Model** in <schema-file/> via the
-        `Read` tool to learn the allowed object kinds, properties,
-        nestings, and value constraints. Do not output anything.
+    1.  Set <schema-files/> to the list of file paths constituting the
+        **SpecBook SCHEMA Model** of the project (resolved as described
+        in `ase-format-spec.md`), each annotated with `standard` for the
+        bundled schema or `custom` for a project-specific one. Do not
+        output anything.
+
+    2.  <if condition="the content of a file of <schema-files/> was *not* already read into the current context -- neither by an earlier run of this skill nor by a dedicated specification skill">
+        Read those files of the **SpecBook SCHEMA Model** in
+        <schema-files/> via the `Read` tool to learn the allowed object
+        kinds, properties, nestings, and value constraints. Do not
+        output anything.
         </if>
         <else>
-        Do *not* read <schema-file/> again -- its content is already
-        active in the context. Do not output anything.
+        Do *not* read the files of <schema-files/> again -- their content
+        is already active in the context. Do not output anything.
         </else>
 
 4.  **Activate Artifacts:**
@@ -98,7 +100,7 @@ an ad-hoc change, and it *never* touches the artifact kinds `CODE`,
     <template>
     <ase-tpl-boxed title="SPEC" subtitle="ACTIVATED">
 
-    **SCHEMA**: `<schema-file/>` (<schema-kind/>)
+    **SCHEMA**: <schema-files/> (one `<file/>` (`standard`|`custom`) entry per line, aligned)
     **SPEC**:   `<ase-spec-basedir/>` (<artifact-count/> artifacts)
 
     </ase-tpl-boxed>

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

@@ -14,12 +14,13 @@
 The `ase-spec-activate` skill activates the know-how about the
 *SpecBook*-based specification (`SPEC`) of the project in the current
 session: it loads the *SpecBook* format contract, reads the *SpecBook*
-schema configuration of the project (the standard schema bundled with
-*ASE*, or the custom schema configured via `project.artifact.spec.schema`),
-and resolves the list of `SPEC` artifacts in the configured specification
-base directory. The activation is reported in a `SPEC ACTIVATED` box,
-listing the schema file (marked `standard` or `custom`) and the base
-directory with the number of resolved artifacts.
+schema configuration of the project (the schema files configured via
+`project.artifact.spec.schema`, where the entry `std` -- also the default
+-- names the standard schema bundled with *ASE*), and resolves the list
+of `SPEC` artifacts in the configured specification base directory. The
+activation is reported in a `SPEC ACTIVATED` box, listing the schema
+files (each marked `standard` or `custom`) and the base directory with
+the number of resolved artifacts.
 
 Once activated, the specification can be worked with *ad-hoc* in plain
 conversation for the remainder of the session: reading, querying, and