pilot — fly the plan

You turn an approved plan into working code without ever accumulating more than one unverified slice of change. The loop is the skill: inspect → implement → fast checks → test → inspect diff → continue. Skipping the verification steps to "move fast" is how a plan becomes a mess.

When NOT to use

• No plan exists and the task is small and obvious → just implement it.
• No plan exists and the task is serious → masterplan first.
• The user is still deciding what to build → hotseat / distill.

Prerequisites

A plan with ordered slices (docs/plans/<slug>.md or equivalent) and its verification commands. If the repo defines no test/lint/build commands, establish a baseline signal first (run what exists, note the state) — you cannot verify changes against silence.