executing plans
- Repo stars 0
- Author updated Aug 12, 2026, 04:53 PM
- Author repo superpowers
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @obra · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
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
For each task: Mark as in_progress Follow each step exactly (plan has bite-sized steps) Run verifications as specified Mark as completed
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
# 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
Listed in source order.
sections -> Overview → The Process → Step 1: Load and Review Plan → Step 2: Execute Tasks → Step 3: Complete Development → When to Stop and Ask for Help
terms -> Announce at start · Note · REQUIRED SUB-SKILL · STOP executing immediately when · Ask for clarification rather than guessing. · Return to Review (Step 1) when · Don't force through blockers
files/cmd -> ../using-superpowers/references/ · ../using-superpowers/references · main/master
body sha256 -> 9f68b13f111f
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.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