How do I install the Executing Plans skill?

Run npx skillmds@latest add makerjackie/executing-plans in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Executing Plans skill do?

Use when you have a written implementation plan to execute with checkpoints. It is listed under Coding & Dev Tools on SkillMD.

Is Executing Plans safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Executing Plans?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Executing Plans free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Executing Plans?

makerjackie (@makerjackie) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Executing Plans by makerjackie — Agent Skill

Name: Executing Plans
Author: makerjackie

File contents

（中文）Executing Plans

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

Read plan file
Review critically - identify any questions or concerns about the plan
If concerns: Raise them with your human partner before starting
If no concerns: Create TodoWrite and proceed

Step 2: Execute Batch

Default: First 3 tasks

For each task:

Mark as in_progress
Follow each step exactly (plan has bite-sized steps)
Run verifications as specified
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

Step 5: Complete Development

After all tasks complete and verified:

Announce: "I'm using the finishing-a-development-branch skill to complete this work."
REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
Follow that skill to verify tests, present options, execute choice

When to Stop and Ask for Help

STOP executing immediately when:

Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
Plan has critical gaps preventing starting
You don't understand an instruction
Verification fails repeatedly

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

Return to Review (Step 1) when:

Partner updates the plan based on your feedback
Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember

Review plan critically first
Follow plan steps exactly
Don't skip verifications
Reference skills when plan says to
Between batches: just report and wait
Stop when blocked, don't guess
Never start implementation on main/master branch without explicit user consent

Integration

Required workflow skills:

superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
superpowers:writing-plans - Creates the plan this skill executes
superpowers:finishing-a-development-branch - Complete development after all tasks

---name: executing-plansdescription: Use when you have a written implementation plan to execute with checkpoints.---# （中文）Executing Plans## OverviewLoad 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 Plan1. Read plan file2. Review critically - identify any questions or concerns about the plan3. If concerns: Raise them with your human partner before starting4. If no concerns: Create TodoWrite and proceed### Step 2: Execute Batch**Default: First 3 tasks**For each task:1. Mark as in_progress2. Follow each step exactly (plan has bite-sized steps)3. Run verifications as specified4. Mark as completed### Step 3: ReportWhen batch complete:- Show what was implemented- Show verification output- Say: "Ready for feedback."### Step 4: ContinueBased on feedback:- Apply changes if needed- Execute next batch- Repeat until complete### Step 5: Complete DevelopmentAfter all tasks complete and verified:- Announce: "I'm using the finishing-a-development-branch skill to complete this work."- **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch- Follow that skill to verify tests, present options, execute choice## When to Stop and Ask for Help**STOP executing immediately when:**- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)- Plan has critical gaps preventing starting- You don't understand an instruction- Verification fails repeatedly**Ask for clarification rather than guessing.**## When to Revisit Earlier Steps**Return to Review (Step 1) when:**- Partner updates the plan based on your feedback- Fundamental approach needs rethinking**Don't force through blockers** - stop and ask.## Remember- Review plan critically first- Follow plan steps exactly- Don't skip verifications- Reference skills when plan says to- Between batches: just report and wait- Stop when blocked, don't guess- Never start implementation on main/master branch without explicit user consent## Integration**Required workflow skills:**- **superpowers:using-git-worktrees** - REQUIRED: Set up isolated workspace before starting- **superpowers:writing-plans** - Creates the plan this skill executes- **superpowers:finishing-a-development-branch** - Complete development after all tasks

Frequently asked questions

Executing Plans