Agents using our data-pipeline-authoring skill keep producing migration scripts that interleave validation, transformation, and logging in a single pass over the data, so when a migration fails nobody can tell which stage broke or safely re-run part of it. Teammates have asked for guidance in the skill so migration scripts come out cleanly staged. Output: (1) the exact guidance text you would add, (2) your verification plan before deploying it.
