executing-plans

executing-plans is a skill for Claude Code from ericgandrade/claude-superskills. It costs 28 tokens per session (1,133 once invoked), scanned A, original, MIT.

A controlled way to carry out an existing implementation plan in batches, with checks and review points between batches.

In plain words
What is it for?
Use it when a written plan is ready and the work needs progress tracking, verification, and pauses for review.
Why use it?
It reduces the risk of following a flawed plan too far or introducing regressions without noticing. A regression is a new problem caused by a change.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the TodoWrite tool.

Part of the claude-superskills plugin — 18 skills shipped together

Good fit Use it when a written plan is ready and the work needs progress tracking, verification, and pauses for review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ericgandrade/claude-superskills/executing-plans
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ericgandrade/claude-superskills --skill executing-plans
Clone the repo
git clone --depth 1 https://github.com/ericgandrade/claude-superskills

Made for: Claude Code.

Or install claude-superskills, the plugin that ships this one along with the rest of its 18 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for executing-plans

README.md
[![agentmods](https://agentmods.dev/badge/skills/ericgandrade/claude-superskills/executing-plans.svg)](https://agentmods.dev/skills/ericgandrade/claude-superskills/executing-plans)
Your own site
<a href="https://agentmods.dev/skills/ericgandrade/claude-superskills/executing-plans"><img src="https://agentmods.dev/badge/skills/ericgandrade/claude-superskills/executing-plans.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,133 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.01133
Opus 5 $0.00014 $0.00566
Sonnet 5 $0.00006 $0.00227
Haiku 4.5 $0.00003 $0.00113

Measured 8d ago against content hash fe3c5f9d842e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

executing-plans scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/executing-plans/SKILL.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Executing Plans

Purpose

Execute approved implementation plans in controlled batches with checkpoints, verification, and review gates.

When to Use

Use this skill when:

  • A written implementation plan already exists
  • Work must be executed with periodic review checkpoints
  • Risk of regressions requires strict plan adherence and verification

Progress Tracking

Display plan execution progress before each batch:

[████░░░░░░░░░░░░░░░░] 20% — Phase 1: Loading & Reviewing Plan
[████████░░░░░░░░░░░░] 40% — Phase 2: Executing Batch N
[████████████░░░░░░░░] 60% — Phase 3: Reporting & Verification
[████████████████░░░░] 80% — Phase 4: Awaiting Feedback
[████████████████████] 100% — Phase 5: Final Verification Complete

For plans with many tasks, adapt the gauge to reflect actual task completion: X/Y tasks done (N%).

Workflow

  1. Load and review plan critically
  2. Execute first batch of tasks
  3. Report results and verification output
  4. Pause for feedback and continue in batches
  5. Finish branch with final verification

Overview

Load plan, review critically, execute tasks in batches, report for review between batches.

Core principle: Batch execution with checkpoints for architect review.

Announce at start: "I'm using the executing-plans skill to implement this plan."

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 Batch

Default: First 3 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: Report

When batch complete:

  • Show what was implemented
  • Show verification output
  • Say: "Ready for feedback."

Step 4: Continue

Based on feedback:

  • Apply changes if needed
  • Execute next batch
  • Repeat until complete

Read the full file on GitHub · 142 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 142 lines · 28 tokens per session scan A fe3c5f9d842e

Subscribe to this mod's changes

executing-plans is a skill published in the GitHub repository ericgandrade/claude-superskills (74 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,133 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

writing-fragments

Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate"…

stevesolun/ctx · 80 tokens

no-mistakes

Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.

stevesolun/ctx · 67 tokens

obsidian-vault

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

stevesolun/ctx · 43 tokens

continuous-learning-v2

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

sangrokjung/claude-forge · 33 tokens

review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…

stevesolun/ctx · 95 tokens

writing-shape

Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants…

stevesolun/ctx · 76 tokens