Executing Plans

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

49 stars 8 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sodiumjoe/dotfiles --skill executing-plans
Manual install
git clone --depth 1 https://github.com/sodiumjoe/dotfiles.git /tmp/dotfiles
mkdir -p ~/.claude/skills
cp -r /tmp/dotfiles/home/.agents/skills/executing-plans ~/.claude/skills/executing-plans

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Executing Plans

Execute the plan yourself, task by task, in this session: no implementer
subagent per task, no reviewer per task. One fresh-context review of the
whole branch at the end.

**Why inline:** Subagent-driven development pays for a fresh implementer
and a fresh reviewer on every task, each re-reading the codebase from zero.
Inline execution pays for one context (yours) plus one reviewer at the end.
What it gives up is a fresh context per task and a second pair of eyes per
task. This skill keeps what those two things bought, by other means: the
brief is the spec, the ledger is your memory, TDD is the per-task gate, and
the final reviewer is the second pair of eyes.

**Core principle:** The plan already did the thinking. Execute it exactly,
prove each step with a test you watched fail and then pass, and leave a
record that survives your own forgetting.

**Narration:** between tool calls, narrate at most one short line — the
ledger and the tool results carry the record.

**Continuous execution:** Do not pause to check in with your human partner
between tasks. They chose inline execution to spend less, not to answer
"should I continue?" after every task. Execute all tasks from the plan
without stopping.

**Rulings, not stalls.** Conflicts, ambiguities, plan defects — decide them.
The spec is the binding authority, the plan is its argument, and your
judgment settles what neither answers. Record every decision in the ledger
Read the full skill on GitHub

Details

Skill name
executing-plans
Path
home/.agents/skills/executing-plans/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Executing Plans skill do?

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

How do I install the Executing Plans skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sodiumjoe/dotfiles --skill executing-plans. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Executing Plans popular?

It lives in sodiumjoe/dotfiles, which has 49 GitHub stars and 8 forks.

Related skills

Using Superpowers

49

sodiumjoe/dotfiles

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

OtherIn 2 lists

Finishing a Development Branch

49

sodiumjoe/dotfiles

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Git & Code Review

Neovim Review

49

sodiumjoe/dotfiles

Use when the user invokes /neovim-review for a pull request or a local :Review session in Neovim.

Git & Code Review

Nuxt Agent Ready Best Practices

43

vinayakkulkarni/vue-nuxt-best-practices

Nuxt agent-readiness guidelines for making a site operable by autonomous AI agents — not just cited by them. Covers the isitagentready.com standards: Markdown content negotiation, RFC 8288 Link headers, RFC 9727 API catalogs, Agent Skills discovery indexes, WebMCP browser tools, MCP Server Cards, OAuth/OIDC agent auth discovery, and DNS-AID. Triggers on tasks involving agent-ready, isitagentready, MCP, WebMCP, model context protocol, agent skills, API catalog, well-known discovery, agent auth, DNS-AID, A2A, or agentic commerce.

AI, LLMs & Agents

Prompt

43

analystacademy/claude-skills

Build a great prompt through a conversational interview. Use this skill whenever the user wants help writing, improving, or crafting a prompt — including phrases like "help me write a prompt", "I need a prompt for", "how do I prompt Claude to", "make me a prompt that", "I want to prompt an AI to", "create a prompt for", or any time the user describes a task they want an AI to do and seems to want help framing it. Even if they just describe a task vaguely and seem unsure how to ask for it — this skill applies. Trigger it early and often.

AI, LLMs & Agents14

Sanitize

19

agentward-ai/agentward

Detect and redact PII from text files. Supports 15 categories including credit cards, SSNs, emails, API keys, addresses, and more — with zero dependencies.

AI, LLMs & AgentsIn 1 list

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.