The implement workflow starts with a plan. It permits a bounded spike only when an unobserved technical claim could materially change that plan. Most work skips it. A spike has one question, a short deadline, and evidence to settle it. It is either disposable or follows a real path. If it changes the plan, that revised plan returns to review.