executing-plans
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.
npx skills add mohitagw15856/pm-claude-skills --skill executing-plans --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. **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. 2. **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. 3. **Classify every divergence out loud.** When reality disagrees
- What This Skill Produces
- Execution Method
- Output Format
- Execution report: [plan name]
- Quality Checks
- Anti-Patterns
What does the executing-plans skill 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. 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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill executing-plans --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.