plan-execution

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Plan Execution Skill

This skill auto-activates when the user references an existing plan or wants to continue working from one.

Trigger phrases:

"continue the plan"
"next task"
"run task 2.1"
"what's the plan status"
"mark task X done"
References to
```
plans/*.plan.md
```
files

For creating new plans: Use

/superplan <description>

command instead.

此Skill会在用户引用现有计划或想要继续执行计划时自动激活。

触发短语：

"continue the plan"
"next task"
"run task 2.1"
"what's the plan status"
"mark task X done"
引用
```
plans/*.plan.md
```
文件

创建新计划： 请改用

/superplan <description>

命令。

Core Behaviors

核心行为

When User Says "next task" or "continue the plan"

当用户说"next task"或"continue the plan"时

Execute the

/plan next

flow:

Find the active plan (
```
plans/*.plan.md
```
with status
```
in-progress
```
)
Parse for the first unchecked
```
[ ]
```
task whose dependencies are all
```
[x]
```
Show task details and ask for confirmation
Implement, verify, mark complete, commit

执行

/plan next

流程：

找到活跃计划（状态为
```
in-progress
```
的
```
plans/*.plan.md
```
文件）
解析出第一个未勾选
```
[ ]
```
且所有依赖项均已勾选
```
[x]
```
的任务
展示任务详情并请求确认
执行任务、验证、标记完成、提交

When User Says "run task X.Y"

当用户说"run task X.Y"时

Find the active plan
Locate the specific task by ID (e.g.,
```
2.1
```
)
Check dependencies are met
If dependencies unmet, warn: "Task 2.1 depends on 1.3 which is incomplete. Proceed anyway? (y/n)"
Implement, verify, mark complete, commit

找到活跃计划
通过ID定位特定任务（例如
```
2.1
```
）
检查依赖项是否已满足
若依赖项未满足，发出警告："Task 2.1 depends on 1.3 which is incomplete. Proceed anyway? (y/n)"
执行任务、验证、标记完成、提交

When User Says "what's the plan status"

当用户说"what's the plan status"时

Execute the

/plan status

flow — show progress table for all plans.

执行

/plan status

流程——展示所有计划的进度表。

When User Says "mark task X done"

当用户说"mark task X done"时

Find the task in the plan file
Update
```
[ ]
```
to
```
[x]
```
with completion date
Show updated progress

在计划文件中找到该任务
将
```
[ ]
```
更新为
```
[x]
```
并添加完成日期
展示更新后的进度

Plan File Parsing

计划文件解析

Reading a Plan

读取计划

Plans follow this structure:

```
# Plan: <title>
```
— main heading
```
| Status | <value> |
```
— in metadata table
```
## Milestone N: <name>
```
— milestone headings
```
### N.M [ ] <title>
```
— pending task

### N.M [x] <title> *(completed YYYY-MM-DD)*

— completed task

计划遵循以下结构：

```
# Plan: <title>
```
—— 主标题
```
| Status | <value> |
```
—— 元数据表中的状态字段
```
## Milestone N: <name>
```
—— 里程碑标题
```
### N.M [ ] <title>
```
—— 待完成任务

### N.M [x] <title> *(completed YYYY-MM-DD)*

—— 已完成任务

Finding Dependencies

查找依赖项

Each task has a

**Dependencies:**

field:

```
None
```
— can run immediately
```
1.1
```
— depends on task 1.1
```
1.1, 1.2
```
— depends on both tasks 1.1 and 1.2
```
Milestone 1
```
— depends on all tasks in milestone 1

A dependency is met when the referenced task(s) have

[x]

每个任务都有

**Dependencies:**

字段：

```
None
```
—— 可立即执行
```
1.1
```
—— 依赖任务1.1
```
1.1, 1.2
```
—— 同时依赖任务1.1和1.2
```
Milestone 1
```
—— 依赖里程碑1中的所有任务

当引用的任务（或多个任务）标记为

[x]

时，依赖项即满足。

Updating Task Status

更新任务状态

When marking a task complete, replace:

undefined

标记任务完成时，将：

undefined

2.1 [ ] Add API endpoint

with:

替换为：

2.1 [x] Add API endpoint (completed 2026-03-21)

undefined

undefined

Updating Plan Status

更新计划状态

When first task starts: change

| Status | draft |

| Status | in-progress |

When all tasks complete: change to
```
| Status | complete |
```

当首个任务开始时：将

| Status | draft |

改为

| Status | in-progress |

当所有任务完成时：改为
```
| Status | complete |
```

Task Execution Flow

任务执行流程

When implementing a task from the plan:

当执行计划中的任务时：

1. Read Full Context

1. 读取完整上下文

Read the entire plan file (not just the current task)
Understand what was built before (completed tasks)
Understand what comes next (future tasks)
Check architecture decisions section for relevant context

读取整个计划文件（不只是当前任务）
了解之前已完成的工作（已完成任务）
了解后续任务（未来任务）
查看架构决策部分获取相关上下文

