executing-plans

Executes written implementation plans task-by-task with verification checkpoints and review gates.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill executing-plans-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/superpowers/skills/executing-plans
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill executing-plans-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working code often goes wrong when steps are skipped, verifications are ignored, or blockers are guessed through. This Skill enforces a disciplined execution loop so plans are followed exactly and issues surface early. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with your human partner before any code is written. - Task-by-Task Execution: Tracks each task with TodoWrite, follows bite-sized steps exactly, and runs the verifications specified in the plan. - Stop-and-Ask Discipline: Halts immediately on blockers, unclear instructions, or repeated verification failures instead of guessing. - Use Case: You have a multi-task implementation plan from a planning session. Hand it to this Skill in a fresh session, and it reviews the plan, executes every task with verification, then hands off to the finishing-a-development-branch workflow. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/feature-auth.md, reviewing it critically first and stopping if anything is unclear.

Frequently Asked Questions about executing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an implementation plan with an AI assistant?

Provide the plan file and invoke the executing-plans skill. It reads the plan, reviews it critically for concerns, then executes each task in order using TodoWrite tracking, running the verifications specified in each step before marking tasks complete.

What should happen before executing a written implementation plan?

The plan should be reviewed critically first, raising any questions or concerns with your human partner before starting. An isolated workspace such as a git worktree should also be set up, and implementation should never begin on main or master without explicit consent.

What happens when a plan execution hits a blocker?

Execution stops immediately when hitting a blocker such as a missing dependency, failing test, or unclear instruction. The skill asks for clarification rather than guessing, and returns to plan review if the fundamental approach needs rethinking.

Does executing-plans work without subagent support?

Yes, it works in a single session, but the documentation notes results are significantly better on platforms with subagent support such as Claude Code or Codex. Where subagents exist, the subagent-driven-development skill is recommended instead.

When should I use subagent-driven-development instead of executing-plans?

Use subagent-driven-development when your platform supports subagents, since it delegates tasks for higher-quality isolated work. Use executing-plans when running in a single session without subagent capabilities.