executing-plans

A skill in obra/superpowers · 321,873 stars on GitHub

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

Security grade of this SKILL.md: SAFE · how we grade

How to install executing-plans

npx skills add obra/superpowers --skill executing-plans -a claude-code

The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.

What the SKILL.md says

Execute the plan yourself, task by task, in this session: no implementer subagent per task, no reviewer per task. One fresh-context review of the whole branch at the end. Why inline: Subagent-driven development pays for a fresh implementer and a fresh reviewer on every task, each re-reading the codebase from zero. Inline execution pays for one context (yours) plus one reviewer at the end. What it gives up is a fresh context per task and a second pair of eyes per task. This skill keeps what those two things bought, by other means: the brief is the spec, the ledger is your memory, TDD is the per-task gate, and the final reviewer is the second pair of eyes. Core principle: The plan already did the thinking. Execute it exactly, prove each step with a test you watched fail and then pass, and leave a record that survives your own forgetting.

Other skills in obra/superpowers

  • brainstorming You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning…
  • diagnosing-superpowers Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results,…
  • dispatching-parallel-agents Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
  • finishing-a-development-branch Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
  • receiving-code-review Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable…
  • requesting-code-review Use when completing tasks, implementing major features, or before merging to verify work meets requirements
  • subagent-driven-development Use when executing implementation plans with independent tasks in the current session
  • systematic-debugging Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
  • test-driven-development Use when implementing any feature or bugfix, before writing implementation code
  • using-git-worktrees Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated w…
  • using-superpowers Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clari…
  • verification-before-completion Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and…
  • writing-plans Use when you have a spec or requirements for a multi-step task, before touching code
  • writing-skills Use when creating new skills, editing existing skills, or verifying skills work before deployment