@rse/ase 0.9.65 → 0.9.66

package/plugin/skills/ase-meta-search/help.md

@@ -24,14 +24,14 @@ Brave, or `WebSearch` individually.
 
 ##  OPTIONS
 
-`--services`|`-s`=(`all`|`perplexity`|`brave`|`exa`|`websearch`)...:
+-   `--services`|`-s`=(`all`|`perplexity`|`brave`|`exa`|`websearch`)...:
     The comma-separated list of search backends to query. The default
     `all` queries every available backend;
     otherwise only the listed backends are queried.
 
 ##  ARGUMENTS
 
-*query*:
+-   *query*:
     The search query to dispatch to the search services.
 
 ##  SCENARIOS

package/plugin/skills/ase-meta-steelman/help.md

@@ -50,20 +50,20 @@ cheerleading.
 
 ##  OPTIONS
 
-`--count`|`-c` *count*:
+-   `--count`|`-c` *count*:
     Surface at least *count* strong pro-theses (default *10*) per defense
     pass before sorting and reporting the top *count* and deriving the
     *FORTIFICATION*. An invalid or non-positive *count* reverts to the
     default *10*.
 
-`--rounds`|`-r` *rounds*:
+-   `--rounds`|`-r` *rounds*:
     Run *rounds* iterative defense rounds (default *1*), feeding each
     round's *FORTIFICATION* in as the next round's *thesis*. An invalid
     or non-positive *rounds* reverts to the default *1*.
 
 ##  ARGUMENTS
 
-*thesis*:
+-   *thesis*:
     The statement, claim, or position to be charitably strengthened.
     It may be technical, factual, or opinion-based; the skill defends
     its strongest ("steelman") interpretation.

package/plugin/skills/ase-meta-why/help.md

@@ -31,13 +31,13 @@ source code changes.
 
 ##  OPTIONS
 
-`--depth`|`-d` *N*:
+-   `--depth`|`-d` *N*:
     The *maximum* number of "why" iterations (the Five-Whys chain
     length), acting as an *upper bound* only - the analysis still stops
     early once the root cause is reached. Defaults to *5*. A non-numeric
     or non-positive value falls back to the default.
 
-`--width`|`-w` *M*:
+-   `--width`|`-w` *M*:
     The *maximum* number of *candidate sub-causes* to surface per "why"
     level. With the default *1*, the skill walks a single causality chain
     (classic Five-Whys); with *M* > 1, each level surfaces up to *M*
@@ -51,7 +51,7 @@ source code changes.
 
 ##  ARGUMENTS
 
-*fact*:
+-   *fact*:
     The observed *fact* (symptom, problem, or surprising outcome)
     whose root cause should be investigated. The skill implicitly
     prepends "Why" to form the initial question.

package/plugin/skills/ase-meta-workflow/SKILL.md

@@ -338,8 +338,9 @@ Procedure
         following the `Generated Skill Contract` above.
 
     3.  Write <skill-content/> to <target-skill/>, creating the directory
-        `<dir/>/<new-skill-name/>` if it does not exist yet. Calculate the
-        number of words <words/> of <skill-content/>.
+        `<dir/>/<new-skill-name/>` if it does not exist yet. Then call the
+        `ase_text_metric(file: "<target-skill/>")` tool of the `ase` MCP
+        server and set <words/> to the `words` field of its result.
 
     4.  Report the result with the following <template/>:
 

package/plugin/skills/ase-meta-workflow/help.md

@@ -66,7 +66,7 @@ agent tool:
 
 ##  OPTIONS
 
-`--scope`|`-s` `local`|`user`:
+-   `--scope`|`-s` `local`|`user`:
     Where the generated skill is stored. With `local` (the default),
     it is written into the current project, where it can be committed
     and reviewed alongside the code. With `user`, it is written into the
@@ -77,20 +77,20 @@ agent tool:
     Copilot*, and `.agents/skills/` and `~/.codex/skills/` under *OpenAI
     Codex*.
 
-`--force`|`-f`:
+-   `--force`|`-f`:
     Overwrite an already existing skill. Without this option, the skill
     refuses with an error as soon as the target `SKILL.md` exists, so
     hand-edited skills are never lost silently.
 
 ##  ARGUMENTS
 
-*skill-name*:
+-   *skill-name*:
     Name of the skill to generate, matching `^[a-zA-Z][a-zA-Z0-9_-]*$`.
     It is used as the directory name, as the frontmatter `name`, and as
     the resulting `/`*skill-name* command (respectively the
     `$`*skill-name* mention under *OpenAI Codex*).
 
