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
When & Why to Use This Skill
The 'executing-plans' Claude skill is designed to bridge the gap between high-level planning and technical implementation. It enables Claude to systematically execute complex implementation plans through controlled batch processing, critical pre-execution reviews, and mandatory human-in-the-loop checkpoints. By emphasizing verification at every step and providing structured progress reports, this skill ensures high-quality output and architectural alignment in sophisticated software development and technical workflows.
Use Cases
- Incremental Feature Development: Implementing a multi-module software feature by breaking the technical plan into manageable batches, ensuring each component is verified before moving to the next.
- Large-Scale Code Refactoring: Executing wide-reaching codebase changes in controlled increments to maintain system stability and allow for frequent architectural reviews.
- Complex System Migrations: Following a detailed migration checklist where each phase requires successful verification and human sign-off before proceeding to subsequent tasks.
- Technical Documentation Overhauls: Systematically updating extensive documentation sets based on a structured plan, ensuring consistency and accuracy through periodic feedback loops.
| name | executing-plans |
|---|---|
| description | 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 |
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