executing-plans git:20260815.6743039A

Immutable. This exact content is served forever at /api/v1/blob/5cbef67251069a14.

---
name: executing-plans
description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
---

# Executing Plans

## Overview

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

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

**Note:** Superpowers-UML works much better with access to subagents, which Claude Code provides. Use superpowers-uml:subagent-driven-development instead of this skill unless your human partner specifically asked for inline execution.

**Astah design model:** This skill runs in a separate session. Do not run it alongside another session working on the same Astah project — Astah keeps one project open, shared by every session and agent, so two concurrent executions edit the same model with nothing coordinating them.

## The Process

### Step 1: Load and Review Plan
1. Ensure the work is isolated from main/master: use superpowers-uml:using-git-worktrees — it verifies existing isolation, and otherwise chooses between a worktree and an in-place feature branch
2. Read plan file
3. Review critically - identify any questions or concerns about the plan
4. If concerns: Raise them with your human partner before starting
5. If no concerns: Create todos for the plan items and proceed

### Step 2: Execute Tasks

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

### 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 superpowers-uml: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