-*workflow-description*:
+-   *workflow-description*:
     Free-text description of the workflow the generated skill should
     perform. Mentioning that actions run "in parallel", that they are
     dispatched "in a sub-agent", or naming concrete `ase-xxx-xxx` skills

package/plugin/skills/ase-meta-workflow/workflow.txt

@@ -15,13 +15,16 @@ START               -> ase-arch-discover
 START               -> ase-code-insight
 START               -> ase-code-explain
 START               -> ase-code-lint
-START               -> ase-docs-distill
+START               -> ase-docs-shorten
+START               -> ase-docs-refine
 START               -> ase-docs-proofread
+START               -> ase-docs-distill
 START               -> ase-meta-review
 START               -> ase-meta-diff
 START               -> ase-meta-changelog
 START               -> ase-meta-commit
 START               -> ase-meta-proximity
+START               -> ase-meta-mint
 START               -> ase-meta-workflow
 START               -> ase-code-dissect
 ase-help-skill      -> END
@@ -41,13 +44,16 @@ ase-arch-discover   -> END
 ase-code-insight    -> END
 ase-code-explain    -> END
 ase-code-lint       -> END
-ase-docs-distill    -> END
+ase-docs-shorten    -> END
+ase-docs-refine     -> END
 ase-docs-proofread  -> END
+ase-docs-distill    -> END
 ase-meta-review     -> END
 ase-meta-diff       -> END
 ase-meta-changelog  -> END
 ase-meta-commit     -> END
 ase-meta-proximity  -> END
+ase-meta-mint       -> END
 ase-meta-workflow   -> END
 ase-code-dissect    -> END
 START               -> SKETCH

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

@@ -454,7 +454,7 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
     *NOT* run any build, tests, linter, or type-checker.
 
     1.  Validate the specification and capture its <diagnostics/> array
-        of `{ file, line, column, message }` objects:
+        of `{ file, line, column, severity, message }` objects:
 
         <if condition="<worktree-dir/> is not empty">
         Run the command `ase spec lint` with <worktree-dir/> as its

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

@@ -45,7 +45,7 @@ timestamp refreshed.
 
 ##  OPTIONS
 
-`--grill`|`-g`:
+-   `--grill`|`-g`:
     Grill the query before implementing, similar to `ase-task-grill`:
     raise 1-10 questions per round which resolve the open points of the
     query. Each question carries a `FOCUS-AREA` -- `DOMAIN`
@@ -69,20 +69,20 @@ timestamp refreshed.
     into the WHAT and HOW parts of the query. Without `--grill`, no
     questions are asked at all.
 
-`--grill-rounds`|`-r` *n*:
+-   `--grill-rounds`|`-r` *n*:
     The number of grill rounds to apply (default: `1`). Each round
     starts from scratch from only the current WHAT and HOW parts,
     forgetting all information of previous rounds, and closes with an
     `EDIT TODO` box. Only effective together with `--grill`.
 
-`--verify`|`-v`:
+-   `--verify`|`-v`:
     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.
 
-`--worktree`|`-w`:
+-   `--worktree`|`-w`:
     Apply the change sets inside a dedicated Git worktree (as
     `ase-task-implement --worktree`) instead of the current working
     copy. One single worktree, named by a two-word id derived from the
@@ -91,7 +91,7 @@ timestamp refreshed.
     the validation then runs as the `ase spec lint` command inside the
     worktree.
 
-`--loop`|`-l`:
+-   `--loop`|`-l`:
     Loop the whole state cycle: after each iteration, ask for the next
     edit query via the interactive `Edit Query` dialog and repeat, until
     the user answers with its fixed `STOP SKILL` option or cancels the
@@ -99,7 +99,7 @@ timestamp refreshed.
 
 ##  ARGUMENTS
 
-*query*:
+-   *query*:
     Description of the specification edit to perform. When omitted, the
     skill asks for the query via an interactive `Edit Query` dialog,
     carrying the fixed `STOP SKILL` option plus free-text input.

package/plugin/skills/ase-sync-export/SKILL.md

