Skip to content

Executing Plans

Verified

Execute implementation plans in batches with human checkpoints

By Jesse Vincent (obra) 4,500 stars v1.0 Updated 2026-03-15
$ Add to .claude/skills/

About This Skill

# 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 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: Create TodoWrite and proceed

Step 2: Execute Tasks

  1. For each task:
  2. Mark as in_progress
  3. Follow each step exactly (plan has bite-sized steps)
  4. Run verifications as specified
  5. Mark as completed

Step 3: Complete Development

  • After all tasks complete and verified:
  • Announce: "I'm using the finishing-a-development-branch skill to complete this work."
  • REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
  • Follow that skill to verify tests, present options, execute choice

When to Stop and Ask for Help

  • STOP executing immediately when:
  • Hit a blocker (missing dependency, test fails, instruction unclear)
  • Plan has critical gaps preventing starting
  • You don't understand an instruction
  • Verification fails repeatedly

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

  • Return to Review (Step 1) when:
  • Partner updates the plan based on your feedback
  • Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember - Review plan critically first - Follow plan steps exactly - Don't skip verifications - Reference skills when plan says to - Stop when blocked, don't guess - Never start implementation on main/master branch without explicit user consent

Integration

  • Required workflow skills:
  • superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
  • superpowers:writing-plans - Creates the plan this skill executes
  • superpowers:finishing-a-development-branch - Complete development after all tasks

Use Cases

  • Execute project plans with systematic step-by-step tracking
  • Break down complex tasks into manageable execution phases
  • Track progress against plan milestones during implementation
  • Coordinate multi-step workflows with dependency management
  • Maintain execution discipline with structured checkpoints

Pros & Cons

Pros

  • +Integrates with Obra planning tools for end-to-end project workflows
  • +Structured execution prevents scope creep and keeps focus on planned deliverables
  • +Progress tracking provides visibility into implementation status

Cons

  • -Tightly coupled to the Obra workflow ecosystem
  • -Rigid execution structure may not suit all project types

FAQ

What does Executing Plans do?
Execute implementation plans in batches with human checkpoints
What platforms support Executing Plans?
Executing Plans is available on Claude Code, OpenAI Codex CLI, Gemini CLI.
What are the use cases for Executing Plans?
Execute project plans with systematic step-by-step tracking. Break down complex tasks into manageable execution phases. Track progress against plan milestones during implementation.

100+ free AI tools

Writing, PDF, image, and developer tools — all in your browser.

Next Step

Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.