Overview
Load the plan, review rigorously, execute tasks in batches, report for review between batches.
Core Principles: Batch execution with checkpoints for architect review.
At the start, announce:"I am using the execute plan skill to implement this plan."
Process
Step 1: Load and Review the Plan
- Read the plan document
- Review critically - identify any issues or concerns with the plan
- If there are concerns: raise these with your human partner before starting
- If there are no issues: create TodoWrite and continue
Step 2: Execute Batch Processing
Default: first 3 tasks
For each task:
- Mark as in progress
- Follow each step strictly (the plan has small steps)
- Run verification as specified
- Mark as completed
Step 3: Report
After the batch is complete:
- Show what has been implemented
- Show verification output
- Say: "Ready to receive feedback."
Step 4: Continue
Based on feedback:
- Apply changes if needed
- Execute the next batch
- Repeat until complete
Step 5: Complete Development
After all tasks are complete and verified:
- Announce: "I am using the complete development branch skill to complete this work."
- Required sub-skill: Use superpowers: complete development branch
- Follow that skill to verify tests, present options, execute the choice
When to Stop for Help
Stop execution immediately in the following situations:
- Encounter a blocker in a batch (missing dependency, test failure, unclear instruction)
- The plan has major flaws and cannot be started
- You do not understand the instruction
- Verification fails multiple times
**Ask for clarification instead of guessing. **
When to Revisit Previous Steps
Return to review (Step 1) in the following situations:
- The partner updates the plan based on your feedback
- The basic approach needs rethinking
Do not force your way through blockers - stop and ask.
Remember
- First review the plan rigorously
- Follow the plan steps strictly
- Do not skip verification
- Reference the skills mentioned in the plan
- Between batches: just report and wait
- If blocked, stop; do not guess randomly
- Never begin implementation on the main/master branch without the user's explicit consent
Integration
Required workflow skills:
- Superpowers: using-git-worktrees - Required: set up an isolated workspace before starting
- Superpowers: writing plans - Create the plan that this skill executes
- Superpowers: complete development branch - Complete development after all tasks are done