Change Write-Up — refactor-chain · docs

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: docs · Prerequisite: the lane + review gate are done (all steps verified) · Next: refactor-artifacts-sync / refactor-publish-checklist / refactor-ship. Adaptivity / conditional: repo-agnostic and advisory — always safe to run; produces a document, never edits code.

Purpose

When a refactor chain finishes, the person who asked for it wants one thing: a straight answer to "what did you change, and is my app still going to work the same?" This skill writes that answer. It reads the before picture (the Project Profile snapshot refactor-understand captured at the start) and the after picture (the chain's step records, the git diff, the verify results), then produces a calm, plain-language change report — what moved, what got renamed, what got safer, and the explicit promise that behavior was preserved — with a collapsible technical appendix for the developer who wants file-level detail.

When to use

• The chain has reached the docs phase: every lane step and the review gate are done.
• Someone asks "what did you actually change?", "give me the summary", "explain this in plain English".
• Right before shipping, so the PR / handoff has a human-readable narrative attached.
• Advisory-only — safe to run any time after work exists; it just reports.