executing-planslisted

# Executing Plans ## Overview Load an existing `3-PLAN.md`, review it critically, execute tasks in small batches, verify each task, and report for review between batches. **Announce at start:** "I'm using the executing-plans skill to implement this plan." ## The Process ### Step 1: Locate and Review Plan 1. Use the plan path provided by the user, or ask for it if none was provided. 2. If no path is provided and an active `~/.pi/plans/...` task folder is known, read `3-PLAN.md` from that folder. 3. If `3-PLAN.md` is missing, stop and ask for the correct plan path. 4. Review the plan for contradictions, missing verification commands, or unclear tasks. 5. Raise blocking concerns with the user before editing files. 6. Confirm you are not on `main` or `master` before implementation. If you are, ask for explicit consent before editing or ask whether to create/switch to a branch or worktree. ### Step 2: Execute a Small Batch Default batch size is the first unfinished task, or up to three small independent tasks when the plan explicitly marks them independent. For each task: 1. Mark it in progress using `@tintinweb/pi-tasks` if available, otherwise any generic Pi task tool, otherwise the checkbox in `3-PLAN.md`. 2. Follow the task steps exactly. 3. Run the task's verification command and read the output. 4. Mark the task complete only after verification evidence supports completion. 5. Commit only the files for that task when the plan calls for a commit. ### Step 3: Report