Open Skills Logo
Open Skills

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Author

@obra

Category

Office Automation

Install

Hot:5

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=obra-skills-executing-plans&locale=en&source=copy
name:executing-plansdescription:Use when you have a written implementation plan to execute in a separate session with review checkpoints

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

    For each task:

  • Mark as in_progress

  • Follow each step exactly (plan has bite-sized steps)

  • Run verifications as specified

  • 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