跳到正文
cccskills
免费在 GitHub 公开

ase-task-status

Get or set the lifecycle status of the current or given task plan. Use when the user wants to know or change the "status" or "state" of the "task" or "plan", e.g. to "close", "shelve", "cancel", or "re-open" it.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

  • SKILL.md4.8 KB
  • help.md2.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

<purpose name="ase-task-status"> Configure Task Status </purpose> <expand name="getopt" arg1="ase-task-status"> $ARGUMENTS </expand> <objective> *Get* or *set* the lifecycle *status* of the task plan. </objective>

Procedure

  1. Determine Task and Status:

    1. Parse <arguments><getopt-arguments/></arguments> (with any leading and trailing whitespace stripped) into a whitespace-separated list of tokens. Inherit the always existing <ase-task-id/> from the current context. Set <id><ase-task-id/></id> and <status></status> (empty). Set <states/> to the states of the task lifecycle model <ase-project-task-lifecycle/> of the current project:

      • If <ase-project-task-lifecycle/> is solo (or absent): OPEN, SHELVED, CLOSED, and CANCELLED.

      • If <ase-project-task-lifecycle/> is team: PLANNING, SHELVED, IMPLEMENTING, STALLED, IMPLEMENTED, and CANCELLED.

      • If <ase-project-task-lifecycle/> is enterprise: DRAFTED, SHELVED, PLANNING, PLANNED, STALLED, IMPLEMENTING, IMPLEMENTED, DECLINED, QUALIFYING, QUALIFIED, DEFERRED, INTEGRATING, INTEGRATED, and CANCELLED.

      Do not output anything.

    2. <if condition="<arguments/> contains two tokens"> Set <id/> to the first token with a trailing `:` removed and <status/> to the second token. Do not output anything. </if>
    3. <if condition="<arguments/> contains exactly one token"> - If the token ends with `:`: Set <id/> to the token with the trailing `:` removed. - Else if the token, upper-cased, is one of <states/>: Set <status/> to the token. - Else: Set <id/> to the token.

      Do not output anything. </if>

    4. <if condition="<arguments/> contains more than two tokens"> Only output the following <template/> and then immediately *STOP* processing the entire current skill: <template> ⧉ **ASE**: ☻ skill: **ase-task-status**, ▶ ERROR: expected `[<id>:] [<status>]` arguments </template> </if>
    5. <if condition="<id/> 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: <template> ⧉ **ASE**: ☻ skill: **ase-task-status**, ▶ ERROR: invalid task id `<id/>` (expected `^[a-zA-Z0-9#][a-zA-Z0-9#_-]*$`) </template> </if>
  2. Perform Operation:

    1. <if condition="<status/> is empty"> Call the `ase_task_status(id: "<id/>")` tool of the `ase` MCP server to get the lifecycle status of the task plan and set <text/> to the `text` output field of this tool call. Do not output anything related to this MCP tool call.
      • If <text/> starts with ERROR: or WARNING:: Only output the following <template/>:

        <template> ⧉ **ASE**: ◉ task: **<id/>**, ▶ status: **<text/>** </template>
      • If <text/> starts NOT with ERROR: and NOT with WARNING:: Only output the following <template/>:

        <template> ⧉ **ASE**: ◉ task: **<id/>**, ◐ status: **<text/>** </template>
      </if>
    2. <if condition="<status/> is NOT empty"> Call the `ase_task_status(id: "<id/>", status: "<status/>")` tool of the `ase` MCP server to set the lifecycle status of the task plan and set <text/> to the `text` output field of this tool call. Do not output anything related to this MCP tool call.
      • If <text/> starts with ERROR:: Only output the following <template/>:

        <template> ⧉ **ASE**: ◉ task: **<id/>**, ▶ status: **<text/>** </template>
      • If <text/> starts NOT with ERROR:: Strip the leading OK: prefix from <text/> and only output the following <template/>:

        <template> ⧉ **ASE**: ◉ task: **<id/>**, ◐ status: **<status/>** (*updated*), ▶ <text/> </template>
      </if>

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Review software architecture, including package cohesion and inter-package coupling

中文简介正在准备中。当前显示原文说明。

rse/ase602026年10月19日 更新

Discover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.

中文简介正在准备中。当前显示原文说明。

rse/ase602026年10月19日 更新

Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.

中文简介正在准备中。当前显示原文说明。

rse/ase602026年10月19日 更新

Edit Source Code: Use when the user wants to "edit" the code base in one shot from a query or a bare analyzer issue id like "P1", fusing crafting, refactoring, and resolving with optional grilling, verification, looping, and Git worktree isolation.

中文简介正在准备中。当前显示原文说明。

rse/ase602026年10月19日 更新

Explains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"

中文简介正在准备中。当前显示原文说明。

rse/ase602026年10月19日 更新

Give insights into the source code.

中文简介正在准备中。当前显示原文说明。

rse/ase602026年10月19日 更新

查看 rse 的全部技能

报告此技能的问题