Best for
- Use when you have a written implementation plan to execute in a separate session with review checkpoints
Source profileQuality 69/100
obra/superpowers/skills/executing-plans/SKILL.md
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
- Source repository stars
- 262,331
- Declared platforms
- 0
- Static risk flags
- 1
- Last source update
- 2026-07-24
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/obra/superpowers --skill "skills/executing-plans"Safe inspection promptEditorial
Inspect the Agent Skill "executing-plans" from https://github.com/obra/superpowers/blob/3dcbd5c4b48e02263fbf4a3c01e3fe4f81d584d9/skills/executing-plans/SKILL.md at commit 3dcbd5c4b48e02263fbf4a3c01e3fe4f81d584d9. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
The Process
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 co…
Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing oneRead plan fileReview critically - identify any questions or concerns about the plan - 02
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 co…
Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing oneRead plan fileReview critically - identify any questions or concerns about the plan - 03
Step 2: Execute Tasks
For each task: 1. Mark as inprogress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed
Mark as inprogressFollow each step exactly (plan has bite-sized steps)Run verifications as specified - 04
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
Announce: "I'm using the finishing-a-development-branch skill to complete this work."REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branchFollow that skill to verify tests, present options, execute choice
Permission review
Static risk signals and limitations
Reads files
The documentation asks the agent to read local files, directories, or repositories.
Read plan fileEvidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 69/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 262,331 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- obra/superpowers
- Skill path
- skills/executing-plans/SKILL.md
- Commit
- 3dcbd5c4b48e02263fbf4a3c01e3fe4f81d584d9
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
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
- Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one
- Read plan file
- Review critically - identify any questions or concerns about the plan
- If concerns: Raise them with your human partner before starting
- If no concerns: Create todos for the plan items and proceed
Step 2: Execute Tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- 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