Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log.
Install Executing Plans
$ npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills executing-plans --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/executing-plans .claude/skills/executing-plans && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "executing-plans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/executing-plans into .claude/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/executing-plansType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills executing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/executing-plans .agents/skills/executing-plans && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "executing-plans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/executing-plans into .agents/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills executing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/executing-plans .cursor/skills/executing-plans && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "executing-plans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/executing-plans into .cursor/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/executing-plans--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills executing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/executing-plans .gemini/skills/executing-plans && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "executing-plans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/executing-plans into .gemini/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills executing-plansInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/executing-plans .github/skills/executing-plans && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "executing-plans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/executing-plans into .github/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills executing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/executing-plans .opencode/skills/executing-plans && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "executing-plans" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/executing-plans into .opencode/skills/executing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-plans", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
executing-plans- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 614 words
- Files
- 1
- Skills in repo
- 1,334
- Repo updated
- First seen
- Licence
- MIT
At a glance
Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log.
- Works in 6 steps: Load the plan and check it's still true.… → One step, then its verification —… → Classify every divergence out loud. When… → …
- Working through a plan (yours
- SKILL.md covers What This Skill Produces, Execution Method, Output Format and Quality Checks, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Executing Plans is an agent skill from mohitagw15856/pm-claude-skills. Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log. Use when working through a plan (yours or another agent's), resuming multi-session work, or when execution keeps drifting from what was agreed. Produces completed work plus an execution log showing what matched the plan, what deviated and why, and what the plan got wrong. Pairs with writing-plans.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Working through a plan (yours
- Another agents)
- Resuming multi-session work
- Execution keeps drifting from what was agreed
Example prompts
- “/executing-plans”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Load the plan and check it's still true. Before step 1: do the plan's assumptions still hold (the branch, the data, the constraint)? A…
- One step, then its verification — actually run. The verification isn't decoration: run the command, check the observable, record the…
- Classify every divergence out loud. When reality disagrees with the plan, stop and classify
- Respect the stop conditions absolutely. They were written calm; you are now in flow and biased toward momentum. The "must not do" list…
- Checkpoint on schedule. At each planned checkpoint (or ~every 30-45 min of work): where am I vs the plan, what's the log show, is the…
- Close with the feedback loop. At completion: run the plan's DONE test (not your feeling of doneness). Then write the plan feedback: which…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Executing Plans loads about 1.2k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 614 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 614 words, ~1,168 tokens.
Download SKILL.mdSave it as
.claude/skills/executing-plans/SKILL.md (or your agent's skills folder).- name
- executing-plans
- description
- Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log. Use when working through a plan (yours or another agent's), resuming multi-session work, or when execution keeps drifting from what was agreed. Produces completed work plus an execution log showing what matched the plan, what deviated and why, and what the plan got wrong. Pairs with writing-plans.
Executing Plans Skill
A plan's value is realised or destroyed at execution time. The two failure modes: rigid execution (following a plan reality has invalidated) and drift (quietly improvising until the work no longer resembles the plan and nobody decided that). The discipline is the same for both: deviations are decisions, made visibly.
What This Skill Produces
- The work, executed step-by-step with per-step verification actually run
- An execution log: step → result → verification outcome → any deviation with its reason
- A plan feedback note: what the plan got wrong (feeds the next plan)
Execution Method
- Load the plan and check it's still true. Before step 1: do the plan's assumptions still hold (the branch, the data, the constraint)? A plan written yesterday can be stale today; two minutes of validation beats an hour of executing a fiction.
- One step, then its verification — actually run. The verification isn't decoration: run the command, check the observable, record the result. Advancing on "that probably worked" is how step 6 fails mysteriously because step 3 silently didn't.
- Classify every divergence out loud. When reality disagrees with the plan, stop and classify:
- Plan-preserving detail — the plan's intent holds, the mechanics differ slightly → note it in the log, continue
- Plan deviation — the approach must change for this step → amend the plan visibly (strikethrough + new step), state why, continue
- Plan invalidation — a stop condition hit, or the goal itself is now wrong → STOP; report; replan with the human before another line of work The cardinal sin is treating an invalidation as a detail because stopping feels like failure.
- Respect the stop conditions absolutely. They were written calm; you are now in flow and biased toward momentum. The "must not do" list doesn't bend for convenience — if it should, that's a visible plan amendment, decided, not slid into.
- Checkpoint on schedule. At each planned checkpoint (or ~every 30-45 min of work): where am I vs the plan, what's the log show, is the remaining plan still right? Multi-session work ends each session with a state note: done through step N, next action, open questions — the resume beats re-derivation.
- Close with the feedback loop. At completion: run the plan's DONE test (not your feeling of doneness). Then write the plan feedback: which estimates were off, which risk fired, which verification caught something. Plans improve only if execution reports back.
Show full SKILL.md (220 more words)Show less
Output Format
Per step (in the log):
Step N: [action] → [result] · verify: [check run → outcome] · [deviation? classified + reason]
On completion:
Execution report: [plan name]
Done test: [the plan's test → passed/failed, evidence] Deviations: [each, with classification and reason — or "none"] The plan was wrong about: [feedback for the next plan] Follow-ups discovered (not done, not forgotten): […]
Quality Checks
- Every step's verification was actually executed, result recorded
- Every divergence was classified (detail / deviation / invalidation) — none absorbed silently
- Stop conditions were honoured; any override was a visible, stated decision
- Completion was declared by the plan's done-test, not by fatigue
- The plan-feedback note exists
Anti-Patterns
- Do not improvise around a broken plan — amend it visibly or stop; silent drift is unaccountable work
- Do not skip verifications when steps "obviously worked" — the mysterious step-6 failure was born at step 3
- Do not push through a stop condition on momentum — it was written calm precisely because you wouldn't be
- Do not declare done without running the done-test — feeling-finished and being-finished diverge exactly when it matters
- Do not end a session without the state note — re-derivation is the tax on every resumed task
Example Trigger Phrases
- "Work through this plan step by step."
- "Resume the plan from where we left off."
- "Execute this plan and log each step."
- "Follow the plan and tell me when it deviates."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/executing-plans of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Executing Plans next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Executing Plans this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 102k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 56 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Writing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Planning With Files
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
More from mohitagw15856/pm-claude-skills
All 1,334 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Offer Comparison
mohitagw15856/pm-claude-skills
Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.
Related
Categories
Questions about Executing Plans
What does Executing Plans do?
Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log. Executing Plans is an agent skill from mohitagw15856/pm-claude-skills. Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log.
When should I use Executing Plans?
Executing Plans fits situations like: working through a plan (yours; another agents); resuming multi-session work; execution keeps drifting from what was agreed.
How do I install Executing Plans in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a claude-code`. Or copy the skill folder (skills/executing-plans in mohitagw15856/pm-claude-skills) into .claude/skills/executing-plans in your project. Claude Code loads it when a task matches its description.
How do I install Executing Plans in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a codex`. Or copy the skill folder (skills/executing-plans in mohitagw15856/pm-claude-skills) into .agents/skills/executing-plans in your project. Codex loads it when a task matches its description.
Can I use Executing Plans in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill executing-plans -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/executing-plans, .gemini/skills/executing-plans, .github/skills/executing-plans and .opencode/skills/executing-plans in your project.
What does Executing Plans need to run?
SKILL.md names no scripts, command-line tools or credentials: Executing Plans is instructions for the agent only.
Does Executing Plans access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Executing Plans safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Executing Plans use?
Executing Plans is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Executing Plans use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Executing Plans?
Skills that share tags, products or a category with Executing Plans: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 102k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Executing Plans?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,429 GitHub stars. The repository holds 1,334 skills in this directory. The repository was last updated on October 6, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.