@rse/ase 0.0.56 → 0.0.58

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

@@ -0,0 +1,84 @@
+
+##  NAME
+
+`ase-task-edit` - Iteratively Edit a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-edit`
+    [`--help`|`-h`]
+    [`--plan`|`-p` *option*]
+    [`--dry`|`-d`]
+    [`--next`|`-n` *option*]
+    [*id* | *id*: *instruction* | *instruction*]
+
+##  DESCRIPTION
+
+The `ase-task-edit` skill establishes and refines a *task plan* purely
+through a *chat-driven loop*. The user steers each round via an
+interactive dialog that offers continued refinement, finalization, or
+hand-off to implementation or preflight.
+
+The task plan is stored in `.ase/tasks/`*id*`/plan.md` files of the
+project and can be alternatively edited with the "`ase task edit` *id*"
+command from outside the agent tool.
+
+##  OPTIONS
+
+`--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
+    with *instruction*), `REFINE` (refine the existing plan with
+    *instruction*), or `PRESERVE` (preserve the existing plan by
+    ignoring *instruction* and stopping skill processing).
+
+`--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
+    a plan, it strictly skips the entire verification phase (no
+    build, tests, linter, type-checker, or program execution) once
+    the source files have been modified.
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step (at the end
+    of this skill) with *option*, which can be either `none` (default,
+    interactive answer required), `DONE` (no next step), `IMPLEMENT`
+    (hand-over to `ase-task-implement`), `PREFLIGHT` (hand-over to
+    `ase-task-preflight`), or `REFINE` (refine the plan with subsequent
+    instruction).
+
+##  ARGUMENTS
+
+*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.
+
+##  EXAMPLES
+
+Edit the current task:
+
+```text
+❯ /ase-task-edit
+```
+
+Create a new task under id `hello`:
+
+```text
+❯ /ase-task-delete hello
+❯ /ase-task-edit hello: new "ase hello" CLI command which prints
+  a nice "Hello World!" to the terminal in color blue.
+```
+
+Further refine the task under id `hello`:
+
+```text
+❯ /ase-task-edit hello: change the color to red.
+```
+
+##  SEE ALSO
+
+`ase-task-reboot`, `ase-task-preflight`, `ase-task-implement`,
+`ase-task-view`, `ase-task-list`, `ase-task-rename`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-id
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [<id>]"
 description: >
     Get or set unique task id <id>.
     Use when user requests to work on a certain task
@@ -13,13 +13,14 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Task Configuration
-==================
-
 <skill name="ase-task-id">
 Configure Task Id
 </skill>
 
+<objective>
+*Get* or *set* the unique *task id* of the current session.
+</objective>
+
 1.  Determine request:
     <request>$ARGUMENTS</request>
 

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

@@ -0,0 +1,42 @@
+
+##  NAME
+
+`ase-task-id` - Configure Task Id
+
+##  SYNOPSIS
+
+`ase-task-id`
+    [`--help`|`-h`]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-id` skill gets or sets the unique *task id* for the
+current session. Without arguments, it reports the currently active
+task id. With an *id* argument, it switches the session to that
+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.
+
+##  EXAMPLES
+
+Show the current task id:
+
+```text
+❯ /ase-task-id
+```
+
+Switch to a specific task:
+
+```text
+❯ /ase-task-id hello
+```
+
+##  SEE ALSO
+
+`ase-task-list`, `ase-task-edit`, `ase-task-view`,
+`ase-task-rename`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-implement
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>] [<id>]"
 description: >
     Implement current or given task plan.
     Use when the user calls to "implement", "realize" or "apply" the
@@ -15,9 +15,6 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Implement a Task Plan
-=====================
-
 <skill name="ase-task-implement">
 Implement a Task Plan
 </skill>
@@ -28,13 +25,10 @@ Implement a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *implementation* of changes.
-</role>
-
+<objective>
 *Implement* the task plan by modifying the *artifacts*
 with a corresponding, complete *change set*.
+</objective>
 
 Procedure
 ---------
@@ -135,6 +129,16 @@ explicitly requested by this procedure via outputs based on a <template/>!
         overrules the implementation draft in the `IMPLEMENTATION DRAFT`
         section of <content/>.
 
+        <if condition="<content/> does NOT contain a `## ※ VERIFICATION` section heading">
+        The task plan deliberately *omits* the `## ※ VERIFICATION`
+        section. You *MUST* therefore *strictly skip* the entire
+        verification phase after modifying the source files: do *NOT*
+        run any build, do *NOT* run any tests, do *NOT* run any linter,
+        do *NOT* run any type-checker, do *NOT* execute the modified
+        program, and do *NOT* otherwise verify the change set in any
+        way.
+        </if>
+
     2.  Only output the following <template/>:
 
         <template>

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

