reweavelisted

# Reweave — fold a follow-up's answer back into the response it belongs in The user asked a substantive question, got a response, then asked a follow-up about one part of it. Now they want the ORIGINAL target back — rewritten as if the follow-up's answer had been part of it all along — so they don't pay the "scroll up, find the answer, mentally splice it in" tax themselves. Regenerate the target with the follow-up folded in **at the source** and return one clean standalone version. This is a *re-integration* task. It is NOT summarizing the thread, NOT compressing or expanding a point, NOT rewriting from scratch, and NOT changing what source code *does*. The value is entirely in *how* the merge is done — integrate at the source, thread the idea forward, hold the length — not in the mere fact that the new material appears somewhere. Appending it at the bottom is exactly what the user could do themselves, and exactly what this skill exists to prevent. ## Two target shapes — and the output lands where the target lived | Target | Reweave to | After | |---|---|---| | A prior **chat response** (walkthrough, plan, analysis, debug write-up, rec) | **chat**, standalone, inline | — | | An on-disk **prose/plan artifact** a prior turn wrote (`docs/plan.md`, design doc, README section, spec, PR/commit draft, docstring) | **that same file, in place** (Read → Edit/Write) | a 2–3 line note in chat on what threaded through | Don't move the target: never dump a file's reweave into chat, an