2. Implement

2. 执行任务

Follow the task's What specification
Modify only the Files listed (unless the task clearly requires additional files)
Follow existing codebase patterns and style guides

遵循任务的What规范
仅修改列出的Files（除非任务明确要求修改其他文件）
遵循现有代码库的模式和风格指南

3. Verify (Acceptance Gate — mandatory)

3. 验证（验收关卡——必填）

Go through each bullet in the task's Acceptance criteria one by one and explicitly confirm it passes:

Run the exact commands or checks described
For UI changes: use browser automation, take screenshots
For backend changes: make API calls, check database

If any criterion fails:

Fix the issue and re-verify all criteria (retry 1)
If still failing, fix again and re-verify (retry 2)
After 2 retries still failing: stop, do NOT mark
[x]
, and report to the user exactly which criterion failed and what you observed. Do not guess further.

Only proceed to the next step when all acceptance criteria pass.

逐一检查任务Acceptance标准中的每一项，并明确确认其通过：

运行指定的命令或检查项
对于UI变更：使用浏览器自动化工具，截取屏幕截图
对于后端变更：调用API，检查数据库

若任何标准未通过：

修复问题并重新验证所有标准（重试1次）
若仍未通过，再次修复并重新验证（重试2次）
2次重试后仍未通过：停止操作，不要标记
[x]
，并向用户准确报告哪项标准未通过以及你的观察结果。请勿进一步猜测。

只有当所有验收标准都通过时，才能进入下一步。

4. Run Code Quality Checks

4. 运行代码质量检查

Run whatever code quality tooling the project provides (linting, type checking, tests)
If the project has a dedicated code-checks command or script, use it

运行项目提供的代码质量工具（代码检查、类型检查、测试）
若项目有专门的代码检查命令或脚本，请使用它

5. Update Plan

5. 更新计划

Mark task
```
[x]
```
with completion date
Update plan status if needed
Add notes to Architecture Decisions if you learned something important

将任务标记为
```
[x]
```
并添加完成日期
必要时更新计划状态
若学到重要内容，在架构决策部分添加注释

6. Commit

6. 提交

Create a commit with message format:

Plan <N.M>: <Task Title>

Include both the code changes AND the plan file update in the same commit.

创建提交信息，格式如下：

Plan <N.M>: <Task Title>

将代码变更和计划文件更新包含在同一个提交中。

7. Report Progress

7. 报告进度

Show:

What was completed
Current progress (X/Y tasks, percentage)
What's next (next executable task)

展示：

已完成的内容
当前进度（已完成任务数/总任务数，百分比）
下一步任务（下一个可执行的任务）

Multi-Agent Execution

多Agent执行（Multi-Agent Execution）

For tasks that have independent subtasks (e.g., frontend + backend work), use parallel agents:

Task 2.1: Add user settings page
+-- Agent 1 (backend-specialist): Create API endpoint
+-- Agent 2 (frontend-specialist): Create React component
+-- Merge results, verify integration

Only parallelize when the task spec explicitly mentions independent frontend/backend work.

对于包含独立子任务的任务（例如前端+后端工作），使用并行Agent：

Task 2.1: Add user settings page
+-- Agent 1 (backend-specialist): Create API endpoint
+-- Agent 2 (frontend-specialist): Create React component
+-- Merge results, verify integration

仅当任务规范明确提到独立的前端/后端工作时，才进行并行处理。

Handling Plan Changes

处理计划变更

If during implementation you discover the plan needs changes:

Minor adjustment (file paths wrong, small scope change): Update the plan file directly and note it
Significant change (new task needed, task should be removed, reordering): Flag to user before changing
Architecture change: Update the Architecture Decisions section and discuss with user

Never silently deviate from the plan. If you need to do something different from what's specified, say so.

若在执行过程中发现计划需要变更：

微小调整（文件路径错误、小范围变更）：直接更新计划文件并添加注释
重大变更（需要新增任务、删除任务、重新排序）：在变更前告知用户
架构变更：更新架构决策部分并与用户讨论

切勿擅自偏离计划。若你需要执行与计划指定不同的操作，请告知用户。

Integration Points

集成点

The plan system works with whatever tools and commands the project provides:

What	How
Creating plans	`/plan <description>` command
Code quality	Run project-specific checks after each task
PR creation	Use project's PR workflow when milestone or full plan is complete
Self-review	Review changes before marking milestone complete
Ticket tracking	Plan metadata links to issue tracker ticket if applicable

计划系统可与项目提供的任何工具和命令配合使用：

事项	方式
创建计划	`/plan <description>` 命令
代码质量	每个任务完成后运行项目特定的检查
创建PR	当里程碑或整个计划完成时，使用项目的PR工作流
自我审查	在标记里程碑完成前审查变更
工单追踪	若适用，计划元数据链接到问题追踪系统的工单