Use when you have a written implementation plan to execute in the current session. Loads the plan, reviews critically, executes all tasks, and reports when complete.
Installs into .claude/skills of the current project.
Are you the author of Executing Plans?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/rbraga01-executing-plans)
---
name: executing-plans
description: Use when you have a written implementation plan to execute in the current session. Loads the plan, reviews critically, executes all tasks, and reports when complete.
---
# Executing Plans
Load plan, review critically, execute all tasks, report when complete.
**Announce at start:** "I'm using the executing-plans skill to implement this plan."
**Prefer `subagent-driven-development` over this skill** when subagents are available —
it provides higher quality through per-task fresh context and two-stage review.
## The Process
### Step 1: Load and Review Plan
1. Read plan file completely
2. Review critically — identify questions or concerns about the plan
3. If concerns: raise with human partner BEFORE starting
4. If no concerns: create TodoWrite and proceed
### Step 2: Execute Tasks
For each task:
1. Mark as in_progress
2. Follow each step exactly (plan has bite-sized steps)
3. Run verifications as specified
4. Mark as completed
**Do not pause to check in between tasks** unless blocked.
### Step 3: Complete Development
After all tasks complete:
- Use `finishing-a-development-branch` skill
- Verify tests, update docs, commit
## When to Stop and Ask
**STOP executing immediately when:**
- Hit a blocker (missing dependency, test fails, instruction unclear)
- Plan has critical gaps preventing starting
- Verification fails repeatedly
**Ask for clarification rather than guessing.**
## Hard Rules
- Never start on main/master branch without explicit user consent
- Follow plan steps exactly — don't improvise
- Stop when blocked, don't guess
- Skip nothing in the verification steps
