Back to Details

gsdl-execute-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Manage Task List

任务列表管理

Guides implementation of task lists with structured completion tracking. This skill enforces a disciplined, step-by-step approach to working through tasks generated from PRDs.
指导任务列表的实施并进行结构化完成跟踪。该技能采用严谨的分步方法来处理从PRD生成的任务。

Project Context

项目上下文

Task lists are located at 
.planning/[project-name]/tasks/tasks-[prd-name].md
. Implementation code lives at the workspace root (not inside 
.planning/
).
任务列表位于 
.planning/[project-name]/tasks/tasks-[prd-name].md
。实现代码存放在工作区根目录（不在 
.planning/
内部）。

Operating Modes

操作模式

Standard Mode (default)

标准模式（默认）

Work on ONE sub-task at a time. Do NOT start the next sub-task until the user explicitly approves. Stop after each sub-task and wait for "yes", "go", "next", etc.
一次只处理一个子任务。在用户明确批准之前，不要开始下一个子任务。完成每个子任务后暂停，等待用户回复“yes”、“go”、“next”等指令。

Batch Mode (GSD orchestrator only)

批量模式（仅GSD编排器可用）

If your instructions say "BATCH MODE", complete all sub-tasks under your assigned parent task without pausing for approval between sub-tasks. Apply the full completion protocol (mark 
[x]
, update task file) after each sub-task, then immediately continue to the next. When the entire parent task is 
[x]
, follow the Parent Task Completion protocol (including the git commit), then stop and return a summary — do not start any other parent task.
如果你的指令中包含 “BATCH MODE”，则完成分配给你的父任务下的所有子任务，子任务之间无需暂停等待批准。完成每个子任务后应用完整的完成协议（标记 
[x]
、更新任务文件），然后立即继续下一个子任务。当整个父任务标记为 
[x]
后，遵循父任务完成协议（包括git提交），然后暂停并返回总结——不要开始任何其他父任务。

Completion Protocol

完成协议

Follow this protocol strictly when completing tasks:
完成任务时必须严格遵循以下协议：

When You Finish a Sub-Task

完成子任务时

  1. Mark the sub-task as completed: Change 
    [ ]
    to 
    [x]
    immediately
  2. Update the task list file: Save the changes to the task list
  3. Check parent task: If ALL subtasks under a parent are now 
    [x]
    , mark the parent as 
    [x]
    too, then follow the Parent Task Completion protocol below
  4. Pause (Standard Mode only): Stop and wait for user approval before starting the next sub-task. In Batch Mode, skip this step and continue immediately.
  1. 标记子任务为已完成：立即将 
    [ ]
    改为 
    [x]
  2. 更新任务列表文件：保存对任务列表的更改
  3. 检查父任务：如果父任务下的所有子任务都已标记为 
    [x]
    ，则也将父任务标记为 
    [x]
    ，然后遵循下方的父任务完成协议
  4. 暂停（仅标准模式）：在开始下一个子任务前等待用户批准。批量模式下跳过此步骤，立即继续。

When You Complete a Parent Task

完成父任务时

Once all sub-tasks under a parent are 
[x]
and the parent itself is marked 
[x]
:
  1. Stage all changes: 
    git add -A
  2. Commit with a descriptive message:
bash
git commit -m "$(cat <<'EOF'
[N.0] [Parent Task Title]

[2–4 bullet points summarising what was implemented, one per sub-task or logical group]
EOF
)"
Example:
bash
git commit -m "$(cat <<'EOF'
1.0 Set up authentication module

- Created auth directory structure and base config
- Installed and configured JWT dependencies
- Added environment variable definitions for secrets
EOF
)"
  1. Then pause for user approval (Standard Mode) or continue to the next parent task (Batch Mode).
当父任务下的所有子任务都已标记为 
[x]
，且父任务本身也标记为 
[x]
后：
  1. 暂存所有更改：
    git add -A
  2. 使用描述性信息提交：
bash
git commit -m "$(cat <<'EOF'
[N.0] [Parent Task Title]

[2–4 bullet points summarising what was implemented, one per sub-task or logical group]
EOF
)"
示例：
bash
git commit -m "$(cat <<'EOF'
1.0 Set up authentication module

- Created auth directory structure and base config
- Installed and configured JWT dependencies
- Added environment variable definitions for secrets
EOF
)"
  1. 然后暂停等待用户批准（标准模式）或继续下一个父任务（批量模式）。

Example Workflow

示例工作流

markdown
Before:
- [ ] 1.0 Parent Task
  - [x] 1.1 First sub-task (completed earlier)
  - [ ] 1.2 Second sub-task (just finished)
  - [ ] 1.3 Third sub-task (not started)

