---
name: executing-plans
description: Manual-only skill. Activate only after an explicit user request for superpowers-lite:executing-plans.
---

# Executing Plans

## Overview

Load plan, review critically, execute every task in the current branch in one run, perform one overall code review, then report when complete.

**Announce at start:** "I'm using the executing-plans skill to implement this plan."

**Note:** Tell your human partner that Superpowers Lite works better with access to subagents for larger plans. If subagents are available and the user explicitly wants that workflow, use superpowers-lite:subagent-driven-development instead of this skill.

## The Process

### Step 1: Confirm Branch, Load, and Review Plan
1. Confirm the current git branch is not `main` or `master` with `git branch --show-current`
2. If on `main` or `master`, stop and ask the user to switch or create a feature branch before implementation
3. Read plan file
4. Review critically - identify any questions or concerns about the plan
5. If concerns: Raise them with your human partner before starting
6. If no concerns: Create TodoWrite and proceed

### Step 2: Prepare a Single Run

Before implementation, organize the work for one uninterrupted run:

- Preserve the plan's task checklist for progress tracking
- Use phases only as an execution grouping aid, not as review checkpoints
- Do not create or switch to a worktree unless the user explicitly asks

### Step 3: Execute All Tasks

Complete every task from the plan in the current branch:

1. Mark the active task or phase as in_progress
2. Follow each included task step exactly (plan has bite-sized steps)
3. Run verifications specified by the included tasks
4. Mark tasks completed as they finish
5. Continue until all tasks are implemented and verified

Do not request code review between tasks or phases by default. Save review for Step 4.

### Step 4: Overall Code Review

After all tasks are implemented and verified:

1. Use superpowers-lite:requesting-code-review for one overall review of the full implementation
2. Fix Critical and Important findings
3. Re-run relevant verification
4. Re-review if substantial fixes were required

### Step 5: Complete Development

After all tasks complete, verified, and reviewed:
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- **REQUIRED SUB-SKILL:** Use superpowers-lite: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
- Do one overall code review after all tasks are done
- Reference skills when plan says to
- Stop when blocked, don't guess
- Work in the current branch by default; do not create or switch to a worktree unless the user explicitly asks
- Never start implementation on `main` or `master`; ask the user to switch or create a feature branch

## Integration

**Required workflow skills:**
- **superpowers-lite:writing-plans** - Creates the plan this skill executes
- **superpowers-lite:requesting-code-review** - Overall review after all tasks are complete
- **superpowers-lite:finishing-a-development-branch** - Complete development after all tasks

**Optional workflow skills:**
- **superpowers-lite:using-git-worktrees** - Use only when the user explicitly asks for an isolated workspace