@@ -74,7 +74,9 @@ Procedure
 
     1.  Call the `ase_specbook_lint()` tool of the `ase` MCP server
         *once* and read its returned `diagnostics` array of `{ file,
-        line, column, message }` objects. Do not output anything.
+        line, column, severity, message }` objects, reduced to those
+        entries whose <severity/> is `error`, as only those make the
+        export fail. Do not output anything.
 
     2.  <if condition="<diagnostics/> is not empty">
 

package/plugin/skills/ase-sync-export/help.md

@@ -40,7 +40,7 @@ and reports that very command; when it falls back onto a system-installed
 
 ##  OPTIONS
 
-`--output`|`-o` *output*[,...]:
+-   `--output`|`-o` *output*[,...]:
     The comma-separated list of `[<format>:]<file>` entries to render,
     with each file path relative to the project root. Defaults to the
     single HTML rendering `index.html` inside the `SPEC` base directory

package/plugin/skills/ase-sync-import/SKILL.md

@@ -175,7 +175,7 @@ Procedure
 
         Validate the specification by calling the `ase_specbook_lint()`
         tool of the `ase` MCP server and reading its returned
-        `diagnostics` array of `{ file, line, column, message }`
+        `diagnostics` array of `{ file, line, column, severity, message }`
         objects. If it is not empty, fix the reported problems in the
         affected `SPEC` artifacts via the `Write`/`Edit` tools and call
         the tool again -- for at most *three* rounds in total. Do not

package/plugin/skills/ase-sync-import/help.md

@@ -45,14 +45,14 @@ at most three rounds; any remaining diagnostics are surfaced.
 
 ##  OPTIONS
 
-`--target`|`-t` *target*[,...]:
+-   `--target`|`-t` *target*[,...]:
     The comma-separated list of artifact kinds to generate or update.
     Defaults to `SPEC`. The skill errors out on an empty target or
     an unknown/unsupported kind.
 
 ##  ARGUMENTS
 
-*hint*:
+-   *hint*:
     The mandatory free-form description of the foreign sources to import
     from (e.g. a file path, directory, URL, or pasted text). The skill
     errors out on an empty hint.

package/plugin/skills/ase-sync-reconcile/SKILL.md

@@ -192,7 +192,7 @@ Procedure
 
         Validate the specification by calling the `ase_specbook_lint()`
         tool of the `ase` MCP server and reading its returned
-        `diagnostics` array of `{ file, line, column, message }`
+        `diagnostics` array of `{ file, line, column, severity, message }`
         objects. If it is not empty, fix the reported problems in the
         affected `SPEC` artifacts via the `Write`/`Edit` tools and call
         the tool again -- for at most *three* rounds in total. Do not

package/plugin/skills/ase-sync-reconcile/help.md

@@ -40,24 +40,24 @@ in at most three rounds; any remaining diagnostics are surfaced.
 
 ##  OPTIONS
 
-`--bidirectional`|`-b`:
+-   `--bidirectional`|`-b`:
     Reconcile the *target* and *source* artifacts so that they
     faithfully reflect the current state of *each other*, instead of
     only updating the *target* from the *source*. With this flag, a kind
     present in *target* is *not* removed from *source*.
 
-`--target`|`-t` *target*[,...]:
+-   `--target`|`-t` *target*[,...]:
     The comma-separated list of artifact kinds to update. Required (the
     skill errors out on an empty target).
 
-`--source`|`-s` *source*[,...]:
+-   `--source`|`-s` *source*[,...]:
     The comma-separated list of artifact kinds to update *from*. The
     special value `auto` resolves to all recognized kinds except those
     in *target*.
 
 ##  ARGUMENTS
 
-*hint*:
+-   *hint*:
     An optional free-form filtering hint that narrows the source and/or
     target artifacts, or the aspects of those artifacts to take into
     account during reconciliation.

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

@@ -124,14 +124,17 @@ Set <args></args> (set args to empty).
             example. If a shortening would change meaning, *keep the
             longer wording*.
 
-    2.  *Persist only if smaller*: compare the condensed <task-content/>
-        against <content-before/>, without counting words.
+    2.  *Persist only if smaller*: call the `ase_text_metric(text:
+        "<text/>")` tool of the `ase` MCP server once for the condensed
+        <task-content/> and once for <content-before/>, and take the
+        `chars` field of each result, so the comparison rests on a
+        *measured* length instead of an estimate.
 
-        -   <if condition="the condensed <task-content/> is strictly shorter than <content-before/>">
+        -   <if condition="the condensed <task-content/> has strictly fewer `chars` than <content-before/>">
             <expand name="task-save-content" arg1="plan condensed"></expand>
             </if>
 
-        -   <if condition="the condensed <task-content/> is NOT strictly shorter than <content-before/>">
+        -   <if condition="the condensed <task-content/> has NOT strictly fewer `chars` than <content-before/>">
             Do *not* save and do *not* bump the timestamp. Set
             <task-content><content-before/></task-content> (keep the
             *unchanged* stored plan, discard the condensed one).

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

@@ -38,7 +38,7 @@ After condensing, the user is asked whether to stop or hand off to
 
 ##  OPTIONS
 
-`--next`|`-n` *option*[,...]:
+-   `--next`|`-n` *option*[,...]:
     Automatically answer the user dialog for the next step. *option*
     is a single token or a *comma-separated chronological list* of
     tokens; the *first* token is consumed by this skill, and any
@@ -53,7 +53,7 @@ After condensing, the user is asked whether to stop or hand off to
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     The unique identifier of the task whose plan should be condensed.
     If omitted, the *current* task id is used.
 

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

@@ -19,7 +19,7 @@ switched back to `default`.
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     The unique identifier of the task plan to delete. If omitted,
     the current task id is used.
 

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

@@ -48,31 +48,31 @@ The epic plan itself always stays *untouched*.
 
 ##  OPTIONS
 
-`--max-parts`|`-m` *count*:
+-   `--max-parts`|`-m` *count*:
     Upper bound for the number of derived parts (default: `8`). The
     lower bound is always `2`, because fewer parts are no dissection.
 
-`--dry`|`-d`:
+-   `--dry`|`-d`:
     *Report only* -- print the dissection table but create *no*
     artifacts at all, so the decision stays fully reversible. Note that
     this meaning differs from `--dry`/`-d` in `ase-code-craft`, where it
     instead omits the `##  VERIFICATION` section of the composed plan.
 
