Executing Plans
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add executing-plansWho is stuck, and on what
Use when you have a written implementation plan to execute in a separate session with review checkpoints
The whole source
Frontmatter — 2 properties
| name | executing-plans |
|---|---|
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
| 1 | --- |
| 2 | name: executing-plans |
| 3 | description: Use when you have a written implementation plan to execute in a separate session with review checkpoints |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # Executing Plans |
| 7 | |
| 8 | ## Overview |
| 9 | |
| 10 | Load plan, review critically, execute all tasks, report when complete. |
| 11 | |
| 12 | **Announce at start:** "I'm using the executing-plans skill to implement this plan." |
| 13 | |
| 14 | **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. |
| 15 | |
| 16 | ## The Process |
| 17 | |
| 18 | ### Step 1: Load and Review Plan |
| 19 | 1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one |
| 20 | 2. Read plan file |
| 21 | 3. Review critically - identify any questions or concerns about the plan |
| 22 | 4. If concerns: Raise them with your human partner before starting |
| 23 | 5. If no concerns: Create todos for the plan items and proceed |
| 24 | |
| 25 | ### Step 2: Execute Tasks |
| 26 | |
| 27 | For each task: |
| 28 | 1. Mark as in_progress |
| 29 | 2. Follow each step exactly (plan has bite-sized steps) |
| 30 | 3. Run verifications as specified |
| 31 | 4. Mark as completed |
| 32 | |
| 33 | ### Step 3: Complete Development |
| 34 | |
| 35 | After all tasks complete and verified: |
| 36 | - Announce: "I'm using the finishing-a-development-branch skill to complete this work." |
| 37 | - **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch |
| 38 | - Follow that skill to verify tests, present options, execute choice |
| 39 | |
| 40 | ## When to Stop and Ask for Help |
| 41 | |
| 42 | **STOP executing immediately when:** |
| 43 | - Hit a blocker (missing dependency, test fails, instruction unclear) |
| 44 | - Plan has critical gaps preventing starting |
| 45 | - You don't understand an instruction |
| 46 | - Verification fails repeatedly |
| 47 | |
| 48 | **Ask for clarification rather than guessing.** |
| 49 | |
| 50 | ## When to Revisit Earlier Steps |
| 51 | |
| 52 | **Return to Review (Step 1) when:** |
| 53 | - Partner updates the plan based on your feedback |
| 54 | - Fundamental approach needs rethinking |
| 55 | |
| 56 | **Don't force through blockers** - stop and ask. |
| 57 | |
| 58 | ## Remember |
| 59 | - Review plan critically first |
| 60 | - Follow plan steps exactly |
| 61 | - Don't skip verifications |
| 62 | - Reference skills when plan says to |
| 63 | - Stop when blocked, don't guess |
| 64 | - Never start implementation on main/master branch without explicit user consent |
| 65 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current session◐◐◐◐◐●36/40Python Code Style & DocumentationPython code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.◐····●35/40Competitor Price Analysis 💲Competitor pricing strategy analysis and market positioning. Price mapping, pricing gaps identification, elasticity signals evaluation, and strategic pricing optimization. Use when the user asks about competitor pricing, price analysis, pricing strategy, or co◐····●34/40Competitor Price Tracker 📊Set up competitor price tracking and monitoring workflows. Track price changes, detect promotions, analyze pricing patterns, and get alerts for competitive price movements.◐····●34/40