executing-plans
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseExecuting Plans
执行计划
Purpose
目的
Execute approved implementation plans in controlled batches with checkpoints, verification, and review gates.
分批次受控执行已批准的实施计划,配备检查点、验证和评审关口。
When to Use
适用场景
Use this skill when:
- A written implementation plan already exists
- Work must be executed with periodic review checkpoints
- Risk of regressions requires strict plan adherence and verification
当满足以下条件时使用此技能:
- 已有书面实施计划
- 工作执行需设置定期评审检查点
- 存在回归风险,需要严格遵守计划并进行验证
Progress Tracking
进度追踪
Display plan execution progress before each batch:
[████░░░░░░░░░░░░░░░░] 20% — Phase 1: Loading & Reviewing Plan
[████████░░░░░░░░░░░░] 40% — Phase 2: Executing Batch N
[████████████░░░░░░░░] 60% — Phase 3: Reporting & Verification
[████████████████░░░░] 80% — Phase 4: Awaiting Feedback
[████████████████████] 100% — Phase 5: Final Verification CompleteFor plans with many tasks, adapt the gauge to reflect actual task completion: .
X/Y tasks done (N%)每次批次执行前展示计划执行进度:
[████░░░░░░░░░░░░░░░░] 20% — Phase 1: Loading & Reviewing Plan
[████████░░░░░░░░░░░░] 40% — Phase 2: Executing Batch N
[████████████░░░░░░░░] 60% — Phase 3: Reporting & Verification
[████████████████░░░░] 80% — Phase 4: Awaiting Feedback
[████████████████████] 100% — Phase 5: Final Verification Complete对于包含大量任务的计划,调整进度条以反映实际任务完成情况:。
X/Y tasks done (N%)Workflow
工作流程
- Load and review plan critically
- Execute first batch of tasks
- Report results and verification output
- Pause for feedback and continue in batches
- Finish branch with final verification
- 加载并严格评审计划
- 执行第一批任务
- 汇报结果和验证输出
- 暂停等待反馈,分批次继续执行
- 完成分支开发并进行最终验证
Overview
概述
Load plan, review critically, execute tasks in batches, report for review between batches.
Core principle: Batch execution with checkpoints for architect review.
Announce at start: "I'm using the executing-plans skill to implement this plan."
加载计划、严格评审、分批次执行任务,批次之间提交报告供评审。
核心原则: 分批次执行,设置架构师评审检查点。
启动时声明: "I'm using the executing-plans skill to implement this plan."
The Process
流程
Step 1: Load and Review Plan
步骤1:加载并评审计划
- Read plan file
- Review critically - identify any questions or concerns about the plan
- If concerns: Raise them with your human partner before starting
- If no concerns: Create TodoWrite and proceed
- 读取计划文件
- 严格评审——识别计划中存在的任何疑问或问题
- 如有问题:在启动前向你的人类协作伙伴提出
- 如无问题:创建TodoWrite并继续
Step 2: Execute Batch
步骤2:执行批次
Default: First 3 tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
默认:前3个任务
对每个任务:
- 标记为in_progress
- 严格遵循每一步骤(计划包含拆分好的小步骤)
- 按要求运行验证
- 标记为completed
Step 3: Report
步骤3:汇报
When batch complete:
- Show what was implemented
- Show verification output
- Say: "Ready for feedback."
批次完成时:
- 展示已实现的内容
- 展示验证输出
- 提示:"Ready for feedback."
Step 4: Continue
步骤4:继续执行
Based on feedback:
- Apply changes if needed
- Execute next batch
- Repeat until complete
基于反馈:
- 如有需要则进行修改
- 执行下一批次
- 重复直到完成
Step 5: Complete Development
步骤5:完成开发
After all tasks complete and verified:
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
- Follow that skill to verify tests, present options, execute choice
所有任务完成并验证通过后:
- 声明:"I'm using the finishing-a-development-branch skill to complete this work."
- 必填子技能: 使用superpowers:finishing-a-development-branch
- 遵循该技能的要求验证测试、呈现选项、执行选择
When to Stop and Ask for Help
何时停止并寻求帮助
STOP executing immediately when:
- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
- Plan has critical gaps preventing starting
- You don't understand an instruction
- Verification fails repeatedly
Ask for clarification rather than guessing.
出现以下情况时立即停止执行:
- 批次执行中遇到阻塞(依赖缺失、测试失败、指令不清晰)
- 计划存在严重缺陷无法启动
- 你无法理解某条指令
- 验证反复失败
请寻求澄清而非自行猜测。
When to Revisit Earlier Steps
何时回溯到之前的步骤
Return to Review (Step 1) when:
- Partner updates the plan based on your feedback
- Fundamental approach needs rethinking
Don't force through blockers - stop and ask.
出现以下情况时返回评审环节(步骤1):
- 协作伙伴根据你的反馈更新了计划
- 基础方案需要重新考量
不要强行绕过阻塞——停下来询问。
Remember
注意事项
- Review plan critically first
- Follow plan steps exactly
- Don't skip verifications
- Reference skills when plan says to
- Between batches: just report and wait
- Stop when blocked, don't guess
- Never start implementation on main/master branch without explicit user consent
- 首先严格评审计划
- 严格遵循计划步骤
- 不要跳过验证环节
- 当计划要求时引用对应的技能
- 批次之间:仅需汇报并等待
- 遇到阻塞时停止,不要猜测
- 未经用户明确同意,永远不要在main/master分支上启动实施
Integration
集成
Required workflow skills:
- superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
- superpowers:writing-plans - Creates the plan this skill executes
- superpowers:finishing-a-development-branch - Complete development after all tasks
必填工作流技能:
- superpowers:using-git-worktrees - 必备:启动前搭建隔离工作区
- superpowers:writing-plans - 生成此技能执行的计划
- superpowers:finishing-a-development-branch - 所有任务完成后结束开发
Critical Rules
关键规则
- Stop immediately on blockers and ask for clarification.
- Do not skip verification commands defined in the plan.
- Do not continue to the next batch without reporting and waiting for feedback.
- 遇到阻塞立即停止并寻求澄清。
- 不要跳过计划中定义的验证命令。
- 未提交报告并等待反馈前,不要继续执行下一批次。
Error Handling
错误处理
| Error | Likely Cause | Action |
|---|---|---|
| Plan file not found | Path provided doesn't exist or file was moved | Ask user to confirm file path; list available plan files in |
| Ambiguous task description | Step in plan is unclear or underspecified | Stop and ask user for clarification before proceeding |
| Task depends on failed prerequisite | Earlier task failed or was skipped | Report the dependency failure; do not continue until resolved |
| Verification command fails | Tests or checks defined in plan are failing | Stop immediately, report full error output, wait for user instruction |
| Blocker encountered mid-execution | Unexpected state, conflicting files, or missing context | Pause, report the exact blocker, and ask user how to proceed |
| Batch completed with partial failures | Some tasks in batch failed | Report which succeeded and which failed; ask user whether to retry or skip |
| 错误 | 可能原因 | 处理措施 |
|---|---|---|
| 计划文件未找到 | 提供的路径不存在或文件已被移动 | 请用户确认文件路径;列出 |
| 任务描述模糊 | 计划中的步骤不清晰或定义不足 | 停止操作,先向用户寻求澄清再继续 |
| 任务依赖的前置条件失败 | 之前的任务失败或被跳过 | 汇报依赖失败问题;问题解决前不要继续 |
| 验证命令失败 | 计划中定义的测试或检查未通过 | 立即停止,汇报完整错误输出,等待用户指示 |
| 执行过程中遇到阻塞 | 意外状态、文件冲突或上下文缺失 | 暂停操作,汇报具体阻塞问题,询问用户如何处理 |
| 批次执行完成但存在部分失败 | 批次中的部分任务失败 | 汇报成功和失败的任务;询问用户是重试还是跳过 |
Example Usage
使用示例
- "Use executing-plans to implement ."
docs/plans/2026-02-20-api-hardening.md - "Use executing-plans to run the next 3 tasks and stop for review."
- "Use executing-plans to finish remaining tasks and report final checks."
- "Use executing-plans to implement ."
docs/plans/2026-02-20-api-hardening.md - "Use executing-plans to run the next 3 tasks and stop for review."
- "Use executing-plans to finish remaining tasks and report final checks."