executing-plans

Executing Plans

Overview

Load plan, review critically, execute all tasks in the current session, report when complete.

Announce at start: "I'm using the executing-plans skill to implement this plan."

The Process

Step 1: Load and Review Plan

1. Read the plan file in full
2. Review critically — identify any gaps, ambiguities, or concerns
3. If concerns: raise them before starting, don't guess through them
4. If no concerns: create a TodoWrite item per task and proceed

Step 2: Execute Tasks

For each task, in order:

1. Mark task as in_progress
2. Follow each step exactly as written
3. Run every verification command specified — read the actual output
4. Mark task as completed only after verification passes

Never skip a verification step. If a test fails or a command errors, stop and diagnose before continuing.

Step 3: Wrap Up

After all tasks complete:

• Run the full test suite one final time
• Use verification-before-completion before claiming done
• Report what was done and what (if anything) was skipped or changed

When to Stop and Ask

Stop immediately when:

• A dependency is missing or a test fails unexpectedly
• An instruction is ambiguous
• Verification fails twice in a row on the same task
• The plan has a gap that prevents starting a task

Ask for clarification. Don't guess through blockers.

Red Flags

Thought	Reality
"The test failure is probably fine"	Stop. Read the output. Diagnose.
"I'll skip this verification, it's obvious"	Run it. Obvious things fail.
"The plan step is unclear but I think I know what it means"	Ask. Wrong assumptions compound.
"I'll fix the plan as I go"	Stop. Surface the gap. Get approval.

Integration

• writing-plans — creates the plan this skill executes
• test-driven-development — use when a task says "write a failing test first"
• verification-before-completion — required after all tasks are done
• systematic-debugging — use when a task's verification fails unexpectedly