Overview
Load the plan → critically review it → execute tasks in batches → after each batch, report and wait for review.
Core principles: Batch execution + checkpoints, so architecture/code review can step in at a steady rhythm.
At the start, announce: "I am using the executing-plans skill to execute this plan."
The Process
Step 1: Load and review the plan
- Read the plan file
- Critically review: identify questions, risks, and inconsistencies
- If there are concerns: align with your human partner before starting work
- If there are no concerns: create TodoWrite and continue
Step 2: Execute one batch
Default: do the first 3 tasks
For each task:
- Mark as
in_progress - Execute strictly step by step (the plan should be chewable small steps)
- Run verification as required by the plan
- Mark as
completed
Step 3: Report
When this batch is complete:
- Explain what this batch implemented
- Attach the verification output
- Say: "You can give me feedback now."
Step 4: Continue to the next batch
Based on feedback:
- Fix first if necessary
- Execute the next batch
- Repeat until everything is complete
Step 5: Finish development wrap-up
When all tasks are complete and verification passes:
- Announce: "I am using the finishing-a-development-branch skill to complete the wrap-up."
- Required sub-skill:
superpowers:finishing-a-development-branch - Follow that skill to complete test verification, present options, and execute the choice
When to stop and ask for help
Stop execution immediately if the following occurs:
- You hit a blocker mid-batch (missing dependency, failing test, unclear instructions)
- The plan has a critical gap that makes it impossible to start
- You do not understand an instruction
- Verification fails repeatedly
Do not guess. Clarify first.
When to return to earlier steps
Return to Review (Step 1) in the following situations:
- Your partner updated the plan based on your feedback
- The underlying approach needs to be rethought
Do not push through a blocker — stop and ask clearly.
Remember
- Critically review the plan first
- Execute strictly according to the plan steps
- Do not skip verification
- Reference the skill when the plan requires it
- Between batches: only report and wait
- If you get stuck, stop; do not guess