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

1. •Read plan file
2. •Review critically - identify any questions or concerns about the plan
3. •If concerns: Use question tool to raise them:

question({
  questions: [
    {
      header: "Concerns",
      question: "Plan review complete. Any concerns before proceeding?",
      options: [
        {
          label: "No concerns (Recommended)",
          description: "Plan looks good, execute batches",
        },
        {
          label: "Has concerns",
          description: "Need clarification before starting",
        },
      ],
    },
  ],
});

1. •Read plan and identify:
   • •What is the goal?
   • •What are the deliverables?
   • •What are the risks?
   • •Does the approach make sense?
   • •Are there missing pieces?

If no concerns: Create TodoWrite and proceed If concerns: Wait for human to decide and resubmit

Step 2: Execute Batch

Default: First 3 tasks

For each task:

1. •Mark as in_progress
2. •Follow each step exactly (plan has bite-sized steps)
3. •Run verifications as specified
4. •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 finishing-a-development-branch skill to complete this work."
• •REQUIRED SUB-SKILL: Use skill({ name: "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