| name | executing-plans |
| description | This skill should be used when the user has a written implementation plan to execute in a separate session with review checkpoints. |
| license | MIT |
Executing Plans
Purpose
Execute approved implementation plans in controlled batches with checkpoints, verification, and review gates.
When to Use
Use this skill when:
- A written implementation plan already exists
- Work must be executed with periodic review checkpoints
- Risk of regressions requires strict plan adherence and verification
Progress Tracking
Display plan execution progress before each batch:
[████░░░░░░░░░░░░░░░░] 20% — Phase 1: Loading & Reviewing Plan
[████████░░░░░░░░░░░░] 40% — Phase 2: Executing Batch N
[████████████░░░░░░░░] 60% — Phase 3: Reporting & Verification
[████████████████░░░░] 80% — Phase 4: Awaiting Feedback
[████████████████████] 100% — Phase 5: Final Verification Complete
For plans with many tasks, adapt the gauge to reflect actual task completion: X/Y tasks done (N%).
Workflow
- Load and review plan critically
- Execute first batch of tasks
- Report results and verification output
- Pause for feedback and continue in batches
- Finish branch with final verification
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
- Never start implementation on main/master branch without explicit user consent
Integration
Required workflow skills:
- superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
- superpowers:writing-plans - Creates the plan this skill executes
- superpowers:finishing-a-development-branch - Complete development after all tasks
Critical Rules
- Stop immediately on blockers and ask for clarification.
- Do not skip verification commands defined in the plan.
- Do not continue to the next batch without reporting and waiting for feedback.
Error Handling
| Error | Likely Cause | Action |
|---|
| Plan file not found | Path provided doesn't exist or file was moved | Ask user to confirm file path; list available plan files in docs/plans/ |
| Ambiguous task description | Step in plan is unclear or underspecified | Stop and ask user for clarification before proceeding |
| Task depends on failed prerequisite | Earlier task failed or was skipped | Report the dependency failure; do not continue until resolved |
| Verification command fails | Tests or checks defined in plan are failing | Stop immediately, report full error output, wait for user instruction |
| Blocker encountered mid-execution | Unexpected state, conflicting files, or missing context | Pause, report the exact blocker, and ask user how to proceed |
| Batch completed with partial failures | Some tasks in batch failed | Report which succeeded and which failed; ask user whether to retry or skip |
Example Usage
- "Use executing-plans to implement
docs/plans/2026-02-20-api-hardening.md."
- "Use executing-plans to run the next 3 tasks and stop for review."
- "Use executing-plans to finish remaining tasks and report final checks."
