@rse/ase 1.0.6 → 2.0.0

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

@@ -8,6 +8,11 @@
 `ase-task-grill`
     [`--help`|`-h`]
     [`--rounds`|`-r` *n*]
+    [`--until`|`-u` `MUST`|`SHOULD`|`MAY`]
+    [`--perspective`|`-p` *perspective*]
+    [`--ground`|`-G`]
+    [`--focus`|`-f` *section*[,...]]
+    [`--force`|`-F`]
     [`--next`|`-n` *option*[,...]]
     [*id*]
 
@@ -22,37 +27,114 @@ The skill identifies the essential aspects of the plan and raises up to
 carries a `FOCUS-AREA` -- `DOMAIN` (domain-specifics, must be
 clarified), `INTERFACE` (externally observable behavior or UI/API
 interfaces, must be clarified), `ARCHITECTURE` (structure, wiring,
-placement, or dependencies, should be clarified), or `IMPLEMENTATION`
-(inner technical details, can be clarified) -- and a 1-2 word `ASPECT`
-hint. The questions are sorted primarily by descending focus area
-importance (`DOMAIN`, `INTERFACE`, `ARCHITECTURE`, `IMPLEMENTATION`)
-and secondarily by the decision tree of their dependencies, so each
+placement, or dependencies, should be clarified), `IMPLEMENTATION`
+(inner technical details, can be clarified), `REGRESSION` (what must
+not break, should be clarified), or `CONFIRMATION` (what proves the
+specified behavior, should be clarified) -- and a 1-3 word `TOPIC`
+hint. The focus areas are selected by the plan sections under focus
+(`--focus`): `SPECIFICATION` selects `DOMAIN` and `INTERFACE`, `DESIGN`
+selects `ARCHITECTURE` and `IMPLEMENTATION`, and `VERIFICATION` selects
+`REGRESSION` and `CONFIRMATION`. The questions are sorted
+by descending focus area importance, then by descending individual
+impact, and finally by the decision tree of their dependencies, so each
 decision is asked after the decisions it depends on. It honors checks
 for *fuzzy language*, *conflicting terminology*, *conflicting code*,
 *non-concrete scenarios*, *unspecified architecture patterns*, and
 *unspecified dependencies*.
 
-In contrast to the batch grilling of `ase-code-edit --grill`, the
-questions are asked *sequentially*, one at a time: each question is
-announced as an `ASPECT n/N ▶ FOCUS ▷ ASPECT, QUESTION` line and then
-raised via an interactive dialog presenting two to four *grounded*
-answer alternatives labeled `A1`-`A4` (the current plan, marked with
-`⚑`, plus alternatives derived from the code base and world knowledge),
-the fixed `SKIP GRILLING` option (skip the remaining questions and
-rounds, keeping the answers gathered so far), and free-text input.
-Cancelling the dialog stops the skill and leaves the plan untouched.
-Once all aspects are resolved, the plan is updated and persisted, its
-`Properties:` frontmatter key gains the value `grilled`, and the user is
-offered a hand-off to editing, implementation, or preflight.
+As with `ase-code-edit --grill`, all questions of a round are announced
+together below a `GRILLING ROUND K/L` line (plain `GRILLING` for a
+single round) as a `QUESTION`/`ANSWERS` table with one row per
+question, each row carrying two to three *grounded* answer alternatives
+(the one reflecting the current plan marked with `⚑`). They are then
+asked in *one* batch via a single interactive dialog, whose only answer
+option is the fixed `SKIP GRILLING` (skip the remaining grilling, but
+still update the plan with the answers of the previous rounds), plus
+free-text input. The questions are numbered `1`, `2`, etc. and their
+answer alternatives are lettered `A`, `B`, etc., so the free-text input
+can cherry-pick answers with short responses matching `\d+[a-zA-Z]`
+(like `1A 2c`), freely mixed with keyword text. A question not
+addressed by the reply accepts its `⚑` answer, if one exists.
+Cancelling the dialog stops the skill without updating the plan with
+the current round. After every round, the plan is updated and
+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
+re-grilling (with the same grilling options), or a hand-off to editing,
+implementation, or draft.
+
+The *open* questions are recorded in the checkboxes of the plan's
+bullet-points: a bullet-point whose question stayed *unanswered*
+(because the grilling was skipped, or the reply did not address a
+question the plan offers no answer for) is marked `[?]`, an unanswered
+question the plan does not cover yet is added as a new `[?]`
+bullet-point, and an *answered* question resets its bullet-points to
+`[ ]`. When a section is grilled *again* (its `grilled:`*section* tag
+is already present), only its `[?]` bullet-points are re-asked, and a
+section without any `[?]` bullet-point is skipped entirely, unless
+`--force` is given. Bullet-points
+in state `[-]` (cancelled) or `[>]` (deferred) are never questioned.
 
 ##  OPTIONS
 
 -   `--rounds`|`-r` *n*:
