@rse/ase 0.9.53 → 0.9.55

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-list
-argument-hint: "[--help|-h] [--verbose|-v]"
+argument-hint: "[--help|-h] [--verbose|-v] [--include|-i=<state>[,...]] [--exclude|-e=<state>[,...]]"
 description: >
     List all available task ids.
     Use when user wants to see all tasks.
@@ -19,7 +19,7 @@ List Task Plans
 
 <expand name="getopt"
     arg1="ase-task-list"
-    arg2="--verbose|-v">
+    arg2="--verbose|-v --include|-i=none --exclude|-e=COMPLETED,CANCELLED">
     $ARGUMENTS
 </expand>
 
@@ -30,13 +30,40 @@ List Task Plans
 Procedure
 ---------
 
-1.  Call the `ase_task_list(verbose: <getopt-option-verbose/>)` tool from
+1.  Determine the *effective state set* <states/>, i.e., the lifecycle
+    states a task plan has to be in to be listed at all. For this, parse
+    <getopt-option-include/> and <getopt-option-exclude/> as
+    comma-separated token lists, silently dropping the `none` sentinel
+    and any empty token. If a token <token/> is *not* one of the eight
+    `Status:` values `DRAFTED`, `REJECTED`, `APPROVED`, `DEFERRED`,
+    `STARTED`, `BLOCKED`, `COMPLETED`, or `CANCELLED`, only output the
+    following <template/> and then *STOP* processing the entire current
+    skill:
+
+    <template>
+    ⧉ **ASE**: ✪ skill: **ase-task-list**, ▶ ERROR: invalid state: **<token/>**
+    </template>
+
+    Otherwise set <states/> to *all* eight states if both lists are
+    empty, to the *include* list if only it is non-empty, to all eight
+    *minus* the *exclude* list if only it is non-empty, and to the
+    *include* list *minus* the *exclude* list if both are non-empty. If
+    the resulting <states/> is *empty*, only output the following
+    <template/> and then *STOP* processing the entire current skill:
+
+    <template>
+    ⧉ **ASE**: ✪ skill: **ase-task-list**, ▶ ERROR: options `--include` and `--exclude` cancel out to an empty state set
+    </template>
+
+2.  Call the `ase_task_list(verbose: <getopt-option-verbose/>)` tool from
     the `ase` MCP server. The result is a structured object with a
-    `tasks` array where each entry has an `id` field, and -- if
-    <getopt-option-verbose/> is `true` -- additionally an `mtime` field
-    (formatted as `YYYY-MM-DD HH:MM`).
+    `tasks` array where each entry has an `id` and a `status` field, and
+    -- if <getopt-option-verbose/> is `true` -- additionally an `mtime`
+    field (formatted as `YYYY-MM-DD HH:MM`). *Drop* from the `tasks`
+    array every entry whose `status` is *not* contained in <states/>. Do
+    not output anything.
 
-2.  If the `tasks` array is empty, output the following <template/>:
+3.  If the `tasks` array is empty, output the following <template/>:
 
     <template>
     ⧉ **ASE**: ◉ tasks: *(none)*
@@ -45,16 +72,16 @@ Procedure
     Else, dispatch on <getopt-option-verbose/>:
 
     -   If <getopt-option-verbose/> is `true`, output the list of tasks
-        with the following <template/>, where each <id/> and <mtime/>
-        correspond to an entry in the task list:
+        with the following <template/>, where each <id/>, <status/>, and
+        <mtime/> correspond to an entry in the task list:
 
         <template>
         ⧉ **ASE**: ◉ tasks:
 
-        | *Task Id* | *Last Modified*    |
-        |-----------|--------------------|
-        | **<id/>** | `<mtime/>`         |
-        | [...]     | [...]              |
+        | *Task Id* | *Status*    | *Last Modified*    |
+        |-----------|-------------|--------------------|
+        | **<id/>** | `<status/>` | `<mtime/>`         |
+        | [...]     | [...]       | [...]              |
 
         </template>
 
@@ -72,7 +99,7 @@ Procedure
 
         </template>
 
