1---
2name: executing-plans
3description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
4---
5 
6# Executing Plans
7 
8## Overview
9 
10Load plan, review critically, execute all tasks, report when complete.
11 
12**Announce at start:** "I'm using the executing-plans skill to implement this plan."
13 
14**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.
15 
16## The Process
17 
18### Step 1: Load and Review Plan
191. Read plan file
202. Review critically - identify any questions or concerns about the plan
213. If concerns: Raise them with your human partner before starting
224. If no concerns: Create TodoWrite and proceed
23 
24### Step 2: Execute Tasks
25 
26For each task:
271. Mark as in_progress
282. Follow each step exactly (plan has bite-sized steps)
293. Run verifications as specified
304. Mark as completed
31 
32### Step 3: Complete Development
33 
34After all tasks complete and verified:
35- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
36- **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch
37- Follow that skill to verify tests, present options, execute choice
38 
39## When to Stop and Ask for Help
40 
41**STOP executing immediately when:**
42- Hit a blocker (missing dependency, test fails, instruction unclear)
43- Plan has critical gaps preventing starting
44- You don't understand an instruction
45- Verification fails repeatedly
46 
47**Ask for clarification rather than guessing.**
48 
49## When to Revisit Earlier Steps
50 
51**Return to Review (Step 1) when:**
52- Partner updates the plan based on your feedback
53- Fundamental approach needs rethinking
54 
55**Don't force through blockers** - stop and ask.
56 
57## Remember
58- Review plan critically first
59- Follow plan steps exactly
60- Don't skip verifications
61- Reference skills when plan says to
62- Stop when blocked, don't guess
63- Never start implementation on main/master branch without explicit user consent
64 
65## Integration
66 
67**Required workflow skills:**
68- **superpowers:using-git-worktrees** - Ensures isolated workspace (creates one or verifies existing)
69- **superpowers:writing-plans** - Creates the plan this skill executes
70- **superpowers:finishing-a-development-branch** - Complete development after all tasks
71