-    The number of grill rounds to apply (default: `1`). Each round
-    starts from scratch from only the current plan, as updated by all
-    previous rounds, and re-derives its questions from it, forgetting
-    all questions and answers of previous rounds. With more than one
-    round, each round is announced as `GRILLING ROUND K/L`.
+    The *maximum* number of grill rounds to apply (default: `1`). Each
+    round starts from scratch from only the current plan, as updated and
+    saved by all previous rounds, and re-derives its questions from it,
+    forgetting all questions and answers of previous rounds. With more than one
+    round, each round is announced as `GRILLING ROUND K/L`. The grilling
+    stops early -- announced by a `grilling finished early` status line
+    -- once a round, even the first one, finds the open points clear
+    enough according to `--until`.
+
+-   `--until`|`-u` `MUST`|`SHOULD`|`MAY`:
+    Grill until at least all open points of the given severity or
+    higher are clear (default: `MUST`), where the severity follows from
+    the focus area: `MUST` (`DOMAIN`, `INTERFACE`), `SHOULD`
+    (`ARCHITECTURE`, `REGRESSION`, `CONFIRMATION`), and `MAY`
+    (`IMPLEMENTATION`). Independent of this, every open point is rated
+    with an individual impact (`HIGH`, `MEDIUM`, or `LOW`), which
+    decides which points are raised as questions and in which order
+    within a focus area.
+
+-   `--perspective`|`-p` *perspective*:
+    Grill exclusively from the logical *perspective* -- a keyword or
+    short hint like `domain`, `performance`, or `security`. The
+    perspective acts as an exclusive lens: only open points relevant from
+    this perspective are raised as questions, while every question still
+    carries its focus area, severity, and impact. The active perspective
+    is shown in the announcement line, like `GRILLING (security)`.
+    Without a perspective, the grilling is holistic.
+
+-   `--ground`|`-G`:
+    Ground the grilling in facts instead of the world knowledge of the
+    model alone: once before the first round, the artifacts of all kinds
+    (`SPEC`, `CODE`, `DOCS`, `INFR`, and `OTHR`) are scanned for
+    the project facts relevant to the grilled subject (from the given
+    perspective, if any) and the Internet/Web is searched for the
+    established practices, standards, patterns, and pitfalls about it.
+    These facts serve all rounds, both for raising the questions and for
+    preferably deriving their answer alternatives. The grounding is shown
+    in the announcement line, like `GRILLING (security, grounded)`. If
+    no usable facts are found, a warning is shown and the grilling falls
+    back to model knowledge.
+
+-   `--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.
+
+-   `--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.
 
 -   `--next`|`-n` *option*[,...]:
     Automatically answer the user dialog for the next step (at the end
@@ -62,9 +144,10 @@ offered a hand-off to editing, implementation, or preflight.
     to the downstream skill on hand-off so an entire pipeline can be
     pre-scripted in one shot. Recognized tokens at this skill: `none`
     (default, interactive answer required), `DONE` (no next step),
-    `EDIT` (hand-over to `ase-task-edit`), `IMPLEMENT` (hand-over to
-    `ase-task-implement`), or `PREFLIGHT` (hand-over to
-    `ase-task-preflight`).
+    `GRILL` (re-grilling via `ase-task-grill --force` with the same
+    grilling options), `EDIT` (hand-over to `ase-task-edit`),
+    `IMPLEMENT` (hand-over to `ase-task-implement`), or `DRAFT`
+    (hand-over to `ase-task-implement --draft`).
 
 ##  ARGUMENTS
 
@@ -100,6 +183,26 @@ Grill the current task plan in two rounds:
 ❯ /ase-task-grill --rounds 2
 ```
 
+Grill the current task plan exclusively from the performance
+perspective, grounded in the project artifacts and the Internet/Web:
+
+```text
+❯ /ase-task-grill --perspective performance --ground
+```
+
+Grill only the `DESIGN` and then the `SPECIFICATION` section of the
+current task plan:
+
+```text
+❯ /ase-task-grill --focus DES,SPEC
+```
+
+Re-grill the already grilled current task plan completely:
+
+```text
+❯ /ase-task-grill --force
+```
+
 Grill the current task plan and then hand off to editing:
 
 ```text
@@ -108,6 +211,6 @@ Grill the current task plan and then hand off to editing:
 
 ##  SEE ALSO
 
-[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md), [`ase-task-preflight`](../ase-task-preflight/help.md),
+[`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-reboot`](../ase-task-reboot/help.md),
 [`ase-task-implement`](../ase-task-implement/help.md), [`ase-task-view`](../ase-task-view/help.md), [`ase-task-list`](../ase-task-list/help.md),
 [`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md), [`ase-code-edit`](../ase-code-edit/help.md).

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

@@ -34,7 +34,7 @@ Procedure
     Inherit the always existing <ase-session-id/> and the current
     <ase-task-id/> from the current context.
 
-2.  <if condition="<request/> is NOT empty AND <request/> does NOT match the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`">
+2.  <if condition="<request/> is NOT empty AND <request/> does NOT match the regexp `^[a-zA-Z0-9#][a-zA-Z0-9#_-]*$`">
     Only output the following <template/> and then immediately
     *STOP* processing the entire current skill:
 
@@ -77,5 +77,12 @@ Procedure
         <template>
         ⧉ **ASE**: ◉ task: **<ase-task-id/>** (*updated*)
         </template>
+
+    -   If <text/> carries a line `NOTICE: <info/>` (the id does not
+        conform to the task id scheme of the project), additionally
+        output:
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ NOTICE: <info/>
+        </template>
     </if>
 

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

@@ -19,8 +19,11 @@ task id via the `ase_task_id` MCP tool.
 ##  ARGUMENTS
 
 -   *id*:
-    The new task id to activate. If omitted, the currently active
-    task id is reported.
+    The new task id to activate (characters `A-Z`, `a-z`, `0-9`, `#`,
+    `_`, and `-`). If omitted, the currently active task id is
+    reported. An id not conforming to the task id scheme of the
+    project (`project.task.idscheme`: `slug[:<words>]`, `seq[:<template>]`,
+    or `any`) is accepted, but noticed.
 
 ##  SCENARIOS
 
@@ -45,4 +48,4 @@ Switch to a specific task:
 ##  SEE ALSO
 
 [`ase-task-list`](../ase-task-list/help.md), [`ase-task-edit`](../ase-task-edit/help.md), [`ase-task-view`](../ase-task-view/help.md),
-[`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).
+[`ase-task-status`](../ase-task-status/help.md), [`ase-task-rename`](../ase-task-rename/help.md), [`ase-task-delete`](../ase-task-delete/help.md).