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

⭐2stars🔀0forks📁View on GitHub🕐Updated Nov 8, 2025⬇️4downloads

When & Why to Use This Skill

The 'executing-plans' skill is a sophisticated workflow automation tool designed to systematically implement complex implementation plans through controlled batch processing. It bridges the gap between high-level planning and technical execution by incorporating critical reviews, mandatory verification steps, and human-in-the-loop checkpoints. This skill ensures project integrity by preventing 'hallucination' or scope creep, making it an essential asset for reliable, step-by-step task completion in technical environments.

Use Cases

  • Complex Feature Implementation: Executing a multi-step technical design document where each code change requires verification and architectural review before moving to the next phase.
  • Systematic Code Refactoring: Managing large-scale codebase updates in bite-sized batches to ensure system stability and allow for incremental testing and feedback.
  • Migration and Deployment: Following a detailed migration playbook with built-in safety checks, ensuring that blockers are identified and addressed immediately rather than proceeding with errors.
  • Iterative Development Cycles: Implementing a series of planned tasks while maintaining a strict feedback loop with a human partner to refine the approach based on real-time results.
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

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