regroundlisted

# Reground The current session has drifted: the recent work rests on assumptions the codebase has not been shown to support, invents systems that may not exist, or builds past what the task needs. This skill is a hard reset to ground truth. It does not summarize or compact — it **discards the speculative thread** and rebuilds a small, evidence-backed footing for the next step. Run the protocol in order. Do not skip ahead to step 5. ## 1. Halt Stop immediately. Make no further `Edit`, `Write`, or other tool calls that advance the work until the report in step 5 is produced and the user approves a next step. Before reporting, make sure the working tree is in a coherent state — **never leave a file half-written or a multi-file change partly applied.** If a change is mid-flight, the only edits permitted here are the minimal ones that restore a self-consistent, non-broken state, or a clean revert of it; make no new feature progress either way. The aim is solid footing to assess from, not a frozen half-edit. ## 2. Name the drift State plainly, in one or two sentences, the specific unverified assumption(s) the recent work depended on — the equivalent of "the last answer assumed X, but the repo shows no evidence for X." Be concrete: name the assumed file, function, endpoint, schema, or behavior. If you cannot name what was assumed, that itself is the finding — say so. ## 3. Set the anchor Decide the focus file set — the minimum slice of the repo the next step actually depends