---
name: Executing Plans
slug: executing-plans-4
category: Automation
description: Executing Plans loads a written implementation plan, reviews it for gaps, and carries out the tasks with checkpoints and verification. Use it when work is already planned and should be executed in a separate session.
github: "https://github.com/coco-research/coco/tree/main/skills/executing-plans"
language: HTML
stars: 218
forks: 11
install: "npx degit https://github.com/coco-research/coco/tree/main/skills/executing-plans ~/.claude/skills/executing-plans"
installs_to: ~/.claude/skills/executing-plans
source_path: skills/executing-plans/SKILL.md
collection_size: 25
category_size: 1860
collection_url: "https://dirskills.com/collections/coco-research/coco"
added: 2026-09-04T05:25:20.658Z
last_synced: 2026-09-04T05:25:20.658Z
canonical_url: "https://dirskills.com/skills/executing-plans-4"
---

# Executing Plans

Executing Plans loads a written implementation plan, reviews it for gaps, and carries out the tasks with checkpoints and verification. Use it when work is already planned and should be executed in a separate session.

**Install:**

```bash
npx degit https://github.com/coco-research/coco/tree/main/skills/executing-plans ~/.claude/skills/executing-plans
```

## README

# 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:** 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.

## The Process

### 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 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: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:**
- **superpowers:using-git-worktrees** - REQUIRED: Set up isolated workspace before starting
- **superpowers:writing-plans** - Creates the plan this skill executes
- **superpowers:finishing-a-development-branch** - Complete development after all tasks