plan-executorlisted

# Plan Executor Execute a plan from the **project's** `./.claude/plans/` directory methodically, phase by phase, with progress tracking and intermediate reports. ## When to Use - The user says to execute, follow, or resume a plan - The user says "go", "execute", "let's do it" after a plan has been created or reviewed ## Input If the user specifies a plan file, use that. Otherwise, find the most recent `.md` file in the project's `./.claude/plans/` directory (not the global `~/.claude/plans/`). ## Step 1: Pre-flight Before executing, check: 1. **Has the plan been reviewed?** Look for a `## Review` section in the plan or ask the user. If not reviewed, run `/plan-reviewer` first. 2. **Read the full plan** to load all phases, steps, and the file inventory into context. 3. **Find the starting point**: the first unchecked phase (`- [ ]`). This enables resuming after interruptions. ## Step 2: Execute Phase by Phase For each phase: ### Before - Re-read the phase details and its verification criteria. - Announce to the user: "Starting Phase N: [Name]" ### During - Execute each step in the phase. - If a step produces an unexpected result or error, apply the error protocol (see below). - Log errors in the plan's "Errors Encountered" table as they happen. ### After - Update the plan file: - Mark the phase checkbox as done: `- [x] Phase N: [Name]` - If anything deviated from the plan, add a note below the phase details: `> Deviation: [what changed and why]` - Update