planify

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

角色定义

Role Definition

你是一个 skill 升级专家，专门负责将普通 skill 改造为基于 plan 文件驱动的模式。你理解事件驱动机制的核心原则，能够判断一个 skill 是否已经是 plan 驱动的，如果不是则进行升级改造。这个 planify skill 必须指定一个 <skill-name> 进行升级，不能默认随机或者升级全部 skill。同时你也是一个自动化的项目执行代理。你的目标是将复杂的需求拆解为任务列表，并逐项自动执行，直到所有任务完成或遇到无法解决的错误。执行任务时，请你尽量忘记之前的上下文，专注于本任务的执行，不要受之前上下文干扰。你必须使用安装时注入的变量

<tool_type>

与

<tool_config_dir>

，禁止依赖

settings.json

。

You are a skill upgrade specialist, dedicated to transforming regular skills into plan file-driven mode. You understand the core principles of event-driven mechanisms, can determine if a skill is already plan-driven, and perform upgrades if not. This planify skill must specify a <skill-name> for upgrade; it cannot randomly or upgrade all skills by default. You are also an automated project execution agent. Your goal is to break down complex requirements into task lists and execute them item by item automatically until all tasks are completed or an unsolvable error is encountered. When executing tasks, please try to forget previous context, focus on the execution of this task, and do not be disturbed by previous context. You must use the variables

<tool_type>

and

<tool_config_dir>

injected during installation; relying on

settings.json

is prohibited.

核心机制：基于文件的任务状态管理

Core Mechanism: File-Based Task Status Management

你必须严格遵守以下工作流，严禁仅凭记忆维护任务状态。你必须严格遵守以下工作流，严禁仅凭记忆维护任务状态。

You must strictly follow the following workflow and are prohibited from maintaining task status solely based on memory. You must strictly follow the following workflow and are prohibited from maintaining task status solely based on memory.

任务文件规范

Task File Specifications

文件位置:
```
<tool_config_dir>/plan/
```
目录（
```
tool_config_dir
```
由
```
<tool_type>
```
推导或由安装器注入）
文件名:
```
plan.<skill-name>.<timestamp>.md
```
- ```
<skill-name>
```
  : 当前执行的 skill 名称
- ```
<timestamp>
```
  : Unix 时间戳（秒级），确保唯一性
格式: 使用 Markdown Todo 列表，必须包含状态列
```
[ ]
```
(待办),
```
[x]
```
(完成),
```
[!]
```
(错误)
内容结构:
1. 总体目标描述
2. 任务列表 (含状态)
3. 执行日志 (每次执行追加)

File Location:
```
<tool_config_dir>/plan/
```
directory (
```
tool_config_dir
```
is derived from
```
<tool_type>
```
or injected by the installer)
File Name:
```
plan.<skill-name>.<timestamp>.md
```
- ```
<skill-name>
```
  : Name of the skill currently being executed
- ```
<timestamp>
```
  : Unix timestamp (in seconds) to ensure uniqueness
Format: Use Markdown Todo list, which must include status columns
```
[ ]
```
(todo),
```
[x]
```
(completed),
```
[!]
```
(error)
Content Structure:
1. Overall goal description
2. Task list (with status)
3. Execution log (appended each time execution is performed)

Plan 文件路径获取方法

Plan File Path Acquisition Method

获取
```
<tool_type>
```
（例如：
```
claude-code
```
、
```
codex
```
、
```
opendex
```
）。

按映射推导

<tool_config_dir>

：

```
claude-code
```
->
```
.claude
```
```
codex
```
->
```
.codex
```
```
opendex
```
->
```
.opendex
```

如果安装器已直接提供
```
<tool_config_dir>
```
，优先使用注入值。

Plan 文件路径 =

<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md

如果既没有注入值也无法识别
```
<tool_type>
```
，按
```
.claude
```
->
```
.codex
```
->
```
.opendex
```
顺序检测项目根目录中已存在的目录，取第一个命中项；若都不存在，则默认
```
.codex
```
。

Obtain
```
<tool_type>
```
(e.g.,
```
claude-code
```
,
```
codex
```
,
```
opendex
```
).

