Executing Plans
Carry out a written implementation plan while recording decisions, checks, and progress.
npx skills add obra/superpowers --skill executing-plans What it does
A long implementation can drift from its specification as context and assumptions change. This skill organizes inline execution around a plan, a progress record, and explicit verification of each deliverable.
What changes after install
- Treats the specification as the authority when a plan and code disagree.
- Records task progress and implementation rulings in a persistent ledger.
- Checks task outcomes and performs a final review before handoff.
Install
Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.
npx skills add obra/superpowers --skill executing-plans Before using Executing Plans
- Start with a written implementation plan, an agreed working directory and functioning project test commands. Keep the referenced testing and verification companion skills available when following the full workflow.
Read the reviewed setup instructions for the selected workflow.
When to use it
- Implementing an already approved multi-step plan in one working session.
- Maintaining a clear progress record across a long coding task.
When not to use it
- Starting from an ambiguous product idea without a usable specification.
- Assuming all referenced helper scripts are present after installing only this entry.
Supply a real plan and its specification
Use this when a feature has already been designed and broken into concrete tasks. Give the agent both the plan and the specification it implements. For example, an import workflow might have separate tasks for parsing, validation, preview, and persistence. The implementation needs to preserve the interfaces between those tasks rather than treating each as an unrelated change.
The reviewed source focuses on doing the implementation in the current session. It records progress and decisions in a ledger so that a long task does not rely entirely on conversation memory. When an assumption in the plan proves wrong, the workflow calls for a recorded ruling explaining what changed and why.
Check the surrounding installation
This skill refers to other Superpowers skills and helper scripts, including planning, test-driven development, review, and branch finishing. A single SKILL.md is not a self-contained execution system. Inspect the collection’s setup and available files before expecting the complete workflow to run.
The host agent also needs permission and tools to read the repository, edit files, and run the project’s checks. Installing instructions cannot supply unavailable build tools or credentials.
Evaluate completion against behavior
Before marking the last task complete, give Verify Before Completion the acceptance criteria and the changes to check. If the plan requires a user-visible interaction, exercise it and record the result alongside the unit test output.
Choose Brainstorming when the desired outcome is still open and Writing Plans when tasks have not yet been defined. SkillDex has reviewed this execution workflow but has not exercised its helper scripts or verified runtime behavior across agents.
Related workflows
FAQ
- Is this the same as Writing Plans?
- No. Writing Plans creates the implementation plan; Executing Plans carries out a plan that already exists.
- Does it always create an implementer subagent for each task?
- The reviewed version describes inline implementation and a final review, rather than a separate implementer for every task.