Scratch works best as a compact handover between steps. After several drafts, the next chat needs the valid state, not every old message.
Condense goal, decisions, relevant file, exclusions and open questions before continuing.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Create a Scratch handover with goal, current state, confirmed decisions, rejected variants and next question.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to files, sources, responsibilities and expected output format. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not paste long raw text into Scratch when a summary is needed.
The next step starts clear without carrying the whole history.