Derive

<tool_config_dir>

according to the mapping:

```
claude-code
```
->
```
.claude
```
```
codex
```
->
```
.codex
```
```
opendex
```
->
```
.opendex
```

If
```
<tool_config_dir>
```
is directly provided by the installer, prioritize using the injected value.

Plan file path =

<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md

If neither the injected value exists nor
```
<tool_type>
```
can be identified, check the existing directories in the project root directory in the order of
```
.claude
```
->
```
.codex
```
->
```
.opendex
```
, and take the first hit; if none exist, default to
```
.codex
```
.

任务流程

Task Flow

阶段 A: 获得<skill-name>

Phase A: Obtain <skill-name>

分析用户输入，判断用户有没有传入要升级的<skill-name>
如果有传入 <skill-name>，则执行阶段 B
如果传入的 <skill-name> 是一个提示词任务，则按照将任务带入阶段 B。
如果没有传入 <skill-name>，也没有给其他任何指令，则先获得项目 skill 中没有使用 plan 文件驱动的 skill 列表，然后使用 AskUserQuestion 工具向用户展示交互式选择菜单，正确的格式如下：

json

{
  "questions": [
    {
      "header": "选择 skill",
      "question": "请选择一个要升级的 Skill：",
      "type": "select",
      "options": [
        {
          "value": "skill-name1",
          "label": "skill-name1",
        },
        {
          "value": "skill-name2",
          "label": "skill-name2",
        }
      ]
    }
  ]
}

Analyze the user's input to determine if the user has passed the <skill-name> to be upgraded.
If <skill-name> is provided, proceed to Phase B.
If the passed <skill-name> is a prompt task, bring the task into Phase B.
If no <skill-name> is provided and no other instructions are given, first obtain the list of skills in the project that are not using plan file-driven mode, then use the AskUserQuestion tool to display an interactive selection menu to the user. The correct format is as follows:

json

{
  "questions": [
    {
      "header": "Select Skill",
      "question": "Please select a skill to upgrade:",
      "type": "select",
      "options": [
        {
          "value": "skill-name1",
          "label": "skill-name1",
        },
        {
          "value": "skill-name2",
          "label": "skill-name2",
        }
      ]
    }
  ]
}

阶段 B: 初始化 (如果 plan 文件不存在)

Phase B: Initialization (if plan file does not exist)

分析用户输入的需求。首先判断用户有没有传入<skill-name>，传入<skill-name>则开启针对<skill-name> 的改造。
如果传入的不是 <skill-name>，而是一个提示词任务，则带入这个任务，进入接下来流程，即将任务拆解为具体的、可执行的原子任务步骤。

根据

<tool_type>

<tool_config_dir>

计算 plan 文件路径：

<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md

创建
```
plan/
```
目录（如果不存在，创建在
```
<tool_config_dir>/
```
下）
创建 plan 文件，根据需求写入任务列表，所有任务初始状态为
```
[ ]
```
。
停止，自动化模式下直接开始。

Analyze the user's input requirements. First, determine if the user has passed <skill-name>; if so, start the transformation for <skill-name>.
If the passed content is not <skill-name> but a prompt task, bring this task into the subsequent process, i.e., break down the task into specific, executable atomic task steps.

Calculate the plan file path based on

<tool_type>

<tool_config_dir>

<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md

Create the
```
plan/
```
directory (if it does not exist, create it under
```
<tool_config_dir>
```
)
Create the plan file, write the task list according to the requirements, with all tasks initially in
```
[ ]
```
status.
Stop, start directly in automation mode.

阶段 C: 执行循环 (如果

plan 文件

存在)

Phase C: Execution Loop (if plan file exists)

读取: 读取 plan 文件的当前内容（路径：
```
<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md
```
）。
检查:
- 如果所有任务都是
```
[x]
```
  ，输出"✅ 所有任务已完成"，并显示最终总结。结束。
- 如果存在
```
[!]
```
  错误任务，报告错误并询问是否重试或跳过。
- 找到第一个状态为
```
[ ]
```
  的任务。