-`--force`|`-f`:
+-   `--force`|`-f`:
     Overwrite already existing sub-task plans. Without this option, the
     skill detects colliding sub-task ids *before* writing anything,
     reports them, and stops with status *targets exist*.
 
 ##  ARGUMENTS
 
-*task-id*:
+-   *task-id*:
     The unique identifier of the task whose plan should be dissected.
     If omitted, the *current* task id is used. A *lone* argument
     matching the task id syntax is always taken as the *task id*, never
     as a hint; to combine both, separate them with a `:` character, as
     in `auth: split by API and UI`.
 
-*dissect-hint*:
+-   *dissect-hint*:
     A free-text hint telling *how* the epic should be split. If omitted,
     the parts are derived from the plan alone.
 

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

@@ -28,7 +28,7 @@ for the changed plan.
 
 ##  OPTIONS
 
-`--plan`|`-p` *option*:
+-   `--plan`|`-p` *option*:
     Automatically answer the user dialog for the plan refinement
     with *option*, which can be either `none` (default, interactive
     answer required), `OVERWRITE` (overwrite an existing plan
@@ -36,7 +36,7 @@ for the changed plan.
     *instruction*), or `PRESERVE` (preserve the existing plan by
     ignoring *instruction* and stopping skill processing).
 
-`--dry`|`-d`:
+-   `--dry`|`-d`:
     Generate any *new* plan *without* the `##  VERIFICATION` section.
     Applies only to freshly generated plans, not to existing plans
     loaded from disk. When `ase-task-implement` later applies such
@@ -44,7 +44,7 @@ for the changed plan.
     build, tests, linter, type-checker, or program execution) once
     the source files have been modified.
 
-`--next`|`-n` *option*[,...]:
+-   `--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
     chronological list* of tokens; each iteration of the planning
@@ -60,7 +60,7 @@ for the changed plan.
 
 ##  ARGUMENTS
 
-*id* | *id*: *instruction* | *instruction*:
+-   *id* | *id*: *instruction* | *instruction*:
     Edit the task with the unique identifier *id* (default: `default`).
     Optionally, *instruction* either gives instructions for creating a
     new task or gives instructions for refining an existing task.

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

@@ -47,14 +47,14 @@ offered a hand-off to editing, implementation, or preflight.
 
 ##  OPTIONS
 
-`--rounds`|`-r` *n*:
+-   `--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`.
 
-`--next`|`-n` *option*[,...]:
+-   `--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
     chronological list* of tokens; the *first* token is consumed by
