executing-plans
- 作者仓库星标 0
- 作者更新于 2026年8月13日 00:53
- 作者仓库 superpowers
Executing Plans
Overview
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Note: Tell your human partner that Superpowers works much better with access to subagents (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in ../using-superpowers/references/). If subagents are available, use superpowers:subagent-driven-development instead of this skill.
The Process
Step 1: Load and Review Plan
- Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one
- 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 todos for the plan items and proceed
Step 2: Execute Tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
Step 3: Complete Development
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
When to Stop and Ask for Help
STOP executing immediately when:
- Hit a blocker (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.
Remember
- Review plan critically first
- Follow plan steps exactly
- Don't skip verifications
- Reference skills when plan says to
- Stop when blocked, don't guess
- Never start implementation on main/master branch without explicit user consent
- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @obra · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 需简单配置
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。The Process
Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one Read plan file Review critically - identify any questions or concerns about the plan
For each task: Mark as inprogress Follow each step exactly (plan has bite-sized steps)
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
Return to Review (Step 1) when: Partner updates the plan based on your feedback Fundamental approach needs rethinking
# Executing Plans
## Overview
Load plan, review critically, execute all tasks, report when complete.
**Announce at start:** "I'm using the executing-plans skill to implement this plan."
**Note:** Tell your human partner that Superpowers works much better with access to subagents (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in `../using-superpowers/references/`). If subagents are available, use superpowers:subagent-driven-development instead of this skill.
## The Process
### Step 1: Load and Review Plan
1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one
2. Read plan file
3. Review critically - identify any questions or concerns about the plan
4. If concerns: Raise them with your human partner before starting
5. If no concerns: Create todos for the plan items and proceed
### Step 2: Execute Tasks
For each task:
1. Mark as in_progress
2. Follow each step exactly (plan has bite-sized steps)
3. Run verifications as specified
4. Mark as completed
### Step 3: Complete Development
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
## When to Stop and Ask for Help
**STOP executing immediately when:**
- Hit a blocker (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:**
…作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Overview → The Process → Step 1: Load and Review Plan → Step 2: Execute Tasks → Step 3: Complete Development → When to Stop and Ask for Help
要点 -> Announce at start · Note · REQUIRED SUB-SKILL · STOP executing immediately when · Ask for clarification rather than guessing. · Return to Review (Step 1) when · Don't force through blockers
文件/命令 -> ../using-superpowers/references/ · ../using-superpowers/references · main/master
内容 SHA-256 -> 9f68b13f111f
设计思路
executing-plans是「按 plan 执行」的执行器——配合writing-plans使用：plan 已经把任务拆成 bite-sized 步骤、规定了验证手段，本 skill 的工作就是按部就班把它跑完，没有自由发挥。先 critically review 整个 plan，有疑问当面提，没疑问才建 TodoWrite 开干。启动声明
作者特地要求开头先打一句：
让协作者知道你进了执行模式。同样收尾时进
finishing-a-development-branch也要明确声明。流程
Step 1：Load and Review Plan
Step 2：Execute Tasks 每个 task：
Step 3：Complete Development 全部完成且验证通过后：
finishing-a-development-branchskill 走收尾流程何时停下问人
何时回到 Step 1
重要纪律
配套（必读）
using-git-worktrees：保证隔离工作区writing-plans：上一步——产出 planfinishing-a-development-branch：下一步——开发收尾subagent-driven-development替代本 skill 跑出来质量更高适合谁
不适合
writing-plans