SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsexecuting-plans

executing-plans

Coding & development

View repository

Updated 10-15 08:57

About this skill

Execute the Plan

Overview

Load the plan, review it critically, execute all tasks, and report when done.

Announce at the start: "I am using the executing-plans skill to implement this plan."

Note: Tell your human partner that Superpowers works much better with subagent support (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all count; see the platform-specific tool references under ../using-superpowers/references/ ). If subagents are available, use superpowers:subagent-driven-development instead of this skill.

Process

Step 1: Load and Review the Plan

  1. Ensure there is an isolated workspace: create one with superpowers:using-git-worktrees, or verify the existing one
  2. Read the plan file
  3. Review critically—identify any problems or concerns in the plan
  4. If there are concerns: raise them with your human partner before starting
  5. If there are no concerns: create TodoWrite and continue

When reviewing, focus on checking:

  • Are there missing dependencies between steps? (A depends on B, but B comes after A)
  • Are the verification conditions clear? ("confirm it works" doesn't count, "run npm test and all pass" does)
  • Are there implicit environment assumptions? (Node version, database connection, API Key)

Review examples:

计划文件：docs/plan.md
任务清单：5 个任务

审查发现：
- 任务 3（添加数据库迁移）应在任务 2（编写数据模型）之后，顺序正确 ✓
- 任务 4 的验证条件写的是"确认功能正常"→ 需澄清：具体跑什么测试？
- 计划未提及 Python 版本要求 → 需确认

向伙伴提出：
"计划整体可执行。有两个问题：(1) 任务 4 的验证条件不够具体，建议改为
'运行 pytest tests/test_api.py 全部通过'；(2) 需要确认 Python 版本要求。"

Step 2: Execute the Tasks

For each task:

  1. Mark as in progress — update TodoWrite
  2. Understand the goal — reread the task description, clarify the completion criteria
  3. Execute the implementation — strictly follow the plan steps (the plan already has small steps)
  4. Run verification — run tests or checks as required
  5. Commit changes — commit once per completed task, with the commit message referencing the task number
  6. Mark as complete — update TodoWrite

Rhythm for each task:

--- 任务 2/5：添加用户验证 ---
[标记进行中]

目标：为 /api/users 添加输入验证
完成标准：所有验证测试通过，无效输入返回 400

[实现]
- 添加 validateUser() 中间件
- 编写 3 个验证规则（email 格式、密码强度、用户名长度）

[验证]
$ npm test -- --grep "validation"
  ✓ 拒绝无效 email (12ms)
  ✓ 拒绝弱密码 (8ms)
  ✓ 拒绝过长用户名 (5ms)
  3 passing

[提交]
$ git add src/middleware/validate.js tests/validation.test.js
$ git commit -m "feat: 添加用户输入验证（任务 2/5）"

[标记完成]
--- 任务 2/5 完成 ---

Continuous self-check:

  • Keep paying attention during execution: is the overall direction still right? Have you deviated from the plan?
  • If you find a problem with earlier implementation, fix it first before continuing; don't keep going with the problem

Step 3: Complete Development

After all tasks are complete and verified:

  • Announce: "I am using the finishing-a-development-branch skill to complete this work."
  • Required sub-skill: use superpowers:finishing-a-development-branch
  • Follow that skill's guidance to verify tests, present options, and execute the choice

Completion report template:

## 执行报告

**计划：** docs/plan.md
**分支：** feature/user-validation
**任务：** 5/5 已完成

### 完成的任务
1. ✅ 初始化项目结构
2. ✅ 添加用户验证
3. ✅ 添加数据库迁移
4. ✅ 实现 API 端点
5. ✅ 添加集成测试

### 验证结果
- 单元测试：23/23 通过
- 集成测试：8/8 通过
- lint 检查：0 个警告

### 偏离计划的地方
- 任务 3：Redis 配置从 env 改为 config.yaml（经伙伴同意）

### 下一步
按 finishing-a-development-branch 技能处理合并/PR

When to Stop and Ask for Help

Stop execution immediately in the following situations:

  • You hit a blocker (missing dependency, failing tests, unclear instructions)
  • The plan has serious flaws that make it impossible to start
  • You don't understand an instruction
  • Verification repeatedly fails (the same test fails more than 2 times)

When unsure, ask—don't guess.

Common Exception Handling

🇨🇳 This section is incremental content of superpowers-zh and is not present in the upstream obra/superpowers. It expands on the three specific situations from the previous section, "Encountering a blocker (missing dependency, failing tests, unclear instructions)." Upstream steps 1–3 and all other sections are translated section by section and are not modified by this section.

Test failure:

  1. Read the error message and locate the cause of the failure
  2. Distinguish: is it an implementation bug? Or is the test itself problematic? Or is the plan description wrong?
  3. Implementation bug → fix it and rerun
  4. Test problem → fix the test and explain it to the partner
  5. Plan error → stop, report to the partner, and suggest a correction

Missing dependency:

任务 3 需要 Redis 连接，但计划中没有提及 Redis 配置。
→ 停止执行
→ 向伙伴报告："任务 3 需要 Redis，计划中未包含配置步骤。
   建议：在任务 3 前插入 '配置 Redis 连接' 步骤。"

Unclear instructions:

  • Do not guess intent, do not "reasonably infer"
  • List your understanding and confusion, and ask the partner to clarify
  • Wait for a reply before continuing

Commit granularity: Commit each task separately, and reference the task number in the commit message.

When to return to previous steps

Return to review (step 1) when:

  • The partner has updated the plan based on your feedback
  • The fundamental approach needs to be reconsidered

Do not force your way through blockers — stop and ask.

Notes

  • Review the plan critically first
  • Follow the plan steps strictly
  • Do not skip verification
  • Reference the corresponding skills when the plan requires it
  • Stop when encountering a blocker; do not guess
  • Never start implementation on the main/master branch without the user's explicit consent