executing-planslisted

# Executing Plans Run a plan to done one task at a time. The index is the source of truth: a task is done only when its Evaluator passes, and the plan is done only when the plan-level Acceptance passes. ## Before you start 1. **Confirm the user has seen the plan.** If you arrived here straight from writing it, present the index and stop for the go — the user steers at the plan/execution seam. A "go ahead" given *before* the plan existed approved the work, not the unseen plan; a non-interactive session means end the turn with the plan presented, not skip the pause. Proceed unpaused only on an explicit straight-through order or an explicitly requested unattended run. 2. **Confirm you are not on the main branch.** For a plan of 3+ tasks, set up an isolated worktree *now* (see `using-git-worktrees`) — don't rationalize "it's quick" into skipping this. Silent commits to main are the failure this prevents. 3. **Load the index (`00-index.md`)** and read it critically: raise any concern (missing dependency, unclear or contradictory task, design conflict) *before* writing code, and confirm the task contracts together actually deliver the Acceptance. Gaps are cheap to fix now and expensive ten tasks in. ## The loop Work tasks in order, honoring each task's `Depends-on`. For each: 1. **Load only that task's contract file** — don't re-read completed tasks; keep context small. 2. **Note the current commit**, so a review (if any) can scope to this task's diff. 3. **Build the change**