-3.  Finally, give the closing hints by expanding the following (which,
+4.  Finally, give the closing hints by expanding the following (which,
     depending on the configured <ase-guidance-level/>, may each expand
     into nothing and hence emit no output at all):
 
@@ -81,6 +108,11 @@ Procedure
     Use `/ase-task-id <id>` to switch to one of the listed tasks and `/ase-task-view` to inspect its plan.
     </ase-tpl-hint>
     </if>
+    <elseif condition="entries were dropped by the state filtering of step 2">
+    <ase-tpl-hint level="normal">
+    All task plans were filtered out by the effective state set -- use `/ase-task-list --exclude none` to list them regardless of their status.
+    </ase-tpl-hint>
+    </elseif>
     <else>
     <ase-tpl-hint level="normal">
     No task plan exists yet -- use `/ase-task-edit` to create one through a conversational loop.
@@ -89,7 +121,11 @@ Procedure
 
     <if condition="<getopt-option-verbose/> is not equal `true`">
     <ase-tpl-hint level="verbose">
-    Use `/ase-task-list --verbose` to additionally show the last-modified timestamp of each task plan.
+    Use `/ase-task-list --verbose` to additionally show the status and the last-modified timestamp of each task plan.
     </ase-tpl-hint>
     </if>
 
+    <ase-tpl-hint level="verbose">
+    Use `/ase-task-list --include`/`--exclude` to narrow the listing to certain lifecycle states, e.g. `--include STARTED,BLOCKED`.
+    </ase-tpl-hint>
+

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

@@ -8,35 +8,78 @@
 `ase-task-list`
     [`--help`|`-h`]
     [`--verbose`|`-v`]
+    [`--include`|`-i`=*state*[`,`...]]
+    [`--exclude`|`-e`=*state*[`,`...]]
 
 ##  DESCRIPTION
 
 The `ase-task-list` skill lists all available *task ids* in the
 current project by calling the `ase_task_list` MCP tool. In the
 default mode, only the task ids are rendered as a single-column
-Markdown table. In verbose mode, the last-modified timestamp of
-each task plan is rendered as an additional column.
+Markdown table. In verbose mode, the lifecycle status and the
+last-modified timestamp of each task plan are rendered as additional
+columns.
+
+The listing is restricted to an *effective state set*, derived from the
+`Status:` frontmatter key of each task plan (which defaults to `DRAFTED`
+for a plan carrying no such key): with `--include` only, exactly the
+listed states are shown; with `--exclude` only, all states except the
+listed ones; with both, the included ones minus the excluded ones. An
+unknown state, or a combination which cancels out to an empty set,
+aborts the skill with an error. By default,
+`--exclude COMPLETED,CANCELLED` is in effect, so finished and
+abandoned task plans stay out of the way. The eight states are:
+
+```text
+DRAFTED   APPROVED  STARTED  COMPLETED
+REJECTED  DEFERRED  BLOCKED  CANCELLED
+```
 
 ##  OPTIONS
 
 `--verbose`|`-v`:
-    Render an additional `Last Modified` column with the
-    `YYYY-MM-DD HH:MM` timestamp of each task plan.
+    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*[`,`...]:
+    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*[`,`...]:
+    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
+    `COMPLETED,CANCELLED`; pass `--exclude none` to suppress the
+    default and list task plans in every state.
 
 ##  EXAMPLES
 
-List all task ids:
+List all unfinished task ids:
 
 ```text
 ❯ /ase-task-list
 ```
 
-List all task ids together with their last-modified timestamps:
+List all task ids together with their status and last-modified timestamps:
 
 ```text
 ❯ /ase-task-list --verbose
 ```
 
+List the task ids of every task plan, including the finished ones:
+
+```text
+❯ /ase-task-list --exclude none
+```
+
+List only the task ids of the task plans currently under work:
+
+```text
+❯ /ase-task-list --include STARTED,BLOCKED
+```
+
 ##  SEE ALSO
 
 [`ase-task-id`](../ase-task-id/help.md), [`ase-task-view`](../ase-task-view/help.md), [`ase-task-edit`](../ase-task-edit/help.md),

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

@@ -32,6 +32,8 @@ for a corresponding, *complete source code change set*.
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-common-code.md
 
 Procedure
 ---------
@@ -59,6 +61,10 @@ Procedure
         or `ase-task-edit` skills first to create a task plan. Then
         immediately stop processing this skill.
 
+    3.  Internalize the tenets stated by the plan:
+
+        <expand name="code-tenets-from-plan"></expand>
+
 3.  **Create Implementation Draft:**
 
     1.  Perform a *preflight* of the *implementation* of <task-content/> by creating a
@@ -82,16 +88,22 @@ Procedure
 
         </template>
 
-    3.  <if condition="<task-content/> contains '⚙   Modified:'">
+    3.  <if condition="the frontmatter of <task-content/> carries a `Modified:` key">
         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. Update
-        the `⚙   Modified: ...` line of <task-content/> with the new
-        `⚙   Modified: <timestamp-modified/>`.
+        the `Modified: ...` frontmatter key of <task-content/> with the
+        new <timestamp-modified/> value.
         Do not output anything.
         </if>
 
+        Additionally *add* the value `preflighted` to the `Properties:`
+        frontmatter key of <task-content/> if it is still absent, keeping
+        all already present values and *creating* the whole key (with the
+        single value `preflighted`) if the plan carries none. Do not
+        output anything.
+
     4.  Finally, call the `ase_task_save(id: "<ase-task-id/>",
         text: "<task-content/>")` tool of the `ase` MCP server to save the updated
         task plan content. Calculate the number of words <words/> of

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

@@ -16,9 +16,17 @@ The `ase-task-preflight` skill performs a *preflight* (dry-run,
 test-drive) of the *implementation* of a task plan by creating a
 draft for a corresponding, complete *artifact change set* in
 *unified diff* format. The draft is appended to the task plan as
-an `IMPLEMENTATION DRAFT` section (replacing any previous draft).
+an `IMPLEMENTATION DRAFT` section (replacing any previous draft) and
+the plan's `Properties:` frontmatter key gains the value `preflighted`.
 No source files are modified.
 
+The *kind of change* stated by the plan's `Kind:` frontmatter key
+(`CRAFTING`, `REFACTORING`, or `RESOLVING`) selects which
+*operation-specific tenet set* of the **ASE Tenets** is internalized
+before the draft is produced, in addition to the always applying
+**GENERIC TENETS**. If a plan carries no such key, the kind is
+*inferred* from the plan content, defaulting to `CRAFTING`.
+
 After the preflight, the user is asked whether to stop, hand
 off to `ase-task-edit`, or hand off to `ase-task-implement`,
 unless `--next` pre-selects this choice.

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

@@ -126,7 +126,7 @@ Procedure
         (append extracted text to instruction).
         </if>
 
-    6.  <if condition="<task-content/> contains '⎈   Created:  <text/>'">
+    6.  <if condition="the frontmatter of <task-content/> carries a `Created: <text/>` key">
         Set <timestamp-created><text/></timestamp-created> (set
         timestamp-created to extracted text)
         </if>

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

@@ -78,6 +78,27 @@ Procedure
 
     2.  <if condition="<task-content/> is not empty">
         Treat <task-content/> as *verbatim* Markdown.
+
+        For the *rendering only*, drop the leading *frontmatter* block --
+        both `---` delimiters and all of their keys -- and instead place
+        the following column-aligned glyph lines *before* the
+        `#   TASK: <title/>` heading, separated from it by an empty line,
+        omitting the line of every key absent from the frontmatter. The
+        glyph lines *MUST* stay *above* the heading, exactly where the
+        frontmatter block sits in the plan file, and *MUST NOT* be moved
+        below it. This keeps the `---` delimiters from rendering as a
+        horizontal rule plus a *setext heading*. This rewrite is
+        *display-only* and *MUST NOT* change <task-content/> itself:
+
+        <format>
+        ◉   **Id:**         <task-id/>
+        ⎈   **Created:**    <timestamp-created/>
+        ⚙   **Modified:**   <timestamp-modified/>
+        ◐   **Status:**     <task-status/>
+        ⚑   **Properties:** <task-properties/>
+        ☯   **Kind:**       <task-kind/>
+        </format>
+
         *Render plan*: Only output the following <template/>. If
         <getopt-option-full/> is *not* `true`, <task-content/> is longer than
         90 lines, and a `##  IMPLEMENTATION DRAFT` section (from the
@@ -87,9 +108,9 @@ Procedure
         Use the following <template/>:
 
         <template>
-        <ase-tpl-head title="TASK"/>
+        <ase-tpl-head title="TASK" subtitle="<task-id/>"/>
         <task-content/>
-        <ase-tpl-foot title="TASK"/>
+        <ase-tpl-foot title="TASK" subtitle="<task-id/>"/>
         </template>
         </if>