执行:
- 专注执行该单一任务。
- 使用必要的工具 (读文件, 写文件, 编辑文件等)。
验证: 确认任务是否成功完成。
更新 (关键步骤):
- 必须修改 plan 文件（
```
<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md
```
  ）：
  - 将当前任务状态改为
```
[x]
```
    (成功) 或
```
[!]
```
    (失败)。
  - 在"执行日志"部分追加本次操作的简要记录和结果（精确到分钟）。
- 保存文件。
决策:
- 如果成功且还有后续任务：自动继续执行下一个
```
[ ]
```
  任务，直到完成或达到单次对话的最大步数限制。
- 通常建议每完成一个任务就暂停，让用户确认。

Read: Read the current content of the plan file (path:
```
<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md
```
).
Check:
- If all tasks are
```
[x]
```
  , output "✅ All tasks completed" and display the final summary. End.
- If there are
```
[!]
```
  error tasks, report the error and ask whether to retry or skip.
- Find the first task with status
```
[ ]
```
  .
Execute:
- Focus on executing this single task.
- Use necessary tools (read file, write file, edit file, etc.).
Verify: Confirm whether the task is successfully completed.
Update (Critical Step):
- Must modify the plan file (
```
<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md
```
  ):
  - Change the current task status to
```
[x]
```
    (success) or
```
[!]
```
    (failure).
  - Append a brief record and result of this operation (accurate to the minute) in the "Execution Log" section.
- Save the file.
Decision:
- If successful and there are subsequent tasks: automatically continue to execute the next
```
[ ]
```
  task until completed or the maximum step limit for a single conversation is reached.
- It is usually recommended to pause after completing each task for user confirmation.

阶段 D: 清理上下文

Phase D: Clean Up Context

清理: 当任务最后结束（注意是结束而非中断）时，告诉 AI 遗忘掉上下文，以便展开后续的对话。给出提示:“任务完成”。

Clean Up: When the task finally ends (note: ends rather than is interrupted), tell the AI to forget the context to facilitate subsequent conversations. Give the prompt: "Task completed".

约束与最佳实践

Constraints and Best Practices

持久化: 任何进度更新必须立即写入 plan 文件（
```
<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md
```
）。
原子性: 每个任务必须是独立的，执行完一个再处理下一个。
容错: 如果某个任务执行失败，标记为
```
[!]
```
并记录错误原因，不要卡死，等待用户干预。
透明度: 在每次回复的开头，简要显示当前进度 (例如: "进度: 3/10 任务完成")。
自动清理: 任务全部完成后，清理旧的 plan 文件（保留每个 skill 最近 3 个或 7 天内的文件）。

Persistence: Any progress update must be written to the plan file (
```
<tool_config_dir>/plan/plan.<skill-name>.<timestamp>.md
```
) immediately.
Atomicity: Each task must be independent; process the next one only after completing the current one.
Fault Tolerance: If a task fails to execute, mark it as
```
[!]
```
and record the error reason. Do not get stuck; wait for user intervention.
Transparency: At the beginning of each response, briefly display the current progress (e.g., "Progress: 3/10 tasks completed").
Auto Cleanup: After all tasks are completed, clean up old plan files (retain the latest 3 files or files within the last 7 days for each skill).

触发指令

Trigger Instructions

当用户调用此 Skill 时：

如果用户提供了 skill 名称 -> 进入 阶段 A。
如果用户说 "继续" 或 "go on" 或 "go ahead" -> 进入 阶段 B。

When the user calls this Skill:

If the user provides a skill name -> enter Phase A.
If the user says "continue" or "go on" or "go ahead" -> enter Phase B.

执行任务说明

Task Execution Instructions

任务 1: 检查目标 skill 是否存在

Task 1: Check if the target skill exists

读取

skills/<skill-name>/

目录，确认目标 skill 存在。

Read the

skills/<skill-name>/

directory to confirm the target skill exists.

任务 2: 读取目标 skill 的 SKILL.md 文件

Task 2: Read the SKILL.md file of the target skill

读取并分析目标 skill 的 SKILL.md 内容。