After (when 1.2 is complete):
- [ ] 1.0 Parent Task
  - [x] 1.1 First sub-task
  - [x] 1.2 Second sub-task
  - [ ] 1.3 Third sub-task (next up)

After (when 1.3 is complete and parent is done):
- [x] 1.0 Parent Task
  - [x] 1.1 First sub-task
  - [x] 1.2 Second sub-task
  - [x] 1.3 Third sub-task
markdown
之前：
- [ ] 1.0 父任务
  - [x] 1.1 第一个子任务（已提前完成）
  - [ ] 1.2 第二个子任务（刚完成）
  - [ ] 1.3 第三个子任务（未开始）

之后（完成1.2后）：
- [ ] 1.0 父任务
  - [x] 1.1 第一个子任务
  - [x] 1.2 第二个子任务
  - [ ] 1.3 第三个子任务（下一个待处理）

之后（完成1.3且父任务完成后）：
- [x] 1.0 父任务
  - [x] 1.1 第一个子任务
  - [x] 1.2 第二个子任务
  - [x] 1.3 第三个子任务

Task List Maintenance

任务列表维护

Update as You Work

工作时更新

  1. Mark completed items: Update 
    [x]
    for each finished task/sub-task
  2. Add new tasks: If you discover additional work needed, add new tasks to the list
  3. Keep files current: Maintain the "Relevant Files" section with accurate descriptions
  1. 标记已完成项：为每个已完成的任务/子任务更新为 
    [x]
  2. 添加新任务：如果发现需要额外工作，在列表中添加新任务
  3. 保持文件最新：维护“相关文件”部分，确保描述准确

Relevant Files Section

相关文件部分

The "Relevant Files" section should be kept up to date:
  • List every file created or modified (implementation files at workspace root, planning files under 
    .planning/
    )
  • Use full paths relative to workspace root (e.g., 
    src/file.ts
    for code, 
    .planning/[project-name]/tasks/tasks-prd-name.md
    for planning)
  • Provide a one-line description of each file's purpose
  • Add new files as they are created during implementation
“相关文件”部分应保持最新：
  • 列出所有创建或修改的文件（工作区根目录的实现文件，
    .planning/
    下的规划文件）
  • 使用相对于工作区根目录的完整路径（例如，代码文件用 
    src/file.ts
    ，规划文件用 
    .planning/[project-name]/tasks/tasks-prd-name.md
    ）
  • 为每个文件提供一行用途说明
  • 在实施过程中创建新文件时及时添加

Implementation Process

实施流程

Before Starting Work

开始工作前

  1. Read the task list from disk: Read the task file directly from its path on disk — do not rely on any in-context version. The user may have edited the file (added tasks, reworded sub-tasks, reordered items) since the plan was generated. Always use the on-disk state as the source of truth.
  2. Identify the next sub-task: Find the first unchecked 
    [ ]
    sub-task
  3. Check for dependencies: Ensure previous tasks are completed
  4. Understand the goal: Make sure you understand what the sub-task requires
  1. 从磁盘读取任务列表：直接从磁盘路径读取任务文件——不要依赖上下文版本。自计划生成以来，用户可能已编辑过文件（添加任务、重写子任务、重新排序项）。始终以磁盘上的状态为真实来源。
  2. 确定下一个子任务：找到第一个未勾选的 
    [ ]
    子任务
  3. 检查依赖关系：确保之前的任务已完成
  4. 理解目标：确保你理解该子任务的要求

During Implementation

实施过程中

  1. Focus on current sub-task: Work only on the current sub-task
  2. Implement thoroughly: Write code, tests, and documentation as needed
  3. Test your work: Verify the implementation works correctly
  1. 专注于当前子任务：仅处理当前子任务
  2. 全面实施：按需编写代码、测试和文档
  3. 测试工作成果：验证实施是否正常工作

After Completing a Sub-Task

完成子任务后

  1. Update task list: Mark the sub-task as 
    [x]
  2. Check parent task: If all sub-tasks done, mark parent as 
    [x]
    , then follow the Parent Task Completion protocol (commit before proceeding)
  3. Update Relevant Files: Add any new files created
  4. Save the task list file: Persist the changes
  5. Report to user: Briefly describe what was completed
  6. Request permission: Ask "Ready to move to the next sub-task?" or similar
  7. Wait: Do not proceed until the user confirms
  1. 更新任务列表：将子任务标记为 
    [x]
  2. 检查父任务：如果所有子任务都已完成，将父任务标记为 
    [x]
    ，然后遵循父任务完成协议（继续前先提交）
  3. 更新相关文件：添加所有创建的新文件
  4. 保存任务列表文件：持久化更改
  5. 向用户汇报：简要描述已完成的内容
  6. 请求许可：询问“准备好进入下一个子任务了吗？”或类似问题
  7. 等待：在用户确认前不要继续

