# executing plans
## Metadata

- Canonical URL: https://6ducklearn.com/skills/executing-plans/
- Markdown URL: https://6ducklearn.com/skills/executing-plans/index.md
- Product: skills
- Category: collaboration
- Tags: superpowers, collaboration
- Updated: 2026-04-05T16:48:50.396208+00:00
## Summary
Use when you have a written implementation plan to execute in a separate session with review checkpoints
## Content
# 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

## Related Skills

- [brainstorming](https://6ducklearn.com/skills/brainstorming/index.md): You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- [dispatching parallel agents](https://6ducklearn.com/skills/dispatching-parallel-agents/index.md): Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- [finishing a development branch](https://6ducklearn.com/skills/finishing-a-development-branch/index.md): Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- [receiving code review](https://6ducklearn.com/skills/receiving-code-review/index.md): Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
- [requesting code review](https://6ducklearn.com/skills/requesting-code-review/index.md): Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- [subagent driven development](https://6ducklearn.com/skills/subagent-driven-development/index.md): Use when executing implementation plans with independent tasks in the current session