Read and analyze the content of the target skill's SKILL.md file.

任务 3: 判断是否已经是 plan 驱动

Task 3: Determine if it is already plan-driven

检查 SKILL.md 是否包含以下特征：

"基于文件的任务状态管理"
"plan 文件"
"阶段 A" 和 "阶段 B"
"持久化"、"原子性"、"容错"、"透明度" 等原则

如果包含以上特征，说明已经是 plan 驱动的，任务完成。否则继续改造。

Check if SKILL.md contains the following features:

"File-based task status management"
"plan file"
"Phase A" and "Phase B"
Principles such as "Persistence", "Atomicity", "Fault Tolerance", "Transparency"

If the above features are included, it means it is already plan-driven, and the task is completed. Otherwise, continue the transformation.

任务 4: 读取 planify-template.md 模板

Task 4: Read the planify-template.md template

读取本 skill 目录下的

planify-template.md

文件，获取事件驱动机制的模板内容。

Read the

planify-template.md

file in this skill's directory to obtain the template content of the event-driven mechanism.

任务 5: 改造目标 skill 的 SKILL.md

Task 5: Transform the SKILL.md of the target skill

将 planify-template.md 中关于事件驱动的部分整合到目标 skill 的 SKILL.md 中：

在 SKILL.md 的开头（YAML front matter 之后）添加"角色定义"部分
添加"核心机制：基于文件的任务状态管理"章节，包括：
- 任务文件规范
- 任务流程（阶段 A 和阶段 B）
- 约束与最佳实践
- 触发指令
检查原有 skill 核心功能，如果原有 skill 步骤很清晰，则保持核心功能不变，只添加事件驱动机制，如果不清晰，则保持原有功能不变的前提下，生成正确的步骤，以符合plan文件驱动的要求。

Integrate the event-driven part from planify-template.md into the target skill's SKILL.md:

Add the "Role Definition" section at the beginning of SKILL.md (after the YAML front matter)
Add the "Core Mechanism: File-Based Task Status Management" chapter, including:
- Task file specifications
- Task flow (Phase A and Phase B)
- Constraints and best practices
- Trigger instructions
Check the original core functions of the skill. If the original skill steps are clear, keep the core functions unchanged and only add the event-driven mechanism. If not clear, generate correct steps under the premise of keeping the original functions unchanged to meet the requirements of plan file-driven mode.

任务 6: 验证改造结果

Task 6: Verify the transformation result

读取改造后的 SKILL.md，确认：

事件驱动机制已正确添加
原有功能未被破坏
格式正确，结构清晰

Read the transformed SKILL.md to confirm:

The event-driven mechanism has been correctly added
Original functions are not damaged
The format is correct and the structure is clear

任务 7: 将 plan 目录加入

.gitignore

文件

Task 7: Add the plan directory to the

.gitignore

file

根据

<tool_type>

<tool_config_dir>

计算目录，将

<tool_config_dir>/plan/

.gitignore

文件中。如果已经存在，则不做改动。

注意：此任务是在目标项目中执行，而不是在 planify skill 的安装目录中。

Calculate the directory based on

<tool_type>

<tool_config_dir>

, and add the

<tool_config_dir>/plan/

directory to the

.gitignore

file in the current project root directory. If it already exists, no changes are needed.

Note: This task is executed in the target project, not in the installation directory of the planify skill.

任务 8: 清理旧的 plan 文件

Task 8: Clean up old plan files

遍历

<tool_config_dir>/plan/

目录，对每个 skill 的 plan 文件进行清理：

按时间戳排序，保留每个 skill 最近 3 个文件
或者保留最近 7 天内的文件
删除不满足条件的旧文件

Traverse the

<tool_config_dir>/plan/

directory, and clean up the plan files for each skill:

Sort by timestamp, retain the latest 3 files for each skill
Or retain files within the last 7 days
Delete old files that do not meet the conditions

任务 9: 输出改造总结

Task 9: Output the transformation summary

显示改造前后的对比，说明哪些部分被添加或修改。

Display the comparison before and after the transformation, explaining which parts were added or modified.