NEW Browse AI tools across categories — updated daily. See what's new →
Official ★ Featured Productivity

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Authorobra
Version1.0.0
LicenseMIT
Token count~618
UpdatedJun 4, 2026

Install

Quick install

via npx skills · works with 57+ agents
npx skills add https://github.com/obra/superpowers/tree/main/skills/executing-plans
Or pick agent:
npx skills add obra/superpowers --skill executing-plans --agent claude-code
npx skills add obra/superpowers --skill executing-plans --agent cursor
npx skills add obra/superpowers --skill executing-plans --agent codex
npx skills add obra/superpowers --skill executing-plans --agent opencode
npx skills add obra/superpowers --skill executing-plans --agent github-copilot
npx skills add obra/superpowers --skill executing-plans --agent windsurf
More install options

Shorthand — useful for multi-skill repos:

npx skills add obra/superpowers --skill executing-plans

Manual — clone the repo and drop the folder into your agent's skills directory:

git clone https://github.com/obra/superpowers.git
cp -r superpowers/skills/executing-plans ~/.claude/skills/
How to use: Once installed, ask your agent to "use the executing-plans skill" or describe what you want (e.g. "Use when you have a written implementation plan to execute in a separate session"). Requires Node.js 18+.

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 - Ensures isolated workspace (creates one or verifies existing)

  • superpowers:writing-plans - Creates the plan this skill executes

  • superpowers:finishing-a-development-branch - Complete development after all tasks

SKILL.md source

---
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:** 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** - Ensures isolated workspace (creates one or verifies existing)
- **superpowers:writing-plans** - Creates the plan this skill executes
- **superpowers:finishing-a-development-branch** - Complete development after all tasks

Related skills 6

tzst

★ Featured

Use when the user needs to create, extract, flatten, list, test, install, script, or troubleshoot `tzst` CLI workflows for `.tzst` or `.tar.zst` archives, including compression levels, streaming mode, extraction filters, conflict resolution, JSON output, or standalone binary setup, even if they describe the archive task without naming `tzst`.

xixu-me 152k
Productivity

xdrop

★ Featured

Use this skill when the user wants to send or fetch files through an Xdrop server from the terminal, asks to automate encrypted Xdrop share-link workflows, provides an Xdrop `/t/:transferId#k=...` link to download and decrypt locally, or needs Xdrop CLI flags such as `--quiet`, `--json`, `--expires-in`, `--output`, or `--api-url`, even if they do not explicitly mention the skill name.

xixu-me 152k
Productivity

develop-userscripts

★ Featured

Use when building, debugging, packaging, or publishing browser userscripts for Tampermonkey or ScriptCat, including GM APIs, metadata blocks, permission issues, @match/@grant/@connect setup, ScriptCat background or scheduled scripts, UserConfig blocks, or subscription workflows.

xixu-me 109k
Productivity

triage

★ Featured

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

mattpocock 108k
Productivity

browser-use

★ Featured

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.

browser-use 76k
Productivity

Typefully / typefully

★ Featured Official

Create, schedule, and publish social media content across X, LinkedIn, Threads, Bluesky, and Mastodon

Typefully 22
Marketing & Sales