Plan Executor

Executing plans

by davila7 · MIT license · ★ 32,299 on GitHub

Use when you have a written implementation plan to execute in a separate session with review checkpoints

---
name: executing-plans
description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
---

# 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

Overview

Load plan, review critically, execute tasks in batches, report for review between batches.

Manual install (npx, ZIP)

Claude Codenpx skills add davila7/claude-code-templates --skill executing-plans -g -a claude-code

Claude Code (degit)

npx degit davila7/claude-code-templates/cli-tool/components/skills/productivity/executing-plans#main ~/.claude/skills/executing-plans-davila7

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.1 KB

Read SKILL.md here

davila7/main1 file shown

SKILL.md2.1 KB

Browse every file on GitHub↗

SKILL.md

Show the full text77 lines

executing-plans-davila7/SKILL.md77 lines · 2.1 KB

PreviewCode

Outline

RawView on GitHub

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

1	---
2	name: executing-plans
3	description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
4	---
5
6	# Executing Plans
7
8	## Overview
9
10	Load plan, review critically, execute tasks in batches, report for review between batches.
11
12	Core principle: Batch execution with checkpoints for architect review.
13
14	Announce at start: "I'm using the executing-plans skill to implement this plan."
15
16	## The Process
17
18	### Step 1: Load and Review Plan
19	1. Read plan file
20	2. Review critically - identify any questions or concerns about the plan
21	3. If concerns: Raise them with your human partner before starting
22	4. If no concerns: Create TodoWrite and proceed
23
24	### Step 2: Execute Batch
25	Default: First 3 tasks
26
27	For each task:
28	1. Mark as in_progress
29	2. Follow each step exactly (plan has bite-sized steps)
30	3. Run verifications as specified
31	4. Mark as completed
32
33	### Step 3: Report
34	When batch complete:
35	- Show what was implemented
36	- Show verification output
37	- Say: "Ready for feedback."
38
39	### Step 4: Continue
40	Based on feedback:
41	- Apply changes if needed
42	- Execute next batch
43	- Repeat until complete
44
45	### Step 5: Complete Development
46
47	After all tasks complete and verified:
48	- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
49	- REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
50	- Follow that skill to verify tests, present options, execute choice
51
52	## When to Stop and Ask for Help
53
54	STOP executing immediately when:
55	- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
56	- Plan has critical gaps preventing starting
57	- You don't understand an instruction
58	- Verification fails repeatedly
59
60	Ask for clarification rather than guessing.
61
62	## When to Revisit Earlier Steps
63
64	Return to Review (Step 1) when:
65	- Partner updates the plan based on your feedback
66	- Fundamental approach needs rethinking
67
68	Don't force through blockers - stop and ask.
69
70	## Remember
71	- Review plan critically first
72	- Follow plan steps exactly
73	- Don't skip verifications
74	- Reference skills when plan says to
75	- Between batches: just report and wait
76	- Stop when blocked, don't guess
77