Executing Plans
- 168k installs
- 262k repo stars
- Updated July 24, 2026
- obra/superpowers
Executing-plans is a superpowers skill that loads and executes written implementation plans in separate sessions with critical review.
About
Executing-plans is a superpowers skill that systematically executes written implementation plans with critical review. It loads a plan, reviews it for concerns, executes all tasks step-by-step, and reports completion status. Use when you have a detailed plan and need structured task execution with verification checkpoints.
- Executes implementation plans in dedicated sessions with review checkpoints
- Loads plan, reviews critically, executes all tasks, reports completion
- Integrates with superpowers:finishing-a-development-branch for final workflow
Executing Plans by the numbers
- 167,729 all-time installs (skills.sh)
- +8,492 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #31 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
executing-plans capabilities & compatibility
- Capabilities
- task execution · plan review · checkpoint verification
What executing-plans says it does
Load plan, review critically, execute all tasks, report when complete
npx skills add https://github.com/obra/superpowers --skill executing-plansAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 168k |
|---|---|
| repo stars | ★ 262k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 24, 2026 |
| Repository | obra/superpowers ↗ |
What it does
Developers executing detailed implementation plans with task tracking and verification checkpoints.
Who is it for?
Teams with detailed implementation plans who need systematic task execution and verification
Skip if: Sessions with subagent support where subagent-driven-development is available, or work that still needs brainstorming or plan authoring.
When should I use this skill?
You have a written plan to execute and need structured task tracking and completion reporting
What you get
All plan tasks completed, verified, and reported with clear completion status
- Completed code changes
- Verified task checklist
By the numbers
- Follows a 3-step load-execute-complete workflow
- Integrates 3 required Superpowers workflow skills
Files
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 (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. 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 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
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
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kForks & variants (2)
Executing Plans has 2 known copies in the catalog totaling 118 installs. They canonicalize to this original listing.
- guanyang - 115 installs
- jnmetacode - 3 installs
How it compares
Pick executing-plans for sequential plan execution in a fresh session; pick subagent-driven-development when the same session can dispatch implementer and reviewer subagents per task.
FAQ
When should executing-plans be used instead of subagent-driven-development?
executing-plans fits a separate session without subagent delegation. Superpowers recommends subagent-driven-development when subagents are available on Claude Code, Codex CLI, Codex App, or Copilot CLI because isolated per-task agents produce significantly higher quality.
What happens when a plan task verification fails?
executing-plans requires stopping immediately when verification fails repeatedly, a dependency is missing, or instructions are unclear. The agent must ask for clarification rather than force through blockers or skip mandated verification steps.
Which skills must run with executing-plans?
executing-plans integrates superpowers:using-git-worktrees for isolated workspaces, expects a plan from superpowers:writing-plans, and mandates superpowers:finishing-a-development-branch after all tasks complete to verify tests and present merge options.
Is Executing Plans safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.