AI Instructions

AI指令

When working with task lists, you must:
  1. Regularly update the task list file after finishing any significant work
  2. Follow the completion protocol:
    • Mark each finished sub-task 
      [x]
    • Mark parent task 
      [x]
      once all its subtasks are 
      [x]
  3. Add newly discovered tasks if additional work is identified
  4. Keep "Relevant Files" accurate and up to date
  5. Check which sub-task is next before starting work
  6. Pause after each sub-task and wait for user approval
处理任务列表时，你必须：
  1. 完成重要工作后定期更新任务列表文件
  2. 遵循完成协议：
    • 为每个已完成的子任务标记 
      [x]
    • 当所有子任务都为 
      [x]
      时，将父任务标记为 
      [x]
  3. 如果发现额外工作，添加新发现的任务
  4. 保持“相关文件”准确且最新
  5. 开始工作前检查下一个子任务
  6. 完成每个子任务后暂停并等待用户批准

User Permission Phrases

用户许可短语

Accept these as permission to continue to the next sub-task:
  • "yes"
  • "y"
  • "go"
  • "continue"
  • "next"
  • "proceed"
  • "keep going"
Do NOT continue if the user:
  • Asks questions
  • Requests changes
  • Wants to review something
  • Says "wait", "hold on", "stop", etc.
将以下表述视为继续下一个子任务的许可：
  • "yes"
  • "y"
  • "go"
  • "continue"
  • "next"
  • "proceed"
  • "keep going"
如果用户有以下行为，不要继续：
  • 提出问题
  • 请求更改
  • 要求审查内容
  • 说“wait”、“hold on”、“stop”等

Handling Changes and Additions

处理更改和新增内容

Discovered Issues

发现问题

If you discover issues while implementing:
  1. Add a new task or sub-task to the list
  2. Inform the user about the addition
  3. Ask if they want to address it now or later
如果在实施过程中发现问题：
  1. 在列表中添加新任务或子任务
  2. 告知用户新增内容
  3. 询问用户是现在处理还是稍后处理

Task Modifications

任务修改

If the user requests changes to the task list:
  1. Update the task list as requested
  2. Confirm the changes with the user
  3. Resume from the current position
如果用户要求修改任务列表：
  1. 按要求更新任务列表
  2. 与用户确认更改内容
  3. 从当前位置恢复工作

Skipping Tasks

跳过任务

If the user wants to skip a task:
  1. Mark it with a note (e.g., 
    - [ ] 2.3 [SKIPPED] Original description
    )
  2. Continue to the next task
  3. Update the parent task status appropriately
如果用户希望跳过某个任务：
  1. 用注释标记（例如，
    - [ ] 2.3 [已跳过] 原始描述
    ）
  2. 继续下一个任务
  3. 相应更新父任务状态

Quality Focus

质量重点

This one-task-at-a-time approach ensures:
  • Thoroughness: Each task gets full attention
  • Quality: Work is reviewed before moving on
  • Alignment: User can course-correct at each step
  • Documentation: Progress is clearly tracked
  • Learning: Junior developers see proper implementation pace
这种一次处理一个任务的方法可确保：
  • 全面性：每个任务都得到充分关注
  • 质量：在进入下一步前对工作进行审查
  • 一致性：用户可在每个步骤进行方向修正
  • 文档化：进度跟踪清晰
  • 学习性：初级开发者可了解正确的实施节奏

Example Interaction

示例交互

AI: "I've completed sub-task 1.2: Create login endpoint. The endpoint is now functional with proper error handling. I've marked it as complete in the task list. Ready to move to sub-task 1.3: Implement credential validation?"

User: "yes"

AI: [Proceeds to work on sub-task 1.3]
AI：“我已完成子任务1.2：创建登录端点。该端点现已具备功能并带有完善的错误处理。我已在任务列表中将其标记为已完成。准备好进入子任务1.3：实现凭证验证了吗？”

用户：“yes”

AI：[开始处理子任务1.3]

File Location

文件位置

Task lists follow this structure:
  • Path: 
    .planning/[project-name]/tasks/tasks-[prd-name].md
  • Example: 
    .planning/my-auth-project/tasks/tasks-prd-user-authentication.md
Always work within the project's directory structure.
任务列表遵循以下结构：
  • 路径：
    .planning/[project-name]/tasks/tasks-[prd-name].md
  • 示例：
    .planning/my-auth-project/tasks/tasks-prd-user-authentication.md
始终在项目的目录结构内工作。