executing-plans

---
name: executing-plans
description: Use when you have a written implementation plan to execute inline in the current session as the no-subagent fallback
---

# Executing Plans

## Overview

Load plan, review critically, execute all tasks, report when complete.

**Core principle:** Inline execution — run the whole plan, then report.

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

**Note:** This skill works much better with access to subagents. If subagents are available, prefer h-superpowers:subagent-driven-development (fresh subagent + two-stage review per task) instead of this skill.

## The Process

### Step 0: Set Up Workspace
Before starting: Use `h-superpowers:using-git-worktrees` to set up an isolated workspace via the native worktree tool (`EnterWorktree`). Teardown is deferred to `finishing-a-development-branch` (Step 3), which uses `ExitWorktree`.

### Step 1: Load and Review Plan
1. Read plan file
2. Review critically - identify any questions or concerns about the plan
3. If concerns: Raise them with your human partner before starting
4. If no concerns: Create TodoWrite and proceed

### Step 2: Execute All Tasks

For each task, in order:
1. Mark as in_progress in TodoWrite
2. Follow each step exactly (plan has bite-sized steps)
3. Run verifications as specified
4. Mark as completed

Do not pause for human checkpoints between tasks. Execute the full plan, then report. Stop only when blocked (see below).

### 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 h-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:**
- **h-superpowers:using-git-worktrees** - REQUIRED: Set up isolated workspace before starting (native `EnterWorktree`)
- **h-superpowers:writing-plans** - Creates the plan this skill executes
- **h-superpowers:finishing-a-development-branch** - Complete development after all tasks; handles worktree teardown via `ExitWorktree`