Refine Superpowers Lite execution workflow

skills/executing-plans/SKILL.md

@@ -7,7 +7,7 @@ description: Manual-only skill. Activate only after an explicit user request for
 
 ## Overview
 
-Load plan, review critically, group tasks into phases when useful, execute all phases, report when complete.
+Load plan, review critically, execute every task in the current branch in one run, perform one overall code review, then report when complete.
 
 **Announce at start:** "I'm using the executing-plans skill to implement this plan."
 
@@ -23,26 +23,38 @@ Load plan, review critically, group tasks into phases when useful, execute all p
 5. If concerns: Raise them with your human partner before starting
 6. If no concerns: Create TodoWrite and proceed
 
-### Step 2: Group Tasks Into Phases
+### Step 2: Prepare a Single Run
 
-Before implementation, decide whether adjacent tasks should run as one phase:
+Before implementation, organize the work for one uninterrupted run:
 
-- Group tasks that touch the same files or complete one coherent behavior
-- Keep tasks separate when they are independent, risky, or easier to review alone
-- Preserve the plan's task checklist, but use phase-level review checkpoints
+- Preserve the plan's task checklist for progress tracking
+- Use phases only as an execution grouping aid, not as review checkpoints
+- Do not create or switch to a worktree unless the user explicitly asks
 
-### Step 3: Execute Phases
+### Step 3: Execute All Tasks
 
-For each phase:
-1. Mark as in_progress
+Complete every task from the plan in the current branch:
+
+1. Mark the active task or phase as in_progress
 2. Follow each included task step exactly (plan has bite-sized steps)
 3. Run verifications specified by the included tasks
-4. Request or perform one review for the whole phase
-5. Mark all included tasks as completed only after the phase review is addressed
+4. Mark tasks completed as they finish
+5. Continue until all tasks are implemented and verified
 
-### Step 4: Complete Development
+Do not request code review between tasks or phases by default. Save review for Step 4.
 
-After all tasks complete and verified:
+### Step 4: Overall Code Review
+
+After all tasks are implemented and verified:
+
+1. Use superpowers-lite:requesting-code-review for one overall review of the full implementation
+2. Fix Critical and Important findings
+3. Re-run relevant verification
+4. Re-review if substantial fixes were required
+
+### Step 5: Complete Development
+
+After all tasks complete, verified, and reviewed:
 - Announce: "I'm using the finishing-a-development-branch skill to complete this work."
 - **REQUIRED SUB-SKILL:** Use superpowers-lite:finishing-a-development-branch
 - Follow that skill to verify tests, present options, execute choice
@@ -69,6 +81,7 @@ After all tasks complete and verified:
 - Review plan critically first
 - Follow plan steps exactly
 - Don't skip verifications
+- Do one overall code review after all tasks are done
 - Reference skills when plan says to
 - Stop when blocked, don't guess
 - Work in the current branch by default; do not create or switch to a worktree unless the user explicitly asks
@@ -78,6 +91,7 @@ After all tasks complete and verified:
 
 **Required workflow skills:**
 - **superpowers-lite:writing-plans** - Creates the plan this skill executes
+- **superpowers-lite:requesting-code-review** - Overall review after all tasks are complete
 - **superpowers-lite:finishing-a-development-branch** - Complete development after all tasks
 
 **Optional workflow skills:**