@@ -68,7 +68,7 @@ offered a hand-off to editing, implementation, or preflight.
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     Grill the task with the unique identifier *id* (default: `default`).
     The skill accepts *only* an optional *id* argument and never a
     free-text instruction.

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

@@ -18,7 +18,7 @@ task id via the `ase_task_id` MCP tool.
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     The new task id to activate. If omitted, the currently active
     task id is reported.
 

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

@@ -55,7 +55,7 @@ delete the task plan, unless `--next` pre-selects this choice.
 
 ##  OPTIONS
 
-`--next`|`-n` *option*[,...]:
+-   `--next`|`-n` *option*[,...]:
     Automatically answer the user dialog for the next step. *option*
     is a single token or a *comma-separated chronological list* of
     tokens; the *first* token is consumed by this skill, and any
@@ -65,7 +65,7 @@ delete the task plan, unless `--next` pre-selects this choice.
     answer required), `DONE` (preserve task plan and stop), or
     `DELETE` (hand off to `ase-task-delete`).
 
-`--worktree`|`-w`:
+-   `--worktree`|`-w`:
     Apply the change set inside a dedicated *Git WorkTree* instead of
     the current working copy. The worktree directory `.ase/worktree/<id>`
     and its equally named branch are derived from the *task id* and
@@ -75,7 +75,7 @@ delete the task plan, unless `--next` pre-selects this choice.
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     The unique identifier of the task whose plan should be
     implemented. If omitted, the *current* task id is used.
 

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

@@ -37,17 +37,17 @@ REJECTED  DEFERRED  BLOCKED  CANCELLED
 
 ##  OPTIONS
 
-`--verbose`|`-v`:
+-   `--verbose`|`-v`:
     Render an additional `Status` column with the lifecycle state and an
     additional `Last Modified` column with the `YYYY-MM-DD HH:MM`
     timestamp of each task plan.
 
-`--include`|`-i`=*state*[`,`...]:
+-   `--include`|`-i`=*state*[`,`...]:
     Restrict the listed task plans to the given comma-separated list of
     lifecycle states (e.g. `STARTED,BLOCKED`). Without this option, all
     eight states are listed. The `none` sentinel selects no state at all.
 
-`--exclude`|`-e`=*state*[`,`...]:
+-   `--exclude`|`-e`=*state*[`,`...]:
     Remove the given comma-separated list of lifecycle states from the
     listed task plans. Applied *after* `--include`, so
     `-i DRAFTED,STARTED -e STARTED` lists `DRAFTED` only. Defaults to

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

@@ -37,7 +37,7 @@ unless `--next` pre-selects this choice.
 
 ##  OPTIONS
 
-`--next`|`-n` *option*[,...]:
+-   `--next`|`-n` *option*[,...]:
     Automatically answer the user dialog for the next step. *option*
     is a single token or a *comma-separated chronological list* of
     tokens; the *first* token is consumed by this skill, and any
@@ -51,7 +51,7 @@ unless `--next` pre-selects this choice.
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     The unique identifier of the task whose plan should be
     preflighted. If omitted, the *current* task id is used.
 

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

@@ -24,7 +24,7 @@ unless `--next` pre-selects this choice.
 
 ##  OPTIONS
 
-`--next`|`-n` *option*[,...]:
+-   `--next`|`-n` *option*[,...]:
     Automatically answer the user dialog for the next step. *option*
     is a single token or a *comma-separated chronological list* of
     tokens; the *first* token is consumed by this skill, and any
@@ -39,7 +39,7 @@ unless `--next` pre-selects this choice.
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     The unique identifier of the task whose plan should be rebooted.
     If omitted, the *current* task id is used.
 

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

@@ -19,7 +19,7 @@ task id is automatically switched to *new*.
 
 ##  ARGUMENTS
 
-[*old*] *new*:
+-   [*old*] *new*:
     The *old* task id to rename and the *new* task id to assign.
     If only one token is given, *old* defaults to the current
     task id.

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

@@ -25,14 +25,14 @@ the plan in full, without any truncation or summarization.
 
 ##  OPTIONS
 
-`--full`|`-f`:
+-   `--full`|`-f`:
     Render the plan in full, without collapsing the
     `IMPLEMENTATION DRAFT` section. By default, that section is
     replaced with `[...]` for plans longer than 90 lines.
 
 ##  ARGUMENTS
 
-*id*:
+-   *id*:
     The unique identifier of the task plan to view. If omitted,
     the current task id is used.