executing-plans
byobra· 95 skills
Use when you have a written implementation plan to execute in a separate session with review checkpoints
How to install executing-plans?
obra/superpowers/executing-plans
$npx -y skills add obra/superpowers --skill executing-plansInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/obra/superpowers" --skill "obra/superpowers/executing-plans"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/obra/superpowers" that are relevant to the current task. Run `npx skills add "https://github.com/obra/superpowers"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | # Executing Plans |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Load plan, review critically, execute all tasks, report when complete. |
| 6 | |
| 7 | **Announce at start:** "I'm using the executing-plans skill to implement this plan." |
| 8 | |
| 9 | **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. |
| 10 | |
| 11 | ## The Process |
| 12 | |
| 13 | ### Step 1: Load and Review Plan |
| 14 | 1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one |
| 15 | 2. Read plan file |
| 16 | 3. Review critically - identify any questions or concerns about the plan |
| 17 | 4. If concerns: Raise them with your human partner before starting |
| 18 | 5. If no concerns: Create todos for the plan items and proceed |
| 19 | |
| 20 | ### Step 2: Execute Tasks |
| 21 | |
| 22 | For each task: |
| 23 | 1. Mark as in_progress |
| 24 | 2. Follow each step exactly (plan has bite-sized steps) |
| 25 | 3. Run verifications as specified |
| 26 | 4. Mark as completed |
| 27 | |
| 28 | ### Step 3: Complete Development |
| 29 | |
| 30 | After all tasks complete and verified: |
| 31 | - Announce: "I'm using the finishing-a-development-branch skill to complete this work." |
| 32 | - **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch |
| 33 | - Follow that skill to verify tests, present options, execute choice |
| 34 | |
| 35 | ## When to Stop and Ask for Help |
| 36 | |
| 37 | **STOP executing immediately when:** |
| 38 | - Hit a blocker (missing dependency, test fails, instruction unclear) |
| 39 | - Plan has critical gaps preventing starting |
| 40 | - You don't understand an instruction |
| 41 | - Verification fails repeatedly |
| 42 | |
| 43 | **Ask for clarification rather than guessing.** |
| 44 | |
| 45 | ## When to Revisit Earlier Steps |
| 46 | |
| 47 | **Return to Review (Step 1) when:** |
| 48 | - Partner updates the plan based on your feedback |
| 49 | - Fundamental approach needs rethinking |
| 50 | |
| 51 | **Don't force through blockers** - stop and ask. |
| 52 | |
| 53 | ## Remember |
| 54 | - Review plan critically first |
| 55 | - Follow plan steps exactly |
| 56 | - Don't skip verifications |
| 57 | - Reference skills when plan says to |
| 58 | - Stop when blocked, don't guess |
| 59 | - Never start implementation on main/master branch without explicit user consent |
Related
6 picksType
- grill-meA relentless interview to sharpen a plan or design.Jul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.Jul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更…Jul 2026
- lark-okr飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估Jul 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.Jul 2026
- grillingGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.Jul 2026
