executing-plans
- 信任分
- 88/100
- 兼容 Agent
- 1
- 领域
- 工程开发
- 兼容 Agent
- Claude Code
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @obra · 未声明 license
- 安装命令数
- 1 条
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
想读作者英文原文？ ↓ 滚到正文区切换 · 在 GitHub 查看 ↗
设计思路
executing-plans 是「按 plan 执行」的执行器——配合 writing-plans 使用：plan 已经把任务拆成 bite-sized 步骤、规定了验证手段，本 skill 的工作就是按部就班把它跑完，没有自由发挥。先 critically review 整个 plan，有疑问当面提，没疑问才建 TodoWrite 开干。
启动声明
作者特地要求开头先打一句：
"I'm using the executing-plans skill to implement this plan."
让协作者知道你进了执行模式。同样收尾时进 finishing-a-development-branch 也要明确声明。
流程
Step 1：Load and Review Plan
- 读 plan 文件。
- 批判性审查——把疑问 / 顾虑挑出来。
- 有疑问 → 先提给搭档；无疑问 → 建 TodoWrite，开始。
Step 2：Execute Tasks 每个 task：
- 标 in_progress
- 严格照步骤跑（plan 已经切碎到 bite-sized）
- 跑 plan 指定的验证
- 标 completed
Step 3：Complete Development 全部完成且验证通过后：
- 声明：「I'm using the finishing-a-development-branch skill to complete this work.」
- 必须调用
finishing-a-development-branchskill 走收尾流程
何时停下问人
- 撞到 blocker（依赖缺失、测试挂、指令含糊）
- plan 有关键缺口没法开始
- 你不理解某条指令
- 验证反复失败
Ask for clarification rather than guessing.——不要猜。
何时回到 Step 1
- 搭档根据你的反馈更新了 plan
- 根本路线需要重想
重要纪律
- 永远不在 main / master 上未经明确许可就开始实现
- 不要硬 push 过 blocker
- 验证不能跳
配套（必读）
using-git-worktrees：保证隔离工作区writing-plans：上一步——产出 planfinishing-a-development-branch：下一步——开发收尾- 平台支持 sub-agent（Claude Code、Codex）时优先用
subagent-driven-development替代本 skill 跑出来质量更高
适合谁
- 拿到一份审过的实施计划，要按部就班落地的工程师
- 复杂多步任务怕走神想用 todo list 收口的人
- 多人协作中负责执行不负责设计的角色
何时不该用
- 还没 plan——先去
writing-plans - 探索性原型——这套强制流程会束缚手脚
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. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use superpowers:subagent-driven-development instead of this skill.
The Process
Step 1: Load and Review Plan
- 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
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
Integration
Required workflow skills:
- superpowers:using-git-worktrees - Ensures isolated workspace (creates one or verifies existing)
- superpowers:writing-plans - Creates the plan this skill executes
- superpowers:finishing-a-development-branch - Complete development after all tasks