executelisted

# Execute Implementation Plan Execute an implementation plan produced by `plan:write`. The plan is the source of truth: follow it literally, and keep it updated so anyone — human or agent — can read the file and know exactly where the work stands. Code is written and committed under `code:implement` — its standards, verification, branch, and commit rules apply throughout. This skill adds only what the plan contributes: which phase runs, what its tasks say, and keeping the file honest about progress. Phases run sequentially in the current session. They are ordered because they depend on each other, so later phases benefit from the context the earlier ones built — do not farm them out to independent agents. ## Workflow ### 1. Locate and verify the plan Find the plan file in `/plan/` (the user may name it; otherwise pick the file matching the work described). Verify it follows the `plan:write` template: - Front matter with `goal` and `status` - `## 2. Implementation Steps` containing `### Implementation Phase N` sections - Each phase has a `GOAL-NNN` and a task table with `Task | Description | Completed | Date` columns If no plan exists or the file doesn't match this structure, stop — do not improvise a plan or execute from an unstructured document. Tell the user and offer to write one with `plan:write` first. ### 2. Resolve scope Read the request for one of four forms, and state which one you resolved before starting: - **Named phase** — "run phase 2", "phase 3 only"