@@ -0,0 +1,63 @@
+
+##  NAME
+
+`ase-task-implement` - Implement a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-implement`
+    [`--help`|`-h`]
+    [`--next`|`-n` *option*]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-implement` skill performs the *final implementation*
+of a task plan by modifying the corresponding *artifacts* with a
+complete *change set*. The plan is loaded from
+`.ase/tasks/`*id*`/plan.md`, and any optional `IMPLEMENTATION DRAFT`
+section produced by `ase-task-preflight` is used as a hint — the
+plain plan content always overrules the draft.
+
+If the task plan deliberately *omits* the `※ VERIFICATION` section
+(as produced by `ase-code-craft`, `ase-code-refactor`,
+`ase-code-resolve`, or `ase-task-edit` when invoked with `--dry`),
+the entire verification phase is strictly skipped: no build, tests,
+linter, type-checker, or program execution is performed once the
+source files have been modified.
+
+After implementation, the user is asked whether to preserve or
+delete the task plan, unless `--next` pre-selects this choice.
+
+##  OPTIONS
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step with
+    *option*, which can be either `none` (default, interactive
+    answer required), `DONE` (preserve task plan and stop), or
+    `DELETE` (hand off to `ase-task-delete`).
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task whose plan should be
+    implemented. If omitted, the *current* task id is used.
+
+##  EXAMPLES
+
+Implement the current task plan:
+
+```text
+❯ /ase-task-implement
+```
+
+Implement a specific task and delete the plan when done:
+
+```text
+❯ /ase-task-implement --next DELETE hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-preflight`, `ase-task-reboot`,
+`ase-task-view`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-list
-argument-hint: "[-v|--verbose]"
+argument-hint: "[--help|-h] [--verbose|-v]"
 description: >
     List all available task ids.
     Use when user wants to see all tasks.
@@ -13,9 +13,6 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Task List
-=========
-
 <skill name="ase-task-list">
 List Task Plans
 </skill>
@@ -26,6 +23,10 @@ List Task Plans
     $ARGUMENTS
 </expand>
 
+<objective>
+*List* all available *task plans* of the current project.
+</objective>
+
 1.  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

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

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-task-list` - List Task Plans
+
+##  SYNOPSIS
+
+`ase-task-list`
+    [`--help`|`-h`]
+    [`--verbose`|`-v`]
+
+##  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.
+
+##  OPTIONS
+
+`--verbose`|`-v`:
+    Render an additional `Last Modified` column with the
+    `YYYY-MM-DD HH:MM` timestamp of each task plan.
+
+##  EXAMPLES
+
+List all task ids:
+
+```text
+❯ /ase-task-list
+```
+
+List all task ids together with their last-modified timestamps:
+
+```text
+❯ /ase-task-list --verbose
+```
+
+##  SEE ALSO
+
+`ase-task-id`, `ase-task-view`, `ase-task-edit`,
+`ase-task-rename`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-preflight
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>] [<id>]"
 description: >
     Preflight the implementation of current or given task plan.
     Use when the user calls to "preflight", "dry-run" or "test-drive"
@@ -15,9 +15,6 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Preflight a Task Plan
-=====================
-
 <skill name="ase-task-preflight">
 Preflight a Task Plan
 </skill>
@@ -28,13 +25,10 @@ Preflight a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *implementation* of changes.
-</role>
-
+<objective>
 *Preflight* the implementation of a task plan by creating a draft
 for a corresponding, *complete source code change set*.
+</objective>
 
 Procedure
 ---------

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

@@ -0,0 +1,58 @@
+
+##  NAME
+
+`ase-task-preflight` - Preflight a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-preflight`
+    [`--help`|`-h`]
+    [`--next`|`-n` *option*]
+    [*id*]
+
+##  DESCRIPTION
+
+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
+a `※ IMPLEMENTATION DRAFT` section (replacing any previous draft).
+No source files are modified.
+
+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.
+
+##  OPTIONS
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step with
+    *option*, which can be either `none` (default, interactive
+    answer required), `DONE` (stop), `EDIT` (hand off to
+    `ase-task-edit`), or `IMPLEMENT` (hand off to
+    `ase-task-implement`).
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task whose plan should be
+    preflighted. If omitted, the *current* task id is used.
+
+##  EXAMPLES
+
+Preflight the current task plan:
+
+```text
+❯ /ase-task-preflight
+```
+
+Preflight a specific task and hand off to implementation when done:
+
+```text
+❯ /ase-task-preflight --next IMPLEMENT hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-implement`, `ase-task-reboot`,
+`ase-task-view`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-reboot
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>] [<id>]"
 description: >
     Reboot the current or given task plan by re-creating it from scratch.
     Use when the user calls to "reboot", "recreate" or "refresh"
