Vibe Plan Execution

Overview

Execute an existing implementation plan without inventing missing behavior. Bind to the plan, verify the facts it depends on, implement the smallest safe current slice, and stop when reality contradicts the plan.

Questioning a plan is required when its sections conflict or implementation reveals a defect. The plan is authority for scope and intent, not proof that every implementation instruction is correct. Deviating from it is not allowed until verified evidence proves the plan is incorrect, stale, impossible, unsafe, or already satisfied. Treat "this looks redundant" as a hypothesis, not as permission to skip planned API, specification, implementation, or test work. When the defect changes the requirements, acceptance criteria, proof strategy, or implementation contract, return to the owning requirements or planning artifact before editing that behavior. Do not turn a stale plan into a series of one-off patches.