executing-plans

Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

⭐4stars🔀0forks📁View on GitHub🕐Updated Dec 28, 2025

When & Why to Use This Skill

The 'executing-plans' Claude skill is designed for systematic and controlled implementation of complex project roadmaps. It optimizes the workflow by loading structured plans, performing critical pre-execution reviews, and executing tasks in manageable batches with mandatory human-in-the-loop checkpoints. This skill ensures high-quality outcomes by integrating verification steps and stopping immediately when blockers arise, making it an essential tool for reliable agentic task execution.

Use Cases

  • Software Feature Implementation: Following a detailed technical design document to build a multi-component feature, ensuring each module is verified before proceeding to the next batch of tasks.
  • System Migration and Refactoring: Executing a step-by-step codebase migration or large-scale refactoring plan where architectural integrity must be checked at specific intervals.
  • Complex Data Processing: Managing multi-stage data extraction or transformation pipelines that require manual validation of intermediate results to prevent error propagation.
  • Technical Documentation Updates: Systematically updating large sets of documentation based on a predefined plan, allowing for style and accuracy reviews between sections.
nameexecuting-plans
descriptionUse when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

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: Raise them with your human partner before starting
  4. If no concerns: Create TodoWrite and proceed

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

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