Coordinates the execution of pre-written implementation plans through a structured review-to-completion workflow.
Install
mkdir -p .claude/skills/obra-executing-plans && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17964" && unzip -o skill.zip -d .claude/skills/obra-executing-plans && rm skill.zipInstalls to .claude/skills/obra-executing-plans
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when you have a written implementation plan to execute in a separate session with review checkpointsKey capabilities
- →Execute tasks sequentially as defined in the plan.
- →Run verifications as specified for each task.
- →Use `obra-finishing-a-development-branch` to complete development.
- →Stop execution and ask for help when encountering blockers.
How it works
The skill loads and reviews an implementation plan, then executes each task and its verifications sequentially, stopping to ask for help if blockers occur.
Inputs & outputs
When to use obra-executing-plans
- →Execute a step-by-step development plan
- →Run verification tasks for complex features
- →Maintain consistency in multi-session coding
- →Handle complex implementation phases
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 obra-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 obra-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:
- obra-using-git-worktrees - REQUIRED: Set up isolated workspace before starting
- obra-writing-plans - Creates the plan this skill executes
- obra-finishing-a-development-branch - Complete development after all tasks
When not to use it
- →When a written implementation plan is not available.
- →When subagents are available, use `obra-subagent-driven-development` instead.
- →When the user wants to start implementation on main/master branch without explicit consent.
Prerequisites
Limitations
- →The skill relies on specific sub-skills for setup and completion.
- →The skill stops execution when blocked, requiring clarification.
How it compares
This skill provides a structured and guided execution of a pre-defined implementation plan, ensuring all steps and verifications are followed, unlike ad-hoc development.
Compared to similar skills
obra-executing-plans side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| obra-executing-plans (this skill) | 0 | 3mo | No flags | Intermediate |
| executing-plans | 6 | 2mo | No flags | Intermediate |
| task-think | 1 | 17d | No flags | Advanced |
| map-workflows-guide | 0 | 4mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by pagopa
View all by pagopa →You might also like
executing-plans
obra
Use when you have a written implementation plan to execute in a separate session with review checkpoints
task-think
telegramdesktop
Orchestrate a multi-phase implementation workflow for this repository with artifact files under .ai/task-slug and optional fresh codex exec child runs per phase. Use when the user wants one prompt to drive context gathering, planning, implementation, verification, and review iterations while keeping the main session context clean.
map-workflows-guide
diegosouzapw
Comprehensive guide for choosing the right MAP workflow based on task type and requirements
executing-plans
liujiarui0918
Use to execute a written plan. Run tasks in batches with human checkpoints.
aif-improve
vanyastaff
Refine and enhance an existing implementation plan with a second iteration. Re-analyzes the codebase, checks for gaps, missing tasks, wrong dependencies, and improves the plan quality. Use after /aif-plan to polish the plan before implementation, or to improve an existing /aif-fix plan.
brainstorming
doviettung96
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.