Back to browse

obra/superpowers

executing-plans

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

69CollectingReads files
See how to use itView GitHub source
npx skills add https://github.com/obra/superpowers --skill "skills/executing-plans"

Quick start

Start using it in three steps

Install it or open the source, trigger it with a clear task, then follow the source workflow.

1

Install the Skill

npx skills add https://github.com/obra/superpowers --skill "skills/executing-plans"
2

Describe the task

Use executing-plans to help me with: [describe your task]. Before you begin, tell me what input you need, the steps you will follow, and the expected output.

3

Follow the workflow

5 key workflow steps, examples, and cautions are distilled below.

Continue to the workflow

Direct answers

Answers to review before you install

What is executing-plans?

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

Who should use executing-plans?

It is most relevant to product / startup, software development workflows. Confirm the original prerequisites before using it in production.

How do you install executing-plans?

SkillSignal detected this source-specific command: npx skills add https://github.com/obra/superpowers --skill "skills/executing-plans". Inspect the repository and command before running it.

Which Agent platforms does it support?

The upstream source does not declare a dedicated Agent platform.

What permissions or risks should you review?

Static analysis detected read-files signals. Review the cited source lines before installing; these signals are not a security audit.

What are the current evidence limits?

This page combines upstream documentation with deterministic repository, quality, and static-risk signals. It is not described as a manual test or security review.

SkillSignal brief

Decide whether it fits your work first

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

Useful in these contexts

Product / startupSoftware development

Core capabilities

Distilled from the source

Understand this Skill in one minute

About 2 min · 6 sections

When it is worth using

  1. •

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

Core workflow

  1. 1

    Step 1: Load and Review Plan

  2. 2

    Step 2: Execute Tasks

  3. 3

    Step 3: Complete Development

  4. 4

    Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one

  5. 5

    Read plan file

Repository stars
262,331
Repository forks
23,424
Quality
69/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

69/100
Documentation19/30
Specificity20/25
Maintenance18/20
Trust signals12/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

design-system-capture by event4u-app

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

existing-ui-audit by event4u-app

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min

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 (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in ../using-superpowers/references/). If subagents are available, use superpowers:subagent-driven-development instead of this skill.

The Process

Step 1: Load and Review Plan

  1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one
  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: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
Source repo
obra/superpowers
Skill path
skills/executing-plans/SKILL.md
Commit SHA
3dcbd5c4b48e
Repository license
MIT
Data collected