@@ -15,9 +15,6 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Reboot a Task Plan
-==================
-
 <skill name="ase-task-reboot">
 Reboot a Task Plan
 </skill>
@@ -28,13 +25,10 @@ Reboot a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *planning* of changes.
-</role>
-
+<objective>
 *Reboot* the task plan by crafting it from scratch,
 based on the existing *WHAT* and *WHY*.
+</objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
 

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

@@ -0,0 +1,55 @@
+
+##  NAME
+
+`ase-task-reboot` - Reboot a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-reboot`
+    [`--help`|`-h`]
+    [`--next`|`-n` *option*]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-reboot` skill re-creates an existing task plan *from
+scratch* by extracting the original `**WHAT**` and `**WHY**` sections
+(if present) from the current plan, using them as the new instruction,
+preserving the original creation timestamp, and writing a fresh plan
+content via `ase_task_save`.
+
+After the reboot, the user is asked whether to stop or hand off to
+`ase-task-edit`, unless `--next` pre-selects this choice.
+
+##  OPTIONS
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step with
+    *option*, which can be either `none` (default, interactive
+    answer required), `DONE` (stop), or `EDIT` (hand off to
+    `ase-task-edit`).
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task whose plan should be rebooted.
+    If omitted, the *current* task id is used.
+
+##  EXAMPLES
+
+Reboot the current task plan:
+
+```text
+❯ /ase-task-reboot
+```
+
+Reboot a specific task and hand off to editing:
+
+```text
+❯ /ase-task-reboot --next EDIT hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-preflight`, `ase-task-implement`,
+`ase-task-view`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-rename
-argument-hint: "[<old>] <new>"
+argument-hint: "[--help|-h] [<old>] <new>"
 description: >
     Rename the current or given task plan.
     Use when the user calls to "rename", "move" or "relabel" the
@@ -13,18 +13,13 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Rename a Task Plan
-==================
-
 <skill name="ase-task-rename">
 Rename a Task Plan
 </skill>
 
-<role>
-Your role is an experienced, *expert-level assistant*.
-</role>
-
+<objective>
 *Rename* the task plan.
+</objective>
 
 Procedure
 ---------

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

@@ -0,0 +1,44 @@
+
+##  NAME
+
+`ase-task-rename` - Rename a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-rename`
+    [`--help`|`-h`]
+    [*old*] *new*
+
+##  DESCRIPTION
+
+The `ase-task-rename` skill renames a *task plan* from *old* to
+*new* via the `ase_task_rename` MCP tool. If only one argument is
+given, it is treated as *new* and *old* defaults to the *current*
+task id. When the renamed task is the current task, the current
+task id is automatically switched to *new*.
+
+##  ARGUMENTS
+
+[*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.
+
+##  EXAMPLES
+
+Rename the current task:
+
+```text
+❯ /ase-task-rename hello-world
+```
+
+Rename a specific task:
+
+```text
+❯ /ase-task-rename old-id new-id
+```
+
+##  SEE ALSO
+
+`ase-task-list`, `ase-task-id`, `ase-task-edit`,
+`ase-task-view`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-view
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [<id>]"
 description: >
     View current or given task plan.
     Use when the user calls to "view", "show" or "see" the
@@ -13,17 +13,13 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-View a Task Plan
-================
-
 <skill name="ase-task-view">
 View a Task Plan
 </skill>
 
-<role>
-Your role is an experienced, *expert-level assistant*.
-</role>
+<objective>
 *View* the task plan.
+</objective>
 
 Procedure
 ---------

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

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-task-view` - View a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-view`
+    [`--help`|`-h`]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-view` skill renders the *task plan* identified by *id*
+in full, without truncation or summarization. The plan is loaded via
+the `ase_task_load` MCP tool and shown between `TASK-PLAN-BEGIN` and
+`TASK-PLAN-END` markers. If *id* is omitted, the *current* task id
+(inherited from the session context) is used.
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task plan to view. If omitted,
+    the current task id is used.
+
+##  EXAMPLES
+
+View the current task plan:
+
+```text
+❯ /ase-task-view
+```
+
+View a specific task plan:
+
+```text
+❯ /ase-task-view hello
+```
+
+##  SEE ALSO
+
+`ase-task-list`, `ase-task-edit`, `ase-task-id`,
+`ase-task-rename`, `ase-task-delete`.