$npx -y skills add obra/superpowers --skill executing-plansUse when you have a written implementation plan to execute in a separate session with review checkpoints
| 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. The quality of its work will be significantly higher if run on a platform with subagent support (Claude Code, Codex CLI, Codex App, and Copilot 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. Read plan file |
| 15 | 2. Review critically - identify any questions or concerns about the plan |
| 16 | 3. If concerns: Raise them with your human partner before starting |
| 17 | 4. If no concerns: Create todos for the plan items and proceed |
| 18 | |
| 19 | ### Step 2: Execute Tasks |
| 20 | |
| 21 | For each task: |
| 22 | 1. Mark as in_progress |
| 23 | 2. Follow each step exactly (plan has bite-sized steps) |
| 24 | 3. Run verifications as specified |
| 25 | 4. Mark as completed |
| 26 | |
| 27 | ### Step 3: Complete Development |
| 28 | |
| 29 | After all tasks complete and verified: |
| 30 | - Announce: "I'm using the finishing-a-development-branch skill to complete this work." |
| 31 | - **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch |
| 32 | - Follow that skill to verify tests, present options, execute choice |
| 33 | |
| 34 | ## When to Stop and Ask for Help |
| 35 | |
| 36 | **STOP executing immediately when:** |
| 37 | - Hit a blocker (missing dependency, test fails, instruction unclear) |
| 38 | - Plan has critical gaps preventing starting |
| 39 | - You don't understand an instruction |
| 40 | - Verification fails repeatedly |
| 41 | |
| 42 | **Ask for clarification rather than guessing.** |
| 43 | |
| 44 | ## When to Revisit Earlier Steps |
| 45 | |
| 46 | **Return to Review (Step 1) when:** |
| 47 | - Partner updates the plan based on your feedback |
| 48 | - Fundamental approach needs rethinking |
| 49 | |
| 50 | **Don't force through blockers** - stop and ask. |
| 51 | |
| 52 | ## Remember |
| 53 | - Review plan critically first |
| 54 | - Follow plan steps exactly |
| 55 | - Don't skip verifications |
| 56 | - Reference skills when plan says to |
| 57 | - Stop when blocked, don't guess |
| 58 | - Never start implementation on main/master branch without explicit user consent |
| 59 | |
| 60 | ## Integration |
| 61 | |
| 62 | **Required workflow skills:** |
| 63 | - **superpowers:using-git-worktrees** - Ensures isolated workspace (creates one or verifies existing) |
| 64 | - **superpowers:writing-plans** - Creates the plan this skill executes |
| 65 | - **superpowers:finishing-a-development-branch** - Complete development after all tasks |