Skip to main content
skill CX Codex

executing-plans · mdiri-ai — Claude Code skill: setup and use

executing-plans is a Claude Code skill that carries out written implementation plans with review checkpoints. It pauses when a blocker needs clarification.

MIT ★ 6,467 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mdiri-ai/SoduWork --skill executing-plans -a claude-code
Open on GitHub

What executing-plans does

executing-plans loads an implementation plan, checks its logic, and turns its items into an ordered task list. It works through each step, runs the verifications named by the plan, and marks the work as it progresses.

The SoduWork workflow starts with SODUWORK.md, which must be read first. Execution pauses for a missing dependency, a failed check, a serious gap in the plan, or an unclear instruction. Once all tasks are verified, the skill hands off to finishing-a-development-branch; when subagents are available, it points to subagent-driven-development instead.

What it helps with

  • review a written implementation plan before coding
  • turn plan items into an ordered task list
  • run the checks attached to each task
  • pause on blockers instead of guessing
  • keep implementation off main or master without consent

Example prompts for the agent

  • Execute the plan in implementation-plan.md and verify each task.
  • Review this plan, create the task list, and stop if it has a critical gap.
  • Work through the plan in an isolated workspace, checking every step.

How to install executing-plans

1Skills CLI (Vercel)

npx skills add mdiri-ai/SoduWork --skill executing-plans -a claude-code

2Manually: put the files in place

~/.claude/skills/executing-plans/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/executing-plans/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about executing-plans

How do I install executing-plans in Claude Code?

Run npx skills add mdiri-ai/SoduWork --skill executing-plans -a claude-code. The skill file will be placed at ~/.claude/skills/executing-plans/SKILL.md.

What does executing-plans do?

It reads a written plan, reviews it before implementation, tracks its tasks, and runs the listed checks as work proceeds. After completion, it invokes finishing-a-development-branch.

What happens when a plan or verification is blocked?

The skill stops when it encounters a missing dependency, failed verification, a critical plan gap, or an unclear instruction. The agent asks for clarification instead of guessing.

Source text

SKILL.md · MIT
---
name: executing-plans
description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
---

Before following the upstream workflow in SoduWork, read [SoduWork runtime adaptation](SODUWORK.md).


# 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 (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in `../using-superpowers/references/`). If subagents are available, use superpowers:subagent-driven-development instead of this skill.

## The Process

### Step 1: Load and Review Plan
1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one
2. Read plan file
3. Review critically - identify any questions or concerns about the plan
4. If concerns: Raise them with your human partner before starting
5. If no concerns: Create todos for the plan items 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

### 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

© mdiri-ai · MIT · mdiri-ai/SoduWork

Similar skills

All skills for Agent setup: memory, context, orchestration →

executing-plans by other authors comes first.

executing-plans Jesse Vincent executing-plans runs an implementation plan in the current session instead of assigning each task to a subagent. Use it for inline work with TDD, a decision ledger, and a final branch review. CX Codex +1 242,988installs executing-plans FradSer executing-plans — a skill for Claude Code, Codex, and Cursor. Executes written implementation plans in task batches using isolated coordinator sub-agents and a single final commit. CX Codex +1 126installs executing-plans osmontero The executing-plans Claude Code skill carries out a written implementation plan in stages, with checks between batches. It activates when subagents cannot be used or tasks are too coupled to split up. CX Codex +1 107installs executing-plans dev-toolings The executing-plans skill guides Claude Code through an approved implementation plan, with test-first steps and a separate commit for each one. Use it for multi-step work or to resume after an interruption. CX Codex +1 ★ 234repo stars writing-plans bobmatnyc The writing-plans skill turns a finished design into a detailed implementation plan with small tasks, file paths, code, tests, and checks for another engineer. CX Codex +1 352installs azure-test-plans MicrosoftDocs azure-test-plans is a Claude Code skill for configuring Azure Test Plans, including retention limits, custom fields, and access permissions. It also covers failure types and tcm.exe automation. CX Codex +1 171installs paperclip-converting-plans-to-tasks paperclipai The paperclip-converting-plans-to-tasks skill turns an approved plan into owned Paperclip tasks with real dependencies. Use it when work needs deliberate delegation. CX Codex +1 264installs executing-marketing-campaigns davila7 executing-marketing-campaigns structures campaign planning, outbound copy, and performance tracking inside Claude Code across email, social, and web channels. CX Codex +1 1,236installs treatment-plans K-Dense-AI The treatment-plans skill formats and structurally validates local treatment-plan documentation once clinical decisions have been made and verified. It does not make clinical decisions. CX Codex +1 2,100installs creating-development-plans sammcj The creating-development-plans skill drafts a phased development plan with task breakdowns, requirements, and QA checklists. It helps set clear checkpoints before writing code. CX Codex +1 338installs

From the same set2

Project sponsors

Companies that keep this analytics open