executing-plans
Execute a written implementation plan with critical review and task checkpoints.
- Requires loading and critically reviewing the plan before execution; raises concerns with the human partner if issues are identified
- Executes tasks sequentially, marking progress and running verifications as specified in the plan
- Stops immediately on blockers (missing dependencies, test failures, unclear instructions) rather than guessing; asks for clarification
- Integrates with git-worktrees for isolated workspaces and finishing-a-development-branch to complete the work after all tasks verify
- Works best on platforms with subagent support; recommends subagent-driven-development skill as the preferred alternative when available
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. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use superpowers:subagent-driven-development instead of this skill.
The Process
Step 1: Load and Review Plan
- 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 TodoWrite and proceed
Step 2: Execute Tasks
More from obra/superpowers
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
152.3Kusing-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
92.7Ksystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
92.0Kwriting-plans
Use when you have a spec or requirements for a multi-step task, before touching code
91.3Krequesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
80.4Ktest-driven-development
Use when implementing any feature or bugfix, before writing implementation code
79.8K
More in Agent workflows
find-skills
Discover and install skills from skills.sh directly inside an agent session
vercel-labs/skillsagent-browser
Full browser automation: navigate, click, fill forms, extract data, and screenshot
vercel-labs/agent-browserskill-creator
Create, test, and publish new skills from within your agent
anthropics/skillsbrowser-use
Browser automation with visual understanding — interacts with pages based on what it sees
browser-use/browser-usesubagent-driven-development
Orchestrate specialized subagents for different parts of a task
obra/superpowers