@rse/ase 0.0.30 → 0.0.31

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

@@ -0,0 +1,181 @@
+---
+name: ase-task-preflight
+argument-hint: "[<id>]"
+description: >
+    Preflight the implementation of current or given task plan.
+    Use when the user calls to "preflight", "dry-run" or "test-drive"
+    the "task", "plan", "spec", or "specification".
+user-invocable: true
+disable-model-invocation: false
+effort: xhigh
+---
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+
+Preflight a Task Plan
+=====================
+
+<skill name="ase-task-preflight">
+Preflight a Task Plan
+</skill>
+
+Your role is an experienced, *expert-level assistant*,
+specialized in the *implementation* of changes.
+
+*Preflight* the implementation of a task plan by creating a draft
+for a corresponding, *complete source code change set*.
+
+Procedure
+---------
+
+You *MUST* follow the following numbered items *strictly* *sequentially*!
+You *MUST* not skip any numbered item during processing!
+
+You *MUST* *NOT* output anything in this entire procedure, *except* when
+explicitly requested by this procedure via outputs based on a <template/>!
+
+1.  **Determine Task:**
+
+    1.  Set <instruction>$ARGUMENTS</instruction> initially.
+        Inherit the always existing <ase-task-id/> from the current context.
+        Inherit the always existing <ase-session-id/> from the current context.
+        Do not output anything.
+
+    2.  React on task id:
+
+        1.  <if condition="
+                <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+            ">
+            Set <ase-task-id><instruction/></ase-task-id> (set task
+            id to instruction) and <instruction></instruction> (set
+            instruction empty), call the `task_id(id: <ase-task-id/>,
+            session: <ase-session-id/>)` tool from the `ase` MCP
+            service to switch the task, and then only output the
+            following <template/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
+            </template>
+            </if>
+
+        2.  else <if condition="
+                <instruction/> has the format `<id/>: <text/>` where
+                <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$` and
+                <text/> is *empty*
+            ">
+            Set <instruction></instruction> (set instruction to empty)
+            and <ase-task-id><id/></ase-task-id> (set task id to
+            id) and call the `task_id(id: <ase-task-id/>, session:
+            <ase-session-id/>)` tool from the `ase` MCP service to
+            switch the task, and then only output the following
+            <template/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
+            </template>
+            </if>
+
+2.  **Determine Operation:**
+
+    1.  Call the `task_load(id: <ase-task-id/>)` tool of the `ase` MCP
+        service to load the current task plan content and set <content/> to
+        the `text` output field of the `task_load` tool call.
+
+        Calculate the number of words <words/> of <content/>.
+
+        Only output the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan loaded**
+        </template>
+
+    2.  If the <content/> is still empty, complain and tell the user to
+        use the `ase-code-resolve`, `ase-code-refactor`, `ase-code-craft`,
+        or `ase-task-edit` skills first to create a task plan.
+
+3.  **Create Implementation Draft:**
+
+    1.  Perform a *preflight* of the *implementation* of <content/> by creating a
+        draft for a corresponding, *complete artifact change set*
+        which *would* fully implement the task plan <content/>. Store
+        this artifact change set in *unified diff* format in <unified-diff/>.
+
+    2.  Append this artifact change set <unified-diff/> to the end
+        of the <content/> with the following <template/>. If a section
+        named `## ※ IMPLEMENTATION DRAFT:` already exists from a
+        previous run of this skill, *replace* this entire existing
+        section.
+
+        <template>
+
+        ## ※ IMPLEMENTATION DRAFT:
+
+        ```
+        <unified-diff/>
+        ```
+
+        </template>
+
+    3.  <if condition="<content/> contains '✎ modified:'">
+        Set update <timestamp-modified/> with the current time in
+        ISO-style format, which has to be determined by calling the
+        `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
+        MCP service and use the `text` field of its response. Update
+        <content/> with the new `✎ modified: **<timestamp-modified/>**`.
+        Do not output anything.
+        </if>
+
+    4.  Finally, call the `task_save(id: <ase-task-id/>,
+        text: <content/>)` of the `ase` MCP service to save the updated
+        task plan content. Calculate the number of words <words/> of
+        <content/>. Do not output anything related to this MCP tool call
+        except the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated**
+        </template>
+
+4.  **Decide Next Step:**
+
+    1.  *Ask user*: Let the *user interactively choose*
+        what to do as the next step.
+
+        <expand name="user-dialog>
+        Next Step: How would you like to proceed with the plan?
+        DONE: Stop processing.
+        EDIT: Hand processing off to editing.
+        IMPLEMENT: Hand processing off to implementation.
+        </expand>
+
+    2.  Check the tool <result/> and dispatch accordingly:
+
+        -   If <result/> is `DONE` or `CANCEL`:
+            Only output the following <template/> and then *STOP*.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- done**
+            </template>
+
+        -   If <result/> is `EDIT`:
+            Only output the following <template/> and then use the
+            `Skill` tool to invoke the `ase:ase-task-edit` skill
+            in order to *edit* the updated plan. Immediately stop
+            processing the current skill once the `Skill` tool was used.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to edit**
+            </template>
+
+        -   If <result/> is `IMPLEMENT`:
+            Only output the following <template/> and then use the
+            `Skill` tool to invoke the `ase:ase-task-implement` skill
+            in order to *implement* the updated plan. Immediately stop
+            processing the current skill once the `Skill` tool was used.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to implement**
+            </template>
+
+

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

@@ -0,0 +1,161 @@
+---
+name: ase-task-reboot
+argument-hint: "[<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"
+    the "task", "plan", "spec", or "specification".
+user-invocable: true
+disable-model-invocation: false
+effort: xhigh
+---
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
+
+Reboot a Task Plan
+==================
+
+<skill name="ase-task-reboot">
+Reboot a Task Plan
+</skill>
+
+Your role is an experienced, *expert-level assistant*,
+specialized in the *planning* of changes.
+
+*Reboot* the task plan by crafting it from scratch,
+based on the existing *WHAT* and *WHY*.
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
+
+Procedure
+---------
+
+You *MUST* follow the following numbered items *strictly* *sequentially*!
+You *MUST* not skip any numbered item during processing!
+
+You *MUST* *NOT* output anything in this entire procedure, *except* when
+explicitly requested by this procedure via outputs based on a <template/>!
+
+1.  **Determine Task:**
+
+    1.  Set <instruction>$ARGUMENTS</instruction> initially.
+        Inherit the always existing <ase-task-id/> from the current context.
+        Inherit the always existing <ase-session-id/> from the current context.
+        Do not output anything.
+
+    2.  React on task id:
+
+        <if condition="
+            <instruction/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
+        ">
+        Set <ase-task-id><instruction/></ase-task-id> (set task
+        id to instruction) and <instruction></instruction> (set
+        instruction empty), call the `task_id(id: <ase-task-id/>,
+        session: <ase-session-id/>)` tool from the `ase` MCP
+        service to switch the task, and then only output the
+        following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given**
+        </template>
+        </if>
+
+2.  **Determine Operation:**
+
+    1.  Call the `task_load(id: <ase-task-id/>)` tool of the `ase` MCP
+        service to load the current task plan content and set <content/> to
+        the `text` output field of the `task_load` tool call.
+
+        Calculate the number of words <words/> of <content/>.
+
+        Only output the following <template/>:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan loaded**
+        </template>
+
+    2.  <if condition="<content/> is empty">
+        Complain and tell the user to use the `ase-code-resolve`,
+        `ase-code-refactor`, `ase-code-craft`, or `ase-task-edit` skills
+        first to create a task plan. Then immediately stop processing
+        this skill.
+        </if>
+
+3.  **Reboot Task Plan:**
+
+    1.  Start with <instruction></instruction> (set instruction to empty).
+
+    2.  <if condition="<content/> contains neither '- **WHAT**:' nor '- **WHY**:'">
+        Set <instruction><content/></instruction> (set instruction to content).
+        </if>
+
+    3.  <if condition="<content/> contains '- **WHAT**: <text/>'">
+        Set <instruction><text/></instruction> (set instruction to extracted text).
+        </if>
+
+    4.  <if condition="<content/> contains '- **WHY**: <text/>'">
+        Set <instruction><instruction/>, BECAUSE <text/></instruction>
+        (append extracted text to instruction).
+        </if>
+
+    5.  <if condition="<content/> contains 'created: **<text/>**'">
+        Set <timestamp-created><text/></timestamp-created> (set
+        timestamp-created to extracted text)
+        </if>
+
+    6.  Create a new plan from scratch and store the result as
+        <content/> by closely following the defined plan format
+        <format/> and injecting into it all the information from
+        the <instruction/> and all decisions you derived from the
+        <instruction/>.
+
+    7.  Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+        `ase` MCP service and use the `text` field of its response for
+        <timestamp-modified/> information. Then insert the current
+        <ase-task-id/>, previous <timestamp-created/>, and refreshed
+        <timestamp-modified/> information and calculate the number of
+        words <words/> of <content/>.
+
+    8.  Call the `task_save(id: <ase-task-id/>,
+        text: <content/>)` of the `ase` MCP service to save the updated
+        task plan content. Do not output anything related to this MCP
+        call.
+
+    9.  Only output the following <template/> and continue processing:
+
+        <template>
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan rebooted**
+        ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ⇌ instruction: **<instruction/>**, ▶ status: **instruction given**
+        </template>
+
+4.  **Decide Next Step:**
+
+    1.  *Ask user*: Let the *user interactively choose*
+        what to do as the next step.
+
+        <expand name="user-dialog>
+        Next Step: How would you like to proceed with the plan?
+        DONE: Stop processing.
+        EDIT: Hand processing off to editing.
+        </expand>
+
+    2.  Check the tool <result/> and dispatch accordingly:
+
+        -   If <result/> is `DONE` or `CANCEL`:
+            Only output the following <template/> and then *STOP*.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- done**
+            </template>
+
+        -   If <result/> is `EDIT`:
+            Only output the following <template/> and then use the
+            `Skill` tool to invoke the `ase:ase-task-edit` skill
+            in order to *edit* the updated plan. Immediately stop
+            processing the current skill once the `Skill` tool was used.
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ✪ plan: **<words/>** words, ▶ status: **plan updated -- hand-off to edit**
+            </template>

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

@@ -0,0 +1,81 @@
+---
+name: ase-task-view
+argument-hint: "[<id>]"
+description: >
+    View current or given task plan.
+    Use when the user calls to "view", "show" or "see" the
+    "task", "plan", "spec", or "specification".
+user-invocable: true
+disable-model-invocation: false
+effort: low
+---
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+
+View a Task Plan
+================
+
+<skill name="ase-task-view">
+View a Task Plan
+</skill>
+
+Your role is an experienced, *expert-level assistant*.
+*View* the task plan.
+
+Procedure
+---------
+
+You *MUST* follow the following numbered items *strictly* *sequentially*!
+You *MUST* not skip any numbered item during processing!
+
+You *MUST* *NOT* output anything in this entire procedure, *except* when
+explicitly requested by this procedure via outputs based on a <template/>!
+
+1.  **Determine Task:**
+
+    1.  Set <id>$ARGUMENTS</id> initially.
+        Inherit the always existing <ase-task-id/> from the current context.
+        Do not output anything.
+
+    2.  <if condition="<id/> is empty">
+        Set <id><ase-task-id/></id>
+        Do not output anything.
+        </if>
+
+2.  **Perform Operation**:
+
+    1.  Call the `task_load(id: <id/>)` tool of the `ase` MCP
+        service to load the task plan content and set <text/> to the
+        `text` output field of this `task_load` tool call. Do not
+        output anything related to this MCP tool call.
+
+        -   If <text/> starts with `ERROR:` or `WARNING:`:
+            Set <content></content> (set content to empty).
+            Only output the following <template/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<id/>**, ▶ status: **<text/>**
+            </template>
+
+        -   If <text/> starts NOT with `ERROR:`:
+            Set <content><text/></content> (set content to text).
+            Calculate the number of words <words/> of <content/>.
+            Only output the following <template/>:
+
+            <template>
+            ⧉ **ASE**: ◉ task: **<id/>**, ✪ plan: **<words/>** words, ▶ status: **plan loaded**
+            </template>
+
+    2.  <if condition="<content/> is not empty">
+        *Render plan*: Only output the following <template/>, so the user
+        can read the plan and react to it. Do *not* truncate, summarize,
+        or partially show the plan -- always show the complete plan
+        <content/> here:.
+
+        <template>
+        ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(** `TASK-PLAN-BEGIN` **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
+        <content/>
+        ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(**  `TASK-PLAN-END`  **)**━━━━━━━━────────┈┈┈┈┈┈┈┈
+        </template>
+        </if>