Executing Plans

Takes a written implementation plan and executes it step by step with proper checkpoints. Loads the plan file, reviews it critically for gaps or unclear instructions, then works through each task while marking progress and running verifications. Stops immediately when it hits blockers rather than guessing, which prevents the common problem of AI assistants making assumptions that derail implementations. Creates a TodoWrite file to track progress and integrates with git worktrees for isolated development. Really shines when you have a solid plan but want systematic execution with built-in quality gates.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 15
skills.sh installs: 257.5K
GitHub stars: 315.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add obra/superpowers --skill executing-plans --agent claude-code

Installs into .claude/skills of the current project.

Files

Executing Plans

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.

Narration: between tool calls, narrate at most one short line — the ledger and the tool results carry the record.